BSOD while turning on computer, multiple minidumps accumulated

duketerm · 19 Jan 2016

Dear all,

First, thanks for all the help in advance. So I've gotten two BSODs in the last month since I've built this computer (most recently today; last one about 3 weeks ago). But when I went to use bluescreenviewer, there's been over 10 minidumps in the last month. So I've uploaded my stuff here hoping someone can take a look.

As a note, the BSOD seems to come on as soon as I turn on the computer, right after the blue windows logo comes up (I'm on Windows 10). I haven't gotten a BSOD while I've been using my computer or doing anything else.

Thanks so much again!

- Kent

axe0 · 20 Jan 2016

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

duketerm · 30 Jan 2016

Thanks for the reply axe0. I just got back from a trip, so sorry for the delay in posting the memtest results. I've attached the screenshot of my memtest results--seems like no errors after 10 passes.

I've also attached my most recent minidump of BSODs. Two happened recently--the most recent one on 1/29 was actually after I had updated my Nvidia drivers (which seemed to have been the cause of the BSOD on 1/28)?

Appreciate all the help, looking forward to your advice!

Edit: yet another fail on bootup--no BSOD, but computer had to reboot automatically. updated the newest log collector file. thanks!

axe0 · 02 Feb 2016

Ok, I would like to try driver verifier áfter the outdated drivers have been removed/updated.
Please update following drivers
Driver Reference Table - lvbflt64.sys
Driver Reference Table - lvrs64.sys
Driver Reference Table - lvuvc64.sys
Driver Reference Table - ISCTD64.sys
Driver Reference Table - iaStorA.sys

Code:

lvbflt64        Tue Oct 23 04:10:38 2012 (5085fc9e)    lvbflt64.sys
lvrs64        Tue Oct 23 04:11:24 2012 (5085fccc)        lvrs64.sys
lvuvc64        Tue Oct 23 04:12:08 2012 (5085fcf8)        lvuvc64.sys
ISCTD64        Tue Nov 27 20:52:34 2012 (50b51a02)    ISCTD64.sys
iaStorA        Fri Aug 02 03:39:52 2013 (51fb0de8)    iaStorA.sys

duketerm · 07 Feb 2016

axe0 said:

Ok, I would like to try driver verifier áfter the outdated drivers have been removed/updated.
Please update following drivers
Driver Reference Table - lvbflt64.sys
Driver Reference Table - lvrs64.sys
Driver Reference Table - lvuvc64.sys
Driver Reference Table - ISCTD64.sys
Driver Reference Table - iaStorA.sys

Code:

lvbflt64        Tue Oct 23 04:10:38 2012 (5085fc9e)    lvbflt64.sys
lvrs64        Tue Oct 23 04:11:24 2012 (5085fccc)        lvrs64.sys
lvuvc64        Tue Oct 23 04:12:08 2012 (5085fcf8)        lvuvc64.sys
ISCTD64        Tue Nov 27 20:52:34 2012 (50b51a02)    ISCTD64.sys
iaStorA        Fri Aug 02 03:39:52 2013 (51fb0de8)    iaStorA.sys

Thanks axe0,

I've updated the above drivers. I'm running the driver verifier as per (Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums), however, should I be checking multiple drivers (eg. I've only checked the "non-Microsoft" ones as described in the tutorial)?

Thanks a bunch!

axe0 · 08 Feb 2016

I hope you didn't forget to backup and create restore points :)

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

duketerm · 09 Feb 2016

Hey axe0,

So I've run the driver verifier for the last ~45 hours or so. Did not get a BSOD. I've attached the settings in the JPG attached to this reply. One driver never got loaded? Not sure what that means? I'll turn off driver verifier for now.

The thing I want to let you know is that: after you posted for me to update my drivers, I went to my motherboard's website to get the Intel RST and the Smartconnect drivers updated. I updated them, and then I subsequently got two BSODs within 3 hours. I uploaded the most recent crash dumps as well in this reply. I then went online to find the most recent Intel drivers and I then started the driver verifier and I guess it hasn't crashed since? I'll have to see what happens when I reboot, but if you have some spare time and can take a view at the two most recent crashes on 2/7 and if those crashes are anything notable, let me know.

Thanks so much!

axe0 · 10 Feb 2016

dump_*.sys drivers are created to provide disk access during crash dump file generation, nothing to worry about :)

You might want to revert back the display drivers to an early version until there is a newer version available, this one is known for being a little problematic.

Code:

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00141dce060, Physical Device Object of the stack
Arg3: ffffd000e0fb9990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0014107a010, The blocked IRP

2: kd> !irp ffffe0014107a010
Irp is active with 4 stacks 3 is current (= 0xffffe0014107a170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 ffffe00141dce060 00000000 fffff8014369d4f0-ffffd000e29718e0    
	       \Driver\pci	dxgkrnl!DpiFdoPowerCompletionRoutine
			Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 ffffe00141320040 00000000 fffff803a0383d88-ffffe00147a31670 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 \Driver\nvlddmkm	nt!PopRequestCompletion
			Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe00147a31670    

			Args: 00000000 00000000 00000000 00000000

2: kd> lmvm nvlddmkm
start             end                 module name
fffff801`45a80000 fffff801`466a4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Jan 23 01:25:59 2016 (56A2C897)
    CheckSum:         00BE5F37
    ImageSize:        00C24000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

duketerm · 13 Feb 2016

Thanks for the reply again. I've googled NVidia drivers and it appears that they have problems with Windows 10 in almost all versions? Is there a version that you think is more stable?

I've gotten two more BSODs--all during bootup of computer again. Attached are the minidumps--any thoughts?

Much appreciated again!

axe0 · 14 Feb 2016

Is there a version that you think is more stable?

Unfortunately I can't say, I have only a laptop with nothing from Nvidia.
I also don't get feedback from others who I suggested to to use earlier drivers.

Both crashes show drivers from the Windows File System in the stack, this might mean not much but it is better to test than ignore.

Diagnostics Test

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

Short Drive Self Test
Short generic
Long generic

If the short generic fails, no need for the long generic.

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

scan for errors, no quick scan but full scan
check the health,
benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

of the error scan,
make a screenshot of the health of every hard drive and post the screenshots,
post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.