Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - satrow

Pages: 1 [2] 3 4 5
26
Explanation/reason already given.

No more wasting my time on this /unsubbed.

27
You need to use NirSoft's RegScanner and ensure that you're doing a full Registry search (not just the part that's currently loaded): https://www.nirsoft.net/utils/regscanner.html

28
"autocheck autochk *" looks fine, check the same exists in the equivalent HKLM\SYSTEM\ControlSet00x\Control\Session Manager entries.

I said that there are a lot of entries, what exactly is it about???, but only the one related to autocheck etc.

CurrentControlSet = the Boot type you're currently running under, the other sets relate to alternate Boot types, Safe Mode, Safe Mode with networking, etc. is my understanding.

Does "autocheck autochk *" appear for all of the alternate HKLM\SYSTEM\ControlSet00x\Control\Session Manager entries for BootExecute?

29
"autocheck autochk *" looks fine, check the same exists in the equivalent HKLM\SYSTEM\ControlSet00x\Control\Session Manager entries.

30
What do you see detailed for HKLM\SYSTEM\CurrentControlSet\Control\Session Manager -> BootExecute?

And for all the HKLM\SYSTEM\ControlSet00x\Control\Session Manager entries?


31
Tweaking.com Support & Help / Re: Bowser/Browser
« on: October 09, 2018, 01:13:08 am »
bowser(.sys) has been around for a long time, here it is from W7x64:


32
Five days can be a little too early to be sure a BSOD is really fixed but if we pinned down the cause correctly, you might be right :)

Thanks for the feedback!

33
No trouble :)

I did bump into a site which might have more recent drivers for some parts of your PC, don't use their Driver updater/utility, try to check your file versions against the ones listed for your W7 32-bit components here before downloading the package to install it, it's not uncommon to find older drivers inside a newer wrapper: https://www.driverscape.com/manufacturers/fujitsu/laptops-desktops/ga-8sgxlfs/9084 < it's not a Fujitsu site, so take care.

34
Good work.

It looks like your base hardware is all pretty old, and I'd guess it must have been originally on XP. I doubt that there's any W7-specific drivers available for it.

Do you still use dial-up or fax? If not, your SmartLink modem can be uninstalled and physically removed. This should prevent the 2004 drivers loading (slntamr.sys, SlWdmSup.sys, Mtlmnt5.sys and RecAgent.sys).

I don't think we can do anything about the 2007 driver, sisagpx.sys AGP (GART) driver). The latest drivers I see are of the same XP/Server2003 vintage.

The WER logs showed signs of BSOD/program crashes involving at least two different torrent programs, these are pretty notorious for hogging resources and clashing with security drivers. I would fully uninstall any torrent software, or at the very least, prevent them from running at startup.

I don't see any known bad drivers loading otherwise.

Ensure you keep the common malware target software fully updated, Windows obviously, Adobe Reader/Macromedia Flash/Java (are you really sure you still need Java? Uninstall it if you're unsure, if any other program fails to run because it needs Java, look for alternatives to them).

35
They may reinstate themselves after a reboot.

Only if their Registry entries are still in place, which I believe would have been taken care of by the original uninstall, and if disabling them from starting failed. If the Guard driver is stopped and disabled, the Helper driver can then be stopped and disabled, since the Guard driver wasn't running to prevent this 'interference'.

36
It looks like your (Trial?) version of Zemana AM required the user to disable the auto-running sections before uninstalling, though that was probably not made clear.

We'll need to prevent the following from auto-starting:
zam32.sys
zamguard32.sys

I'm sure someone would be able to write a script to disable these but I do it manually - CAUTION: mistakes made using this method could make your PC unbootable. You need to have a recent computer image and the tested means to boot and replace the broken image; I don't know whether a Windows System Restore would work.

Right-click My Computer > Manage > Device Manager. View > Show hidden devices > Non-Plug and Play drivers -> find the entry that refers to the zamguard32.sys and double-click it, switch to the Drivers tab - check the details are correct - click Stop if it's Started and then change the Startup type to Disabled.

With the Guard driver hopefully now stopped, you should now be able to use the same routine for zam32.sys.

Check after a reboot to see whether both settings have stuck.

(I've PMed @Boggin to ask whether he can find/create a script for this).

If all goes well, we'll move on to try to discover what (if anything) was causing ZAM to try to take action and trigger the BSOD, and try to clean up/update some very old drivers (2004 - 2007, was this an upgrade from XP?) that might also trigger BSODs.

37
Okay, it looks like the Zemana zamguard32.sys driver was involved with or caused this BSOD, though I don't see a Zemana entry in the Programs list; did you use/uninstall this software previously? Can you see it in Add/Remove Programs to uninstall it?

38
Hi Sue.

Let's see if we can get some clues as to what's been happening and hopefully get a handle on the cause.

Minidumps are stored in a hidden folder within the main Windows directory: C:\Windows\Minidump where the minidumps have a .dmp file extension (though by default, extensions, and this folder, are hidden). Show hidden files and folders.

Once you can see the dumps, copy them to a new folder on your Desktop, zip the contents of that folder (right-click > Send to > Compressed folders) and attach the resulting compressed/zipped file to a Reply.

We'll need some background info + error messages etc. as well: Start > Run > MSInfo32 > Enter. This should start the collection process for the System Information viewer, it's likely to take several minutes, maybe longer - to check that the info is fully loaded, work through the subsections and check they (almost, a few won't have data) all contain code/details. The main section I'm interested in is the final one, Software Environment > Windows Error Reporting (WER), though many of the others will provide useful info too.

When you're happy that the viewer is fully populated, File > Save > MSInfo32.NFO (the default) to your Desktop, zip it as above and attach the zip file to your Reply.

39
General Computer Support / Re: lost files
« on: July 14, 2018, 01:50:14 am »
DDR2 sticks will fit DDR2 slots. Ensure all sticks are as close as possible in terms of base DDR2 standards and frequencies and that they're all either single- or dual-sided.

Best to check the specs on the 'board maker's QVL list for RAM tested in 4's (Qualified Vendor List, which will contain many more pairs of RAM than quads, the lists are never fully comprehensive, most aren't updated once the 'board goes on sale) for sticks that most resemble your 'good' ones.

Best compatibility/results will always be on matched pairs/quads that most resemble those in the QVL at, or closest to, the max. memory capacity of the 'board.

Checking RAM for that 'board on the Crucial comparator is often quite educational.

40
General Computer Support / Re: lost files
« on: July 12, 2018, 11:47:15 am »
All DDR2 memory sticks have the notch in the exact same position, it's part of the standards laid out before they went into production. Same goes for the other DDR* series. It's impossible to fit one into a slot built for another without causing breakage to RAM, slot, or both. Even if you made use of a file to remove the 'pip' inside the slot, I'm pretty sure the contacts wouldn't line up and the PC would fail a BIOS check, I very much doubt it would get as far as attempting to boot to Windows..

41
General Computer Support / Re: lost files
« on: July 06, 2018, 10:40:50 am »
A quick scan through the wall of text and I'm thinking some kind of interference between Emsisoft, Malwarebytes Chameleon and/or 360.cn drivers and the kernel, they all run close to the Windows kernel and any glitch there could easily cause a BSOD.

Bad RAM can't be ruled out either. The chances of the kernel itself being at fault are miniscule.

Carrona's site says:

Quote
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel

Your BSOD subtype gives no further clues: unknown.

42
Roll back the SATA drivers as per my previous post, this will allow Magician to 'see' your drive.

The problem with changing your drive order using the cables as it stands is that the only working Windows install is accessed by the boot sequence 'bouncing' from one drive to another - not good long term, way too complex.

43
If the SSD isn't being recognised by Samsung Magician, try rolling back the drivers for the SATA ports to the default MS AHCI versions; these will allow Magician to see the drive, the firmware to be updated and Trim to work. The downside is that the drive(s) may not be quite as fast.



 

44
General Computer Support / Re: AdwCleaner 7.1 & 7.1.1 new version
« on: May 02, 2018, 03:40:31 am »
That much has been obvious all along, finding the cause was impossible due to the lack of supplied data and system/software details.

unsubbed

45
General Computer Support / Re: AdwCleaner 7.1 & 7.1.1 new version
« on: May 02, 2018, 02:34:56 am »
You have the data needed to discover the problem, we don't, you haven't supplied it. I could suggest a workaround but that's not the same as a fix.

If you wish to continue playing games you should create your own site, I don't think this is the correct place for them.

Do widzenia.

46
I wasn't suggesting that the Windows installation was faulty, just that the initial steps currently needed to boot to Windows open you up to a breakdown in the future, perhaps with your next OS upgrade, a BIOS glitch or hardware malfunction.

My disk layout ensures that I can remove all but Drive 0, the C: containing Windows, and still have a fully functioning System. You cannot do that, your layout needs at least 2 of those installed drives to boot up.

The reason your WEI scores are unchanged since adding your SSD is that WEI tests only the drive where Windows is installed, namely the K:


47
General Computer Support / Re: AdwCleaner 7.1 & 7.1.1 new version
« on: May 01, 2018, 10:54:50 am »
Are you using a clean, legit version of W7, your C:\Windows\SysWOW64\msvcrt.dll details (file size + Private/Special build) look odd? Check your version with VirusTotal please, give us the VT URL.

My C:\Windows\SysWOW64\msvcrt.dll details:




48
That looks a complete mess, cf. my C: status flags with your current Windows drive K:

Whilst your system can be repaired, it requires an expert to provide the rather complicated list of steps (and checks) to restore your PC to something suitable to be upgraded to W10. That's me out, I've been sticking with the KISS principles for disk management for the last 15 years.

I'd go the clean install route with W7, only the SSD installed, check that TRIM is active after updating Windows (WU might install an 'upgraded' driver that 'blocks' Trim - W10 did it to me after the AU Update - rolling back the drivers to the default W7/10 version will reactivate Trim), upgrade to W10 and then re-attach your HDDs and get it setup to your liking. Don't forget to create clones/backups before any major upgrade or change.

W7 can be installed on a single partition; as my C: shows, W10 requires, I think, 3x partitions; you'll need to make allowances for that according to the current recommendations during the W7 install, which would then likely make use of 2x partitions with unallocated space left for the W10 upgrade 'hidden data' partition.

49
Can you show us a screenshot of Disk Management so we can see the full Status details, please?


50
What's the Windows Experience Index (WEI) score for your drive now? Control Panel\All Control Panel Items\Performance Information and Tools.

Run a benchmark on your SSD with =http://www.hdtune.com/HDTune Pro and attach the screenshot, please.

Trim being enabled by the OS doesn't necessarily mean that the Trim calls are reaching the drive(s), a 'bad' Controller driver can block the calls (even drivers from the hardware maker or Windows Update have been known to do this). If you can update the firmware on the drive(s) successfully, Hard Disk Sentinel or Trimcheck report  that Trim is active or that it's working, then Trim is almost certainly enabled and active.

Pages: 1 [2] 3 4 5