BSOD - 0x0000001e (usually) when playing games

barnabas79 · 06 Oct 2012

I've been getting BSOD recently when playing games (Starcraft II and Diablo III, to be exact)... though I can't be certain it's related to the games, since games are what I primarily use this computer for.

I thought the crash might be due to faulty memory, and I had been looking to upgrade my memory anyway, so I recently bought entirely new memory and installed it in my box... unfortunately, this did not solve the problem, as I got another crash today, so I'm coming here for help.

Any hints on where to look would be appreciated!

Thanks,

Paul

Arc · 07 Oct 2012

Welcome aboard. Your latest dump says:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

In such a situation, it is better to check that if there is any device driver is there behind those crashes.
Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

barnabas79 · 08 Oct 2012

Well, I followed the above instructions, and loaded the Driver Verifier.

The Good News: It seems to have identified usbfilter.sys as the problem driver.

The Bad News: I can no longer boot into windows.

Basically, when I restart windows now, I have two options: Startup Repair (which I'll get to in a sec.), and Start Windows Normally, which will immediately throw a BSOD, usually identifying usbfilter.sys as the problem (it once didn't name any particular culprit.)

If I do startup repair, when I get to the screen where I need to choose an operating system, there are no OSes available to select. I'm not sure why this would be, as I'm not using RAID on the drive where windows is installed. (Full disclosure - I have a total of 4 drives in my box: 1 on which Windows 7 is installed, one on which Fedora 16 is installed, and 2 which I have setup as a RAID 1-mirrored data drive, using my motherboard's controller.)

Due to the fact that it can't find my OS, none of the normal startup options seems to work, other than the memory diagnostic (which I doubt is the problem, since I replaced all my memory - see my first post), and the command prompt... which is useless, since all I can access is the X: drive, which I assume is a ram drive holding the system recovery program.

Any help would be appreciated!

barnabas79 · 08 Oct 2012

UPDATE - I was able to get it to recognize my drives by disabling the motherboard support for RAID in my BIOS (apparently, even though that specific drive wasn't RAID'ed, it was managing all my drives through the RAID controller, which confused Windows).

I can now access the drives through the command prompt, and it seems I will need to do offline editing of the registry to disable the driver verifier. Anybody have more specific instructions on how to do this?