BSOD after verifier

[lsuk]

Hello all,

Okay, so I have been getting a lot of BSOD. I tried to do the verifier trick and got a BSOD quickly. When you get a moment, can you please review and let me know if you can isolate the problem? Thanks.

P.S. - Sorry for the bump.

 

[usasma]

Please turn off Driver Verifier and let the system BSOD on it's own.
Then upload those minidumps.

 

[lsuk]

okay, so i was on internet explorer and got another BSOD (after deleting the verifier). Please find enclosed the minidump and my system information.

side note- as i was looking through my event log, i notice that two items (lirsgt and atksgt) were failing at start up. are these the culprits? and is there a way to see if my usb is a nvidia EHCI?

Thanks for all your help.

 

[usasma]

lirsgt and atksgt are a part of the Tages copy protection system - it's possible that they are causing issues with your system.

Your USB is a nVidia OpenHCD USB Host Controller
Here's the details on your USB devices:

Standard OpenHCD USB Host Controller    PCI\VEN_10DE&DEV_077B&SUBSYS_2A81103C&REV_A1\3&267A616A&0&10
Standard Enhanced PCI to USB Host Controller    PCI\VEN_10DE&DEV_077C&SUBSYS_2A81103C&REV_A1\3&267A616A&0&11
Standard OpenHCD USB Host Controller    PCI\VEN_10DE&DEV_077D&SUBSYS_2A81103C&REV_A1\3&267A616A&0&20
Standard Enhanced PCI to USB Host Controller    PCI\VEN_10DE&DEV_077E&SUBSYS_2A81103C&REV_A1\3&267A616A&0&21

The dump files blame core Windows files, which is probably not the case (if it were, you'd have many more problems other than the occasional BSOD).

I'd suggest starting with these tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, I'd suggest running Driver Verifier according to these directions:

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/Win7 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.

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

Here's a summary of the BSOD's:
Please note that the middle one is a Driver Verifier enabled minidump - and it indicates memory corruption

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 10 03:53:05.223 2010 (GMT-5)
System Uptime: 0 days 1:15:19.236
BugCheck 50, {fffff908c0c161e8, 0, fffff96000134b2c, 5}
Probably caused by : win32k.sys ( win32k!InternalRebuildHwndListForIMEClass+94 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 10 13:01:59.987 2010 (GMT-5)
System Uptime: 0 days 0:21:16.047
BugCheck A, {fffffa9009dd4be8, 2, 1, fffff80002b7aabf}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 11 01:13:42.497 2010 (GMT-5)
System Uptime: 0 days 0:17:00.511
BugCheck 50, {fffff9c0c25bd8a0, 0, fffff96000291136, 5}
Probably caused by : win32k.sys ( win32k!vDynamicConvertNewSurfaceDCs+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe