Win7 32-bit Crashing Since Jan 2010

gedafe said:

Gents,

Thanks for the new memtest86+ link--it worked just fine--even from a usb drive. Anyway, I ran it for 20 minutes and it cycled through 100 passes. Here's what the readout said:

Walltime 0:19:30
Cached 4087M
RsudMem 264K
MemMap e820
Cache on
ECC off
Test Std
Pass 0
Errors 0

Does this mean that my memory is ok? Just for an update, I haven't had any crashes (knock on wood) since I updated my keyboard and mouse drivers. What do I need to do next?

-Fence

How did it run so fast?

But yes, it should mean that the RAM is fine.

~Lordbob

I would for you to rerun memtest following these instructions. As Lordbob said, your test ran faster than I am used to seeing it run. I want to make sure it ran properly. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

The error code is still pointing to a possible memory problem. Error code 1A -

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

I am still finding an old driver running when you had the BSOD:

whfltr2k.sys Thu Jan 25 10:45:01 2007 - USB Mouse Lower filter driver, Gigabyte GM-M6800 Driver. Please update this driver and we will go from there.

Yes, the number of loops or passes is the number of times it has run. After 7 or 8, you can stop it. Memtest gives you a display on the screen and will show you any any errors.

Have you got another mouse you can try - maybe a standard PS2 mouse or a newer USB mouse? If you do, install it and then completely uninstall your current mouse. YOu can always reinstall it it if it proves not to be a the source of your problem. If it were me, I would just buy a new gaming mouse and verify that it is Win 7 compatible before I purchase it.

Looks like your memory is good; that is good to know. Good job.

You raised something that I need to ask you about, do you still have Kaspersky installed? If so, please uninstall it for the purposes of trouble shooting. Kaspersky is well known for causing BSOD's on Win 7 systems. Replace it with MSE and make sure Windows Firewall is turned on.

I can't really answer your question about the mouse except to say it is certainly possible that the driver could be causing problems. The only way I know to test it is to try another mouse. A 2007 driver is pretty old for a Win 7 system. But, yes, the BSOD could have been caused by something else.

Trouble shooting is a trial and error thing. There is no software that will definitively pin point an exact cause. I wish there were such a critter.

Edited to add - You posted your latest dump while I was posting. I will look at this one and get back.

This dmp shows the same error code, 1A - memory management.

Once you have done the things I posted above, I suggest you run Driver Verifier.

Using Driver Verifier to identify issues with Drivers

Please follow these instructions in order to run it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users