Recurring BSOD on Vista x86 Login

awilson29 · Oct 11, 2010

I woke up this morning on a bright and sunny Autumn morning went to boot my PC, came back after a coffee, logged in and watched the dreaded BSOD appear whilst my system tray icons were loading. The issue reoccurs in the exact same point after 5 reboots and I have now just had the BSOD in safe mode also.

System is:

Vista Ultimate 32bit OEM
Asus P5-K Deluxe MB
4GB RAM
Intel Q6600
Approx 2 years old self-built
2* Nvidia 8800 Graphics Cards (1 GTS 640GB and 1 GT)

I have attached the output from the BSOD tool but cannot run the system health report in safe mode as it keeps say that it cannot find the file specified in the viewer. The system has been running fine for a years and all of a sudden recurring BSOD. Temperatures look within limits - processor at 42c idle - ram passes memtest86+ cursory scan. I have reinstalled all drivers, Chipset (forced overwrite of Intel Chipset drivers & AHCI from Intel, Marvell Yukon Ethernet Driver, Sound Drivers, Nvidia Video Card Drivers.

If I use a diagnostic startup from MSCONFIG I can get the machine to boot whilst not being in safe mode but still cannot run the Perfmon report.

C:\Users\Alistair>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Users\Alistair>

Any help or diagnosis greatly appreciated as I am running out of ideas other than an upgrade to Windows 7 / repair / reinstall of Vista ...

Thanks in advance!

...

usasma · Oct 11, 2010

While the memory dump files are running in the debugger, here's some comments:

MSINFO32 points to 9 memory dumps with 6 different BSOD errors. The 2 biggest concerns (IMO) are the STOP 0x116 error (a video card issue). Please have a look at the troubleshooting procedures here (although it's Win7, the procedures will work for Vista also): STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

The other issue points to your Kaspersky program. Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Kaspersky from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Kaspersky using this free tool: Removal tool for Kaspersky Lab products
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Also, Daemon Tools and the Catalyst Control Center have BSOD issues with some Windows installations. Please uninstall them until we're finished troubleshooting. Use this free tool to remove the sptd.sys driver from the C:\Windows\System32\drivers directory: DuplexSecure - Downloads

Check after running the program. If the sptd.sys file isn't gone, then rename it to sptd.BAK

Although you do have 4 gB of RAM, you have more startup items than I've seen in a very long time (I count 78). I would suggest removing at least 3/4 of them.
Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

Code:

[font=lucida console]
hardlock.sys Wed Jul 27 09:08:29 2005 (42E7874D) - Hardlock Device Driver by Aladdin Knowledge Systems - [url=http://www.carrona.org/dvrref.html#hardlock.sys]Driver Reference[/url]
Afc.sys      Wed Feb 23 01:58:55 2005 (421C29AF) - Arcsoft(R) ASPI Shell (CD/DVD program) - [url=http://www.carrona.org/dvrref.html#Afc.sys]Driver Reference[/url]
ASACPI.sys   Wed Oct 18 01:44:46 2006 (4535BF4E) - Asus ATK0110 ACPI Utility - [url=http://www.carrona.org/dvrref.html#ASACPI.sys]Driver Reference[/url]
mgnt.sys     Tue Mar 03 06:58:31 1998 (34FBF067) - MicroGuard Copy Protection - [url=http://www.carrona.org/dvrref.html#mgnt.sys]Driver Reference[/url] [COLOR=red]Remove with care.[/COLOR]
SVKP.sys     Mon Mar 10 11:31:42 2003 (3E6CAFDE) - Slovakian anti-cracking program - [url=http://www.carrona.org/dvrref.html#SVKP.sys]Driver Reference[/url] [COLOR=red]Remove with care.[/COLOR]
[/font]

If all this doesn't stop the BSOD's, then please run Driver Verifier according to these instructions:

Code:
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 05:43:26.646 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:58.414
Probably caused by : ntkrnlmp.exe ( nt!KiAttachProcess+5f )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments 001bf448 0000001b 00000000 8408ca8c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 04:18:39.841 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:42.340
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+45 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  verclsid.exe
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments c0000005 8409ddb3 807b0858 807b0554
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 04:14:59.058 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:23.558
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+45 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  verclsid.exe
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments c0000005 840cfdb3 807c0858 807c0554
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 02:45:06.902 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:39.047
Probably caused by : memory_corruption ( nt!MiDeferredUnlockPages+1a1 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 000081fa 00000002 00000000 84082c31
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 02:25:57.074 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:00.184
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments c0000005 a68afb7a 807b4c80 807b497c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 01:53:09.568 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:02.663
Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::TransferCodecVerbs+148 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 0000006c 0000001b 00000001 840a2a36
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Oct 11 00:59:36.953 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:49.048
Probably caused by : ntkrnlmp.exe ( nt!KiAttachProcess+9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 0000006e 0000001b 00000001 840b5a36
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Recurring BSOD on Vista x86 Login

awilson29

New Member

Attachments

My Computer

System One

usasma

Old and cranky

My Computer

System One