BSOD Randomly happens, flash for a second, and then turns off PC.

[jburnssa]

I've had a shuttle sk22g2 v2 system that I leave on and sometimes find turned off and occasionally see a BSOD when using. The BSOD happens randomly, flashes on the screen for about 1 sec, and then turns off the PC. I've had this issue since doing a fresh install of Win7 ultimate 64 from window XP 64.

I don't know if it is related, but I also had an issue where my on board NIC would stop working. I tried fixes from installing different driver versions, restarting services, and restarting the NIC. The only thing that would recover would its functionality be restarting windows. I added a NIC card and that has allowed me to keep network access.

Thanks in advance for your help,
John

 

[jburnssa]

Analysis of latest dump file \091612-21484-01.dmp:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\091612-21484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0020d022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`03c534d2?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`03291670
Debug session time: Sun Sep 16 00:34:42.625 2012 (UTC - 5:00)
System Uptime: 1 days 2:15:25.171
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8003c9f060, fffff80000b9c518, fffffa8004570910}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : pci.sys
Followup: MachineOwner
---------

 

[Arc]

Welcome aboard.

► First of all, your BIOS is very old, if possible, update it.

BIOS Version/Date    Phoenix Technologies, LTD 6.00 PG, [COLOR=Red][B]11/3/2006[/B][/COLOR]

► Update the following drivers:

• VIA Rhine III Compatible Fast Ethernet Adapter : From VIA Drivers Download - VIA Technologies, Inc.
• ATI Video driver (driver only, not Catalyst Control Center) : From AMD Support & Drivers

► 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.

 

[jburnssa]

Thanks for the quick reply.

I updated my LOM to the latest drivers from the VIA site.
New LOM driver version is 1.15.0.1.

The current video driver for the ATI Radeon HD 4600 on the system is from 4/5/2012. ATI version 12.4 driver version 8.961.0.0. There is a later driver, but it is a beta version which was released 6/28/2012. 12.7 Beta. I prefer not to use a beta driver, but if you think this is the issue I will try it.

The bios needs to be flashed from DOS boot disk. I have a few of these, but they are at work, so I will try this tomorrow.

Does it make sense to run the driver verifier before upgrading the BIOS or wait until it is updated?

 

[Arc]

The BIOS update is not mandatory, but desirable. You may do it any time.

But Driver verifier is must.

Drop updating ATI, enable driver verifier and let us know the result.

 

[jburnssa]

After updating the LOM driver I got a blue screen a couple of hours later. I've attached that dump. The prblem details are at the bottom of this entry.

I am now going to turn on the driver verifier and will post results, probably tomorrow 9/17/2012.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8003C9FA10
BCP3: FFFFF80000B9C518
BCP4: FFFFFA8006F76E10
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\091612-21328-01.dmp
C:\Users\John\AppData\Local\Temp\WER-102750-0.sysdata.xml

 

[jburnssa]

After turining on verify and rebooting I got a blue screen. The blue screen came pretty quickly (it seemed like 1 -2 minutes of logging in). This happened 2 more times before I went to safe mode to disable verify.

I'm attaching the 3 dump files. They were created about 4 minutes apart, so that give you an idea of how often I was getting them.

 

[Arc]

All the three dumps you uploaded indicated the same victim: Lavasoft Ad-Aware driver.

One says Stop 0xC4:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck C4,[/B][/COLOR] {3c, b8c, 0, 0}

Unable to load image \??\C:\[COLOR=Red]Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys[/COLOR], Win32 error 0n2
*** WARNING: [COLOR=Red]Unable to verify timestamp for KernExplorer64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
[COLOR=Red][B]Probably caused by : KernExplorer64.sys[/B][/COLOR] ( KernExplorer64+1277 )

Followup: MachineOwner
---------

And the other two indicates Stop 0x93.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 93[/B][/COLOR], {1514, fffff8a000001810, fffff8a0042cb450, 1}

Unable to load image \??\[COLOR=Red]C:\Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys[/COLOR], Win32 error 0n2
*** WARNING: [COLOR=Red]Unable to verify timestamp for KernExplorer64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red][B]Probably caused by : KernExplorer64.sys[/B][/COLOR] ( KernExplorer64+1277 )

Followup: MachineOwner
---------

Better you uninstall it. The version is there is of February, 2011.

 

[jburnssa]

I removed the program that was causing the issue and restarted driver verifier last night. I have a new dmp file from last night.

 

[jburnssa]

So, this BSOD happend yesterday after opening my vmware view client while running verifier. It happened again today when I opened the vmware client and runinng the verifier. I wasn't sure that it was this application at first, as I use it frequently to do remote work and have never had a blue screen while using it. How should I proceed, I need this application for work?

 

[Arc]

Which version of VMWare you are using? Try to update it to the very latest, or disable USB for the virtual machines.

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 224, fffffa800548e060, fffff8800599f139}

Unable to load image \SystemRoot\System32\Drivers\vmwvusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmwvusb.sys
*** ERROR: Module load completed but symbols could not be loaded for vmwvusb.sys
[COLOR=Red][B]Probably caused by : vmwvusb.sys[/B][/COLOR] ( vmwvusb+1139 )

Followup: MachineOwner
---------

It is VMware View Generic USB Driver, and it is of 2 years old in your system. Needs update.