BSOD on start-up before desktop

DjFIL · 17 Dec 2012

Wow... I really do appreciate the help. I'm just noticing that the file you're pointing me towards (the Intel one) isn't for my operating system. I would just like confirmation that you want me to try that file.

I've done the other two checks you suggested... I got the latest ASMedia driver installed, and confirmed that my OCZ SSD is running the latest firmware.

DjFIL · 17 Dec 2012

If I can get any further assistance. New crash dumps from this evening. Had computer turned off while at work. Come home and turn on... BSOD is back. Occurred twice. In safe mode... collected logs. Rebooted system back to normal mode, and it appears fine for now.

I looked further in to the driver you were suggesting, and within the read me it does mention Windows 7 (where the Intel site didn't mention Windows 7, and caused my concern). The driver has been installed now (after the logs were created) and can be seen in the screenshot.

Guessing it'll work fine while I play games for the night... and will report back tomorrow if BSOD is back.

Arc · 18 Dec 2012

Can you enable Driver verifier?

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

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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

DjFIL · 18 Dec 2012

Wow, that's a really cool feature. Crashed pretty quickly... looks like some ASUS driver (asupio.sys).

Not my first run-in with software issues from them... had their Network iControl software (from their AI Suite II) cause major (45-60 second) delays with my NIC grabbing a connection (even a static IP) before. Fixed later with an update... but this is more major then that.

Your suggestion for my next step?

Thanks again.

Arc · 18 Dec 2012

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 124, fffffa800b59fb30, fffff880019f98c8}

*** WARNING: Unable to verify timestamp for AsUpIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsUpIO.sys
Probably caused by : AsUpIO.sys ( AsUpIO+18c8 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000124, Handle value being referenced.
Arg3: fffffa800b59fb30, Address of the current process.
Arg4: fffff880019f98c8, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  PEUpdater.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000331a3dc to fffff80002e93fc0

STACK_TEXT:  
fffff880`0a38e198 fffff800`0331a3dc : 00000000`000000c4 00000000`000000f6 00000000`00000124 fffffa80`0b59fb30 : nt!KeBugCheckEx
fffff880`0a38e1a0 fffff800`0332fae4 : 00000000`00000124 fffffa80`0b59fb30 00000000`00000004 00000000`000001f0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a38e1e0 fffff800`030e7000 : 00000000`00000000 fffff880`0a38e418 fffff880`0a38e500 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`0a38e2c0 fffff800`031a92f6 : 0000007f`ffffff00 00000000`00000002 fffffa80`0673f550 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x212de
fffff880`0a38e390 fffff800`02e93253 : 00000000`00000124 fffffa80`0baef060 fffff880`0a38e688 00000000`00000000 : nt!NtMapViewOfSection+0x215
fffff880`0a38e460 fffff800`02e8f810 : fffff800`033200e1 00000000`00000000 fffff880`0a38eae0 00000000`c0000002 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a38e668 fffff800`033200e1 : 00000000`00000000 fffff880`0a38eae0 00000000`c0000002 fffff800`0332f878 : nt!KiServiceLinkage
fffff880`0a38e670 fffff880`019f98c8 : 00000000`00000000 00000000`00000002 00000000`00000001 fffff980`15aacfe0 : nt!VfZwMapViewOfSection+0xb1
fffff880`0a38e6e0 00000000`00000000 : 00000000`00000002 00000000`00000001 fffff980`15aacfe0 00000000`007f0000 : AsUpIO+0x18c8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AsUpIO+18c8
fffff880`019f98c8 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  AsUpIO+18c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AsUpIO

IMAGE_NAME:  AsUpIO.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c57835f

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+18c8

BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+18c8

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

0: kd> lmvm AsUpIO
start             end                 module name
fffff880`019f8000 fffff880`019ff000   AsUpIO   T (no symbols)           
    Loaded symbol image file: AsUpIO.sys
    Image path: \SystemRoot\SysWow64\drivers\AsUpIO.sys
    Image name: AsUpIO.sys
    Timestamp:        Tue Aug 03 08:17:59 2010 (4C57835F)
    CheckSum:         0000BD68
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Had I been there in your place, I would not have used ASUS hardware monitoring software.

Better you Uninstall it:

Code:

Start Menu\Programs\ASUS\AI Suite II

DjFIL · 18 Dec 2012

Totally done with the extra ASUS software. Uninstalled.

File is still found in c:\windows\syswow64\drivers\... is that of any concern since the software it is uninstalled?

Should I run verifier to stress test again... or just give it regular time to see if it reoccurs?

Arc · 18 Dec 2012

Delete that one manually ... also search in system32\drivers ...

Disable DV now. Run it normally. If it crashes again, enable DV again. But it may not, as both the DV enabled crashes indicated the exactly same thing.

DjFIL · 18 Dec 2012

Ok. Thanks again. I'll be back in a day or so... or upon the next BSOD if that occurs sooner.

Cheers.

DjFIL · 18 Dec 2012

Sad to say, it's back this morning. First crash I noticed 'srv2.sys' mentioned. Not sure what to do about that. Second crash was random. Back to safe mode and collected the first set of logs.

Back in normal mode. Enabled Driver Verifier (all non-MS drivers). After first reboot, minute or so after desktop has loaded we get another crash... didn't catch the exact driver. After another reboot... no crash at all (with Driver Verifier still enabled). Disabled verifier... rebooted.. re-enabled verifier... still no crash. Now disabled once again. Second set of logs collected.

Thanks.

Arc · 18 Dec 2012

One crash indicates to Intel(R) 82579V Gigabit Network Connection driver. Though it is not very old.

Code:

lmvm e1c62x64
start             end                 module name
fffff880`04550000 fffff880`045c9000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Sat Aug 11 04:14:15 2012 (50258EBF)
    CheckSum:         000829CE
    ImageSize:        00079000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Still search if any updates are available, in Intel Download Center. BTW, what antivirus do you use?

Scan the system for possible virus infection.

Do some disc checks, too.

Update your SSD's Firmware (Skip it, if it is not a ssd)
Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.