[BSOD] Windows 8 DPC_WATCHDOG_VIOLATIONS

V

VindicoAtrum

Member
Joined
Dec 10, 2012
Posts
5
Windows 8, newly installed from Dreamspark.32-bit.
Upgraded from windows 7 32-bit. It's probably worth saying that before the upgrade I had zero issues, it was stable for months. I installed that version of windows 7.
Mobo/HD are few years old now. graphics/ram 1 year.
Windows 8 was installed few days ago.

I've ran extensive memory testing, and it's given me no errors at all so far. Both with memtest86 and the windows memory diagnostic tool. Also ran driver verifier, and that's all fine now, after I've reinstalled sound/graphics drivers up to date.

· CPU - AMD Athlon II x4 645 processor 4 at ~3.1ghz.
· Video Card - Nvidia gtx 550 ti.
· MotherBoard - I have no idea right now. Was in the system with the processor when I bought it though.
· Power Supply - brand & wattage - Can't remember, it's not the one I got with the system. It's 570 watt if I recall rightly.
Ok, so a few points. Has ran windows 7 for months now, perfectly stable with no issues. Upgraded to 8 and my sound drivers went caputt. Updated those and fixed the sound immediately. Had DPC_WATCHDOG_VIOLATIONS since. Uninstalled sound drivers, still get the error. Uninstall everything to do with sound (drivers/card) and still get the errors. Uninstalled graphics card, still get errors. Re-install, update drivers, still the same error. Googled excessively, the information on this error is useless for a typical user like me. It's worth nothing - I can do anything trivial without getting this error. Browsing/music/working is all fine. As soon as I start gaming, i'll be lucky to get 5 minutes before good old DPC_WATCHDOG_VIOLATION. Files are attached, any ideas?

View attachment PerfmonJcGriffFolder.rar
 
All crashes center around your NVIDIA storage drivers. The 0x133 have those as the third party drivers at the top of the memory stack, and the 0x9F are indicating an issue during hibernating sequences due to a RAID storage driver which probably means the NVIDIA storage drivers are interfering with hibernation. I do note that the driver is a bit old for a Windows 8 system.

nvstor.sys Mon Sep 12 17:22:00 2011 (4E6E9418)
nVidia Storage Drivers
http://www.carrona.org/drivers/driver.php?id=nvstor.sys​

I see no updates to that driver within your BIOSTAR N68S3+ support page: N68S3+ Ver. 6.x.

I would recommend uninstalling the driver through device manager, selecting the option to Delete the driver software for this device, and then restarting the system to let Windows install default drivers for it. More specific steps to do so follow:

  1. Click the lower left corner to open the Start Screen.

  2. Type devmgmt.msc to get to the Device Manager icon.

  3. Click on devmgmt.msc to open Device Manager.

  4. Expand IDE ATA/ATAPI Controllers

  5. Right Click each NVIDIA device and do the following steps:
    • Click Uninstall

    • Put a tick to Delete the driver software for this device.

    • Click OK

    • Click Yes in any dialog boxes that open

    • Restart your computer and let Windows install the appropriate drivers during the next boot.

Code: 
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\121012-21512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x8141f000 PsLoadedModuleList = 0x81609de8
Debug session time: Mon Dec 10 05:58:21.993 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:50.731
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
Probably caused by : ntkrpamp.exe ( nt! ?? ::FNODOBFM::`string'+ea93 )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
82e80890  815a0cab nt! ?? ::FNODOBFM::`string'+0xea93
82e808e8  814aa49b nt!KeUpdateRunTime+0x4c
82e808fc  814aa49b nt!KeUpdateRunTime+0x4c
82e80924  819c9fd4 hal!HalpTimerClockInterruptCommon+0x3c
82e80928  819d11d4 hal!HalpTscQueryCounter+0x2
82e80940  819db5fd hal!HalpTimerClockInterrupt+0x199
82e80950  819d11d4 hal!HalpTscQueryCounter+0x2
82e80970  814aa49b nt!KeUpdateRunTime+0x4c
82e80984  814aa49b nt!KeUpdateRunTime+0x4c
82e809b4  819d11d4 hal!HalpTscQueryCounter+0x2
82e809c0  819c544b hal!HalpTimerStallExecutionProcessor+0x139
82e809d8  819dc4bf hal!READ_PORT_UCHAR+0x7
82e80a20  819c44d4 hal!KeStallExecutionProcessor+0x14e
82e80a3c  819dc4bf hal!READ_PORT_UCHAR+0x7
82e80a48  822ea4eb storport!StorPortReadPortUchar+0xe
82e80a54  822bdaed[color=red][b]*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys[/b][/color]
82e80a64  822b9676 nvstor+0xf676
82e80a6c  822af70e nvstor+0x570e
82e80a80  822aed52 nvstor+0x4d52
82e80a90  822aeebe nvstor+0x4ebe
82e80aa4  822b2aa1 nvstor+0x8aa1
82e80acc  822af5f8 nvstor+0x55f8
82e80aec  822ad302 nvstor+0x3302
82e80af4  822aef5b nvstor+0x4f5b
82e80b10  822ad5ca nvstor+0x35ca
82e80b30  822b99bd nvstor+0xf9bd
82e80b5c  822bc239 nvstor+0x12239
82e80b6c  8147b4ab nt!KiExecuteAllDpcs+0x1f2
82e80b7c  822b9956 nvstor+0xf956
82e80ba0  822b9956 nvstor+0xf956
82e80bd0  822bc226 nvstor+0x12226
82e80bdc  814ab56f nt!PpmIdleExecuteTransition+0x755
82e80be8  814ab5a0 nt!PpmIdleExecuteTransition+0x786
82e80bf8  819c41ea hal!KeQueryPerformanceCounter+0xbe
82e80c08  814e5beb nt!KeGetNextTimerExpirationDueTime+0x2e
82e80c24  8147b0e6 nt!KiRetireDpcList+0xed
82e80c78  822bc226 nvstor+0x12226
82e80cc0  81557e5b nt!PpmIdlePrepare+0xca
82e80ce0  81558108 nt!PoIdle+0x213
82e80d08  81558180 nt!PoIdle+0x28b
82e80d44  8158eeb4 nt!KiIdleLoop+0x38
82e80d54  81510182 nt!KiGetXSaveSupportedFeatures+0x23
82e80d84  8163f5e7 nt!KiInitializeXSave+0x78
82e80d98  8163f62c nt!KiInitializeXSave+0xbd
82e80dac  8158f020 nt!KiThreadStartup
82e80db4  8158ee7c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\121012-20982-01.dmp]
Could not match Dump File signature - invalid file format
Could not open dump file [121012-20982-01.dmp], Win32 error 0n87
    "The parameter is incorrect."
Debuggee initialization failed, Win32 error 0n87
    "The parameter is incorrect."
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\121012-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81672000 PsLoadedModuleList = 0x8185cde8
Debug session time: Sun Dec  9 18:38:34.827 2012 (UTC - 7:00)
System Uptime: 1 days 3:29:01.566
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {4, 12c, 88c31d40, 80b93b54}
Can't retrieve thread context, Win32 error 0n30
Probably caused by : storport.sys ( storport!RaidBusEnumeratorIssueSynchronousRequest+186 )
0: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
a7b87420  816a7818 nt!KiCommitThreadWait+0x280
a7b87460  818494c8 nt!ExNode0+0x108
a7b8746c  81cb362b storport!RaUnitScsiIrp+0x627
a7b87478  81cb3659 storport!RaUnitScsiIrp+0x655
a7b87494  816a6eeb nt!KeWaitForSingleObject+0x269
a7b874c0  8162c796 hal!KfLowerIrql+0x2c
a7b874d4  816aae2b nt!KeReleaseInStackQueuedSpinLock+0x3a
a7b874d8  8184d4e0 nt!NonPagedPoolDescriptor+0xb60
a7b87500  81cc1884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
a7b87530  81cc1884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
a7b8755c  81755f8d nt!MiFindContiguousMemoryInPool+0x56
a7b87564  81755fa3 nt!MiFindContiguousMemoryInPool+0x6c
a7b8758c  8171cf2a nt!MiAllocateContiguousMemory+0x263
a7b875a8  816e7992 nt!IoReuseIrp+0x79
a7b875bc  81837308 nt!ExFreePoolWithTag+0x2f3
a7b875cc  81838303 nt!ExAllocatePoolWithTag+0xd3
a7b875d4  8184c980 nt!NonPagedPoolDescriptor
a7b87620  81040001*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
a7b87648  81cc2e6c storport!RaidBusEnumeratorIssueReportLuns+0x2b
a7b87650  81cc2e79 storport!RaidBusEnumeratorIssueReportLuns+0x38
a7b87670  81cc2add storport!RaidBusEnumeratorGetLunListFromTarget+0x41
a7b87698  81cc236e storport!RaidBusEnumeratorGetLunList+0x43
a7b87718  81cc1415 storport!RaidAdapterEnumerateBus+0xb5
a7b8784c  81cbbe4d storport!RaidIsAdapterControlSupported+0x4a
a7b87858  81cc1f69 storport!RaidAdapterRescanBus+0x7e
a7b878b4  9258dfa1Unable 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
a7b878cc  81cc1c43 storport!RaidAdapterQueryDeviceRelationsIrp+0x9b
a7b878e8  925a352d nvlddmkm+0x19252d
a7b87904  92561e6d nvlddmkm+0x150e6d
a7b87934  81cbfa03 storport!RaidAdapterPnpIrp+0x193
a7b8795c  8170ce50 nt!KeReleaseMutex+0x12d
a7b87984  81cb75ac storport!RaDriverPnpIrp+0x6e
a7b879a0  816aaa7c nt!IofCallDriver+0x3f
a7b879bc  818da19f nt!PnpAsynchronousCall+0x94
a7b879d8  818da0cf nt!PnpQueryDeviceRelations+0x67
a7b879e0  817571d7 nt!PnpDeviceCompletionRoutine
a7b87a1c  816e7121 nt!PopFxActivateDevice+0x8e
a7b87a3c  818da35c nt!PipEnumerateDevice+0x119
a7b87a44  817571d7 nt!PnpDeviceCompletionRoutine
a7b87a54  818627f8 nt!PnpSpinLock
a7b87a64  818d8ebc nt!PnpProcessAssignResources+0x5f
a7b87a90  8192d726 nt!PipProcessDevNodeTree+0x26b
a7b87ab0  8162c995 hal!HalpDispatchSoftwareInterrupt+0x4f
a7b87aec  8162c796 hal!KfLowerIrql+0x2c
a7b87b18  9258dfa1 nvlddmkm+0x17cfa1
a7b87b20  925a34ba nvlddmkm+0x1924ba
a7b87b4c  925a352d nvlddmkm+0x19252d
a7b87b68  8162c76a hal!KfLowerIrql
a7b87b7c  8162c796 hal!KfLowerIrql+0x2c
a7b87b90  8170ce50 nt!KeReleaseMutex+0x12d
a7b87bc4  8162c796 hal!KfLowerIrql+0x2c
a7b87be0  8162c995 hal!HalpDispatchSoftwareInterrupt+0x4f
a7b87bec  816d59e7 nt!ExpReleaseResourceForThreadLite+0x264
a7b87c00  8162c702 hal!HalpInterruptEnumerateUnmaskedInterrupts+0xf6
a7b87c08  8162c796 hal!KfLowerIrql+0x2c
a7b87c0c  81864e18 nt!IopDeviceTreeLock+0x18
a7b87c1c  816a7844 nt!KiCommitThreadWait+0x2ac
a7b87c2c  816d52eb nt!ExAcquireResourceSharedLite+0x184
a7b87c4c  81930de7 nt!PiMarkDeviceTreeForReenumerationWorker+0x1c
a7b87c58  81864e34 nt!IopDeviceTreeLock+0x34
a7b87c6c  81930e1c nt!PipForAllChildDeviceNodes+0x21
a7b87c78  816d576a nt!ExReleaseResourceLite+0xd
a7b87c7c  81864e00 nt!IopDeviceTreeLock
a7b87c90  81920547 nt!PiProcessReenumeration+0x75
a7b87cb8  8162c796 hal!KfLowerIrql+0x2c
a7b87ccc  81714338 nt!PnpDeviceActionWorker+0x116
a7b87cd0  818494b8 nt!ExNode0+0xf8
a7b87cd8  818493c0 nt!ExNode0
a7b87cf0  816f3725 nt!IopProcessWorkItem+0x8f
a7b87d00  9255e0ac nvlddmkm+0x14d0ac
a7b87d0c  816f37f9 nt!ExpWorkerThread+0xb6
a7b87d10  818494b8 nt!ExNode0+0xf8
a7b87d20  816f3854 nt!ExpWorkerThread+0x111
a7b87d3c  81714222 nt!PnpDeviceActionWorker
a7b87d44  818627e0 nt!PnpDeviceEnumerationWorkItem
a7b87d48  818627e0 nt!PnpDeviceEnumerationWorkItem
a7b87d68  8162c796 hal!KfLowerIrql+0x2c
a7b87d78  81736415 nt!PspSystemThreadStartup+0x4a
a7b87da4  81779bb9 nt!_except_handler4
a7b87db4  817e2039 nt!KiThreadStartup+0x19
a7b87db8  816f3747 nt!ExpWorkerThread
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-22354-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81257000 PsLoadedModuleList = 0x81441de8
Debug session time: Sat Dec  8 14:48:28.523 2012 (UTC - 7:00)
System Uptime: 0 days 2:23:47.261
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
Probably caused by : ntkrpamp.exe ( nt! ?? ::FNODOBFM::`string'+ea93 )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
a5d25000  ????????                             ????
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-35100-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c14000 PsLoadedModuleList = 0x81dfede8
Debug session time: Sat Dec  8 12:23:59.123 2012 (UTC - 7:00)
System Uptime: 0 days 4:36:21.861
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {4, 12c, 857db040, 811f5b54}
Can't retrieve thread context, Win32 error 0n30
Probably caused by : storport.sys ( storport!RaidBusEnumeratorIssueSynchronousRequest+186 )
0: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
8bb31420  81c49818 nt!KiCommitThreadWait+0x280
8bb31460  81deb4c8 nt!ExNode0+0x108
8bb3146c  82ac962b storport!RaUnitScsiIrp+0x627
8bb31478  82ac9659 storport!RaUnitScsiIrp+0x655
8bb31494  81c48eeb nt!KeWaitForSingleObject+0x269
8bb314c0  821b1796 hal!KfLowerIrql+0x2c
8bb314d4  81c4ce2b nt!KeReleaseInStackQueuedSpinLock+0x3a
8bb314d8  81def4e0 nt!NonPagedPoolDescriptor+0xb60
8bb31500  82ad7884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
8bb31530  82ad7884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
8bb3155c  81cf7f8d nt!MiFindContiguousMemoryInPool+0x56
8bb31564  81cf7fa3 nt!MiFindContiguousMemoryInPool+0x6c
8bb31594  81dee900 nt!WmipRegLookaside+0x80
8bb315a0  821b1796 hal!KfLowerIrql+0x2c
8bb315a8  81dee980 nt!NonPagedPoolDescriptor
8bb315ac  81dd9308 nt!ExFreePoolWithTag+0x2f3
8bb315bc  81dd9308 nt!ExFreePoolWithTag+0x2f3
8bb315cc  81dda303 nt!ExAllocatePoolWithTag+0xd3
8bb315d4  81dee980 nt!NonPagedPoolDescriptor
8bb31620  82040001 nt! ?? ::NNGAKEGL::`string'+0x14f70
8bb31648  82ad8e6c storport!RaidBusEnumeratorIssueReportLuns+0x2b
8bb31650  82ad8e79 storport!RaidBusEnumeratorIssueReportLuns+0x38
8bb31670  82ad8add storport!RaidBusEnumeratorGetLunListFromTarget+0x41
8bb31698  82ad836e storport!RaidBusEnumeratorGetLunList+0x43
8bb31718  82ad7415 storport!RaidAdapterEnumerateBus+0xb5
8bb3184c  82ad1e4d storport!RaidIsAdapterControlSupported+0x4a
8bb31858  82ad7f69 storport!RaidAdapterRescanBus+0x7e
8bb318b4  90db8fa1Unable 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
8bb318cc  82ad7c43 storport!RaidAdapterQueryDeviceRelationsIrp+0x9b
8bb318e8  90dce52d nvlddmkm+0x19252d
8bb31904  90d8ce6d nvlddmkm+0x150e6d
8bb31934  82ad5a03 storport!RaidAdapterPnpIrp+0x193
8bb3195c  81caee50 nt!KeReleaseMutex+0x12d
8bb31984  82acd5ac storport!RaDriverPnpIrp+0x6e
8bb319a0  81c4ca7c nt!IofCallDriver+0x3f
8bb319bc  81e7c19f nt!PnpAsynchronousCall+0x94
8bb319d8  81e7c0cf nt!PnpQueryDeviceRelations+0x67
8bb319e0  81cf91d7 nt!PnpDeviceCompletionRoutine
8bb31a1c  81c89121 nt!PopFxActivateDevice+0x8e
8bb31a3c  81e7c35c nt!PipEnumerateDevice+0x119
8bb31a44  81cf91d7 nt!PnpDeviceCompletionRoutine
8bb31a54  81e047f8 nt!PnpSpinLock
8bb31a64  81e7aebc nt!PnpProcessAssignResources+0x5f
8bb31a90  81ecf726 nt!PipProcessDevNodeTree+0x26b
8bb31ab0  821b1995 hal!HalpDispatchSoftwareInterrupt+0x4f
8bb31aec  81c49844 nt!KiCommitThreadWait+0x2ac
8bb31af8  81c49858 nt!KiCommitThreadWait+0x2c0
8bb31b24  821b1796 hal!KfLowerIrql+0x2c
8bb31b50  90db8fa1 nvlddmkm+0x17cfa1
8bb31b58  90dce4ba nvlddmkm+0x1924ba
8bb31b84  90dce52d nvlddmkm+0x19252d
8bb31ba0  821b176a hal!KfLowerIrql
8bb31bb4  821b1796 hal!KfLowerIrql+0x2c
8bb31bc0  81dee980 nt!NonPagedPoolDescriptor
8bb31bc4  81dd9308 nt!ExFreePoolWithTag+0x2f3
8bb31be0  821b1995 hal!HalpDispatchSoftwareInterrupt+0x4f
8bb31bec  81c779e7 nt!ExpReleaseResourceForThreadLite+0x264
8bb31c00  821b1702 hal!HalpInterruptEnumerateUnmaskedInterrupts+0xf6
8bb31c08  821b1796 hal!KfLowerIrql+0x2c
8bb31c0c  81e06e18 nt!IopDeviceTreeLock+0x18
8bb31c1c  81c49844 nt!KiCommitThreadWait+0x2ac
8bb31c2c  81c772eb nt!ExAcquireResourceSharedLite+0x184
8bb31c4c  81ed2de7 nt!PiMarkDeviceTreeForReenumerationWorker+0x1c
8bb31c58  81e06e34 nt!IopDeviceTreeLock+0x34
8bb31c6c  81ed2e1c nt!PipForAllChildDeviceNodes+0x21
8bb31c78  81c7776a nt!ExReleaseResourceLite+0xd
8bb31c7c  81e06e00 nt!IopDeviceTreeLock
8bb31c90  81ec2547 nt!PiProcessReenumeration+0x75
8bb31cb8  821b1796 hal!KfLowerIrql+0x2c
8bb31ccc  81cb6338 nt!PnpDeviceActionWorker+0x116
8bb31cd0  81deb4b8 nt!ExNode0+0xf8
8bb31cd8  81deb3c0 nt!ExNode0
8bb31cf0  81c95725 nt!IopProcessWorkItem+0x8f
8bb31d00  90d890ac nvlddmkm+0x14d0ac
8bb31d0c  81c957f9 nt!ExpWorkerThread+0xb6
8bb31d10  81deb4b8 nt!ExNode0+0xf8
8bb31d20  81c95854 nt!ExpWorkerThread+0x111
8bb31d3c  81cb6222 nt!PnpDeviceActionWorker
8bb31d44  81e047e0 nt!PnpDeviceEnumerationWorkItem
8bb31d48  81e047e0 nt!PnpDeviceEnumerationWorkItem
8bb31d68  821b1796 hal!KfLowerIrql+0x2c
8bb31d78  81cd8415 nt!PspSystemThreadStartup+0x4a
8bb31da4  81d1bbb9 nt!_except_handler4
8bb31db4  81d84039 nt!KiThreadStartup+0x19
8bb31db8  81c95747 nt!ExpWorkerThread
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-75520-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80e65000 PsLoadedModuleList = 0x81050e68
Debug session time: Sat Dec  8 07:29:05.966 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:27.700
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+14da2 )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
81e80958  80f8919d nt! ?? ::FNODOBFM::`string'+0xead3
81e809a0  8b85590e ndis!ndisMiniportIsr+0xae
81e809c8  80e8fa23 nt!KeUpdateRunTime+0x4c
81e809f0  80e2cfd4 hal!HalpTimerClockInterruptCommon+0x3c
81e809f4  8100a477 nt!KxWaitForLockOwnerShip+0x21
81e80a0c  80e3e60d hal!HalpTimerClockInterrupt+0x199
81e80a1c  8100a477 nt!KxWaitForLockOwnerShip+0x21
81e80a38  80e1f796 hal!KfLowerIrql+0x2c
81e80a4c  80e91509 nt!KeInsertQueueDpc+0x1b0
81e80a80  8100a477 nt!KxWaitForLockOwnerShip+0x21
81e80a94  816cd7c4 storport!StorPortNotification+0x8a
81e80aa0  816cf15a storport!StorPortWriteRegisterUlong+0x11
81e80aac  816bbb89 nvstor+0x14b89
81e80ab4  816bbda2 nvstor+0x14da2
81e80ad4  816aae91 nvstor+0x3e91
81e80afc  816aa6c0 nvstor+0x36c0
81e80b10  816aa5ca nvstor+0x35ca
81e80b30  816b69bd nvstor+0xf9bd
81e80b5c  816b9239 nvstor+0x12239
81e80b6c  80febd59 nt!KiExecuteAllDpcs+0x1f2
81e80b7c  816b6956 nvstor+0xf956
81e80ba0  816b6956 nvstor+0xf956
81e80bd0  816b9226 nvstor+0x12226
81e80bdc  80e90af7 nt!PpmIdleExecuteTransition+0x755
81e80be8  80e90b28 nt!PpmIdleExecuteTransition+0x786
81e80bf8  80e271ea hal!KeQueryPerformanceCounter+0xbe
81e80c08  80ece361 nt!KeGetNextTimerExpirationDueTime+0x2e
81e80c24  80feb9a3 nt!KiRetireDpcList+0xed
81e80c78  816b9226 nvstor+0x12226
81e80cc0  80f3fa2d nt!PpmIdlePrepare+0xca
81e80ce0  80f3fcd2 nt!PoIdle+0x213
81e80d08  80f3fd4a nt!PoIdle+0x28b
81e80d44  80f76f94 nt!KiIdleLoop+0x38
81e80d54  80ef6aca nt!KiGetXSaveSupportedFeatures+0x23
81e80d84  81086377 nt!KiInitializeXSave+0x78
81e80d98  810863bc nt!KiInitializeXSave+0xbd
81e80dac  80f77100 nt!KiThreadStartup
81e80db4  80f76f5c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-31824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81019000 PsLoadedModuleList = 0x81204e68
Debug session time: Sat Dec  8 07:24:18.629 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:32.364
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+13aed )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
82080918  8113d19d nt! ?? ::FNODOBFM::`string'+0xead3
82080950  815cc1e4 hal!HalpTscQueryCounter+0x2
82080984  81043a23 nt!KeUpdateRunTime+0x4c
820809ac  815c4fd4 hal!HalpTimerClockInterruptCommon+0x3c
820809b0  815d74cf hal!READ_PORT_UCHAR+0x7
820809c8  815d660d hal!HalpTimerClockInterrupt+0x199
820809cc  815c0402 hal!HalpTimerStallExecutionProcessor+0xf0
820809d8  815d74cf hal!READ_PORT_UCHAR+0x7
82080a3c  815d74cf hal!READ_PORT_UCHAR+0x7
82080a48  818c54eb storport!StorPortReadPortUchar+0xe
82080a54  81898aed nvstor+0x13aed
82080a64  81894676 nvstor+0xf676
82080a70  8188a6f5 nvstor+0x56f5
82080a80  81889d52 nvstor+0x4d52
82080a90  81889ebe nvstor+0x4ebe
82080aa4  8188daa1 nvstor+0x8aa1
82080acc  8188a5f8 nvstor+0x55f8
82080aec  81888302 nvstor+0x3302
82080af4  81889f5b nvstor+0x4f5b
82080b10  818885ca nvstor+0x35ca
82080b30  818949bd nvstor+0xf9bd
82080b5c  81897239 nvstor+0x12239
82080b6c  8119fd59 nt!KiExecuteAllDpcs+0x1f2
82080b7c  81894956 nvstor+0xf956
82080ba0  81894956 nvstor+0xf956
82080bd0  81897226 nvstor+0x12226
82080bdc  81044af7 nt!PpmIdleExecuteTransition+0x755
82080be8  81044b28 nt!PpmIdleExecuteTransition+0x786
82080bf8  815bf1ea hal!KeQueryPerformanceCounter+0xbe
82080c08  81082361 nt!KeGetNextTimerExpirationDueTime+0x2e
82080c24  8119f9a3 nt!KiRetireDpcList+0xed
82080c78  81897226 nvstor+0x12226
82080cc0  810f3a2d nt!PpmIdlePrepare+0xca
82080ce0  810f3cd2 nt!PoIdle+0x213
82080d08  810f3d4a nt!PoIdle+0x28b
82080d44  8112af94 nt!KiIdleLoop+0x38
82080d54  810aaaca nt!KiGetXSaveSupportedFeatures+0x23
82080d84  8123a377 nt!KiInitializeXSave+0x78
82080d98  8123a3bc nt!KiInitializeXSave+0xbd
82080dac  8112b100 nt!KiThreadStartup
82080db4  8112af5c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-150447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81a12000 PsLoadedModuleList = 0x81bfcde8
Debug session time: Sat Dec  8 07:10:21.026 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:48.764
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+14da2 )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
83080958  81b93cab nt! ?? ::FNODOBFM::`string'+0xea93
830809a0  808537b4 ndis!ndisMiniportIsr+0xae
830809c8  81a9d49b nt!KeUpdateRunTime+0x4c
830809f0  81fbcfd4 hal!HalpTimerClockInterruptCommon+0x3c
830809f4  81ab2525 nt!KxWaitForLockOwnerShip+0x1f
83080a0c  81fce5fd hal!HalpTimerClockInterrupt+0x199
83080a1c  81ab2525 nt!KxWaitForLockOwnerShip+0x1f
83080a38  81faf796 hal!KfLowerIrql+0x2c
83080a4c  81a9ef7d nt!KeInsertQueueDpc+0x1b0
83080a80  81ab2525 nt!KxWaitForLockOwnerShip+0x1f
83080a94  806a87c4 storport!StorPortNotification+0x8a
83080aa0  806aa15a storport!StorPortWriteRegisterUlong+0x11
83080aac  80696b89 nvstor+0x14b89
83080ab4  80696da2 nvstor+0x14da2
83080ad4  80685e91 nvstor+0x3e91
83080afc  806856c0 nvstor+0x36c0
83080b10  806855ca nvstor+0x35ca
83080b30  806919bd nvstor+0xf9bd
83080b5c  80694239 nvstor+0x12239
83080b6c  81a6e4ab nt!KiExecuteAllDpcs+0x1f2
83080b7c  80691956 nvstor+0xf956
83080ba0  80691956 nvstor+0xf956
83080bd0  80694226 nvstor+0x12226
83080bdc  81a9e56f nt!PpmIdleExecuteTransition+0x755
83080be8  81a9e5a0 nt!PpmIdleExecuteTransition+0x786
83080bf8  81fb71ea hal!KeQueryPerformanceCounter+0xbe
83080c08  81ad8beb nt!KeGetNextTimerExpirationDueTime+0x2e
83080c24  81a6e0e6 nt!KiRetireDpcList+0xed
83080c78  80694226 nvstor+0x12226
83080cc0  81b4ae5b nt!PpmIdlePrepare+0xca
83080ce0  81b4b108 nt!PoIdle+0x213
83080d08  81b4b180 nt!PoIdle+0x28b
83080d44  81b81eb4 nt!KiIdleLoop+0x38
83080d54  81b03182 nt!KiGetXSaveSupportedFeatures+0x23
83080d84  81c325e7 nt!KiInitializeXSave+0x78
83080d98  81c3262c nt!KiInitializeXSave+0xbd
83080dac  81b82020 nt!KiThreadStartup
83080db4  81b81e7c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-38111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80e11000 PsLoadedModuleList = 0x80ffbde8
Debug session time: Sat Dec  8 07:07:11.194 2012 (UTC - 7:00)
System Uptime: 0 days 0:33:00.932
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
Probably caused by : storport.sys ( storport!RaidpAdapterTimerDpcRoutine+55 )
0: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
a982c000  ????????                             ????
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120812-21184-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x8181b000 PsLoadedModuleList = 0x81a05de8
Debug session time: Sat Dec  8 06:33:22.658 2012 (UTC - 7:00)
System Uptime: 1 days 10:41:35.397
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck D1, {d789d1c2, 2, 0, 8068650d}
Unable to load image \SystemRoot\System32\drivers\nvstor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+750d )
0: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
80db6038  818a1e2f nt!RaspAntiAlias+0xe0
80db6068  818a2693 nt!GxpWriteFrameBufferPixels+0xe3
80db607c  818a26c8 nt!GxpWriteFrameBufferPixels+0x118
80db6098  818a217a nt!BgpRasPrintGlyph+0x246
80db60d0  819f9740 nt!BcpCharacterCache
80db60f8  81db0829 hal!IoFlushAdapterBuffersV2+0x6f
80db611c  81daef29 hal!IoFlushAdapterBuffers+0x3f
80db613c  9162d983 dump_diskdump!FreeScatterGatherList+0x47
80db6158  9162fbe6 dump_diskdump!StorPortReadRegisterUlong+0xe
80db6164  90d6219aUnable to load image \SystemRoot\System32\Drivers\dump_nvstor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_nvstor.sys
80db6178  90d621cc dump_nvstor+0x41cc
80db617c  9162fbe6 dump_diskdump!StorPortReadRegisterUlong+0xe
80db61e4  81dc13eb hal!HalpTimerStallExecutionProcessor+0xd9
80db61f0  81dc144b hal!HalpTimerStallExecutionProcessor+0x139
80db6208  9162fb14 dump_diskdump!StorPortReadPortUchar+0xe
80db6250  81dc04d4 hal!KeStallExecutionProcessor+0x14e
80db6290  90d7021c dump_nvstor+0x1221c
80db629c  9162dbb0 dump_diskdump!ExecuteSrb+0xf0
80db62bc  9162def3 dump_diskdump!DiskDumpWrite+0x177
80db62f4  82d72b50 crashdmp!CrashdmpWriteRoutine+0x38
80db6300  82d772b8 crashdmp!Context+0x20
80db630c  82d70da4 crashdmp!WritePageSpanToDisk+0x248
80db631c  82d772b8 crashdmp!Context+0x20
80db6324  82d772b8 crashdmp!Context+0x20
80db6330  82d72bd4 crashdmp!CrashdmpWritePendingRoutine
80db6338  82d72b18 crashdmp!CrashdmpWriteRoutine
80db63d4  82d709d0 crashdmp!WriteBitmapDump+0x15a
80db63e4  82d772b8 crashdmp!Context+0x20
80db644c  82d74750 crashdmp!_except_handler4
80db645c  82d706ea crashdmp!DumpWrite+0x1dc
80db6460  82d772b8 crashdmp!Context+0x20
80db6464  8193b973 nt!KiBugCheckProgress
80db646c  8193b973 nt!KiBugCheckProgress
80db6488  82d6f8ca crashdmp!CrashdmpWrite+0x90
80db648c  8193b973 nt!KiBugCheckProgress
80db6494  8193b973 nt!KiBugCheckProgress
80db649c  82d77300 crashdmp!Context+0x68
80db64a4  819327a2 nt!IoWriteCrashDump+0x3b1
80db64a8  82d77300 crashdmp!Context+0x68
80db64ac  8193b973 nt!KiBugCheckProgress
80db64b4  81a1d404 nt!KiInitialPCR+0x404
80db64dc  8193b973 nt!KiBugCheckProgress
80db64e8  81dcc21b hal!HalSocRequestApi+0x189
80db64f4  81932258 nt!IoSetDumpRange
80db64f8  819321c7 nt!IoFreeDumpRange
80db650c  81a0b470 nt!KeBugCheckAddPagesCallbackListHead
80db6520  81a0b470 nt!KeBugCheckAddPagesCallbackListHead
80db6534  8068650d nvstor+0x750d
80db654c  81922bb9 nt!_except_handler4
80db655c  8193b664 nt!KeBugCheck2+0x761
80db6570  8068650d nvstor+0x750d
80db6578  81a2c0c0 nt!KiInitialThread
80db657c  8193b973 nt!KiBugCheckProgress
80db6588  81a1d138 nt!KiInitialPCR+0x138
80db65bc  8193b973 nt!KiBugCheckProgress
80db65c4  81a2c0c0 nt!KiInitialThread
80db65c8  81a1d120 nt!KiInitialPCR+0x120
80db65e0  8068650d nvstor+0x750d
80db66a0  8068650d nvstor+0x750d
80db66b8  81912ccc nt!KiBugCheck2
80db68d0  81dda900 hal!Amd64ProfileSourceDescriptorTable+0xe88
80db68ec  818e4eb5 nt!MiRaisedIrqlFault+0x46
80db690c  81855a74 nt!MmAccessFault+0x8f7
80db692c  8068534f nvstor+0x634f
80db6944  8068538b nvstor+0x638b
80db6958  81912d92 nt!KiBugCheck2+0xc6
80db696c  8068650d nvstor+0x750d
80db697c  81989840 nt!KiTrap0E+0x2c8
80db6990  8068650d nvstor+0x750d
80db699c  8068650d nvstor+0x750d
80db6a00  8068650d nvstor+0x750d
80db6a20  80686650 nvstor+0x7650
80db6a30  8068595a nvstor+0x695a
80db6a50  80680761 nvstor+0x1761
80db6a68  80686745 nvstor+0x7745
80db6a78  80690703 nvstor+0x11703
80db6a90  806ace88 storport!RaCallMiniportAdapterControl+0x24
80db6aa4  806aabd6 storport!RaidAdapterRestartAdapter+0xffffffff`ffffd889
80db6ab4  806ace4d storport!RaidIsAdapterControlSupported+0x4a
80db6ac4  806ad4e9 storport!RaidAdapterPowerUpDeviceCompletionLastStep+0x2c
80db6ad0  81a10001 nt!HvlpLogicalProcessorRegions+0xb81
80db6ad8  81e5a4c8 ACPI!AcpiBuildRunMethodList
80db6ae0  81897701 nt!EtwpDequeueFreeBuffer+0x20e
80db6af0  806ad4b4 storport!RaidAdapterDevicePowerUpSrbComplete+0x1c
80db6b00  806a61ac storport!RaidpAdapterDpcRoutine+0xe2
80db6b10  81a1f30c nt!KiInitialPCR+0x230c
80db6b6c  818774ab nt!KiExecuteAllDpcs+0x1f2
80db6b80  81a20c18 nt!KiInitialPCR+0x3c18
80db6b84  81a1d120 nt!KiInitialPCR+0x120
80db6b88  81a2c0c0 nt!KiInitialThread
80db6ba8  81a20f44 nt!KiInitialPCR+0x3f44
80db6bb0  81a1f300 nt!KiInitialPCR+0x2300
80db6bb8  81a1f30c nt!KiInitialPCR+0x230c
80db6bbc  81a2c0c0 nt!KiInitialThread
80db6bc8  81a1d120 nt!KiInitialPCR+0x120
80db6bd0  806a60cb storport!RaidpAdapterDpcRoutine
80db6bd4  81a1f308 nt!KiInitialPCR+0x2308
80db6be8  818a75a0 nt!PpmIdleExecuteTransition+0x786
80db6bf4  81a1f380 nt!KiInitialPCR+0x2380
80db6c24  818770e6 nt!KiRetireDpcList+0xed
80db6c28  81a2c0c0 nt!KiInitialThread
80db6c34  81a2c0c0 nt!KiInitialThread
80db6c38  81a1d000 nt!KiInitialPCR
80db6c4c  81a2c0c0 nt!KiInitialThread
80db6c5c  81a1d120 nt!KiInitialPCR+0x120
80db6c6c  81a20e10 nt!KiInitialPCR+0x3e10
80db6c78  819573c4 nt!PpmCheckPeriodicStart
80db6c84  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6c90  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6c9c  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6ca8  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6cb4  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6cc0  81e975d8 pci!PciPowerUpDeviceTimerDpc
80db6ccc  81cce973 nt!AnFwpFadeAnimationTimer
80db6cd8  81e36296 ACPI!ACPIBuildDeviceDpc
80db6ce4  806a60cb storport!RaidpAdapterDpcRoutine
80db6d04  81a2c0c0 nt!KiInitialThread
80db6d08  81954180 nt!PoIdle+0x28b
80db6d18  81a1d120 nt!KiInitialPCR+0x120
80db6d44  8198aeb4 nt!KiIdleLoop+0x38
80db6dac  8198b020 nt!KiThreadStartup
80db6db4  8198ae7c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120712-29889-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81460000 PsLoadedModuleList = 0x8164ade8
Debug session time: Thu Dec  6 19:50:28.202 2012 (UTC - 7:00)
System Uptime: 0 days 4:19:52.941
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {4, 12c, 885a1840, 80a35b54}
Can't retrieve thread context, Win32 error 0n30
Probably caused by : storport.sys ( storport!RaidBusEnumeratorIssueSynchronousRequest+186 )
0: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
82f3d418  8166433c nt!KiInitialPCR+0x233c
82f3d41c  81662100 nt!KiInitialPCR+0x100
82f3d420  81495818 nt!KiCommitThreadWait+0x280
82f3d43c  816710c0 nt!KiInitialThread
82f3d448  81662120 nt!KiInitialPCR+0x120
82f3d45c  81665c18 nt!KiInitialPCR+0x3c18
82f3d460  816374c8 nt!ExNode0+0x108
82f3d46c  81ab262b storport!RaUnitScsiIrp+0x627
82f3d478  81ab2659 storport!RaUnitScsiIrp+0x655
82f3d494  81494eeb nt!KeWaitForSingleObject+0x269
82f3d4c0  8141a796 hal!KfLowerIrql+0x2c
82f3d4d4  81498e2b nt!KeReleaseInStackQueuedSpinLock+0x3a
82f3d4d8  8163b4e0 nt!NonPagedPoolDescriptor+0xb60
82f3d500  81ac0884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
82f3d530  81ac0884 storport!RaidBusEnumeratorIssueSynchronousRequest+0x186
82f3d544  81662120 nt!KiInitialPCR+0x120
82f3d55c  81543f8d nt!MiFindContiguousMemoryInPool+0x56
82f3d564  81543fa3 nt!MiFindContiguousMemoryInPool+0x6c
82f3d58c  8150af2a nt!MiAllocateContiguousMemory+0x263
82f3d5a8  8163a980 nt!NonPagedPoolDescriptor
82f3d5ac  81625308 nt!ExFreePoolWithTag+0x2f3
82f3d5bc  81625308 nt!ExFreePoolWithTag+0x2f3
82f3d5cc  81626303 nt!ExAllocatePoolWithTag+0xd3
82f3d5d4  8163a980 nt!NonPagedPoolDescriptor
82f3d648  81ac1e6c storport!RaidBusEnumeratorIssueReportLuns+0x2b
82f3d650  81ac1e79 storport!RaidBusEnumeratorIssueReportLuns+0x38
82f3d670  81ac1add storport!RaidBusEnumeratorGetLunListFromTarget+0x41
82f3d698  81ac136e storport!RaidBusEnumeratorGetLunList+0x43
82f3d718  81ac0415 storport!RaidAdapterEnumerateBus+0xb5
82f3d84c  81abae4d storport!RaidIsAdapterControlSupported+0x4a
82f3d858  81ac0f69 storport!RaidAdapterRescanBus+0x7e
82f3d86c  81498e2b nt!KeReleaseInStackQueuedSpinLock+0x3a
82f3d8cc  81ac0c43 storport!RaidAdapterQueryDeviceRelationsIrp+0x9b
82f3d8e0  81ab4d81 storport!RaidpAdapterContinueScatterGather
82f3d8e8  8141534d hal!IoFreeAdapterChannelV2+0x41
82f3d8fc  81410df1 hal!IoFreeAdapterChannel+0x27
82f3d928  81410f70 hal!HalAllocateAdapterChannel+0x3c
82f3d934  81abea03 storport!RaidAdapterPnpIrp+0x193
82f3d984  81ab65ac storport!RaDriverPnpIrp+0x6e
82f3d9a0  81498a7c nt!IofCallDriver+0x3f
82f3d9bc  816c819f nt!PnpAsynchronousCall+0x94
82f3d9d8  816c80cf nt!PnpQueryDeviceRelations+0x67
82f3d9e0  815451d7 nt!PnpDeviceCompletionRoutine
82f3da1c  814d5121 nt!PopFxActivateDevice+0x8e
82f3da3c  816c835c nt!PipEnumerateDevice+0x119
82f3da44  815451d7 nt!PnpDeviceCompletionRoutine
82f3da54  816507f8 nt!PnpSpinLock
82f3da64  816c6ebc nt!PnpProcessAssignResources+0x5f
82f3da90  8171b726 nt!PipProcessDevNodeTree+0x26b
82f3dab0  8141a995 hal!HalpDispatchSoftwareInterrupt+0x4f
82f3daec  8141a796 hal!KfLowerIrql+0x2c
82f3db18  94583fa1Unable 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
82f3db20  945994ba nvlddmkm+0x1924ba
82f3db4c  9459952d nvlddmkm+0x19252d
82f3db68  8141a76a hal!KfLowerIrql
82f3db7c  8141a796 hal!KfLowerIrql+0x2c
82f3db90  814fae50 nt!KeReleaseMutex+0x12d
82f3dbc0  8163bac0 nt!NonPagedPoolDescriptor+0x1140
82f3dbc4  81625308 nt!ExFreePoolWithTag+0x2f3
82f3dbe4  9458082d nvlddmkm+0x17982d
82f3dbec  814c39e7 nt!ExpReleaseResourceForThreadLite+0x264
82f3dc00  8141a702 hal!HalpInterruptEnumerateUnmaskedInterrupts+0xf6
82f3dc08  8141a796 hal!KfLowerIrql+0x2c
82f3dc0c  81652e18 nt!IopDeviceTreeLock+0x18
82f3dc1c  81495844 nt!KiCommitThreadWait+0x2ac
82f3dc2c  814c32eb nt!ExAcquireResourceSharedLite+0x184
82f3dc3c  8166d0c0 nt!KiPendingTimersMask0
82f3dc4c  8171ede7 nt!PiMarkDeviceTreeForReenumerationWorker+0x1c
82f3dc58  81652e34 nt!IopDeviceTreeLock+0x34
82f3dc6c  8171ee1c nt!PipForAllChildDeviceNodes+0x21
82f3dc78  814c376a nt!ExReleaseResourceLite+0xd
82f3dc7c  81652e00 nt!IopDeviceTreeLock
82f3dc90  8170e547 nt!PiProcessReenumeration+0x75
82f3dcb8  8141a796 hal!KfLowerIrql+0x2c
82f3dccc  81502338 nt!PnpDeviceActionWorker+0x116
82f3dcd0  816374b8 nt!ExNode0+0xf8
82f3dcd8  816373c0 nt!ExNode0
82f3dcec  8165fc60 nt!CmpDelayDerefKCBLock
82f3dcf4  814c376a nt!ExReleaseResourceLite+0xd
82f3dcf8  8166d000 nt!CmpRegistryLock
82f3dd00  816c4f31 nt!CmpUnlockRegistry+0x16
82f3dd0c  814e17f9 nt!ExpWorkerThread+0xb6
82f3dd10  816374b8 nt!ExNode0+0xf8
82f3dd20  814e1854 nt!ExpWorkerThread+0x111
82f3dd3c  81502222 nt!PnpDeviceActionWorker
82f3dd44  816507e0 nt!PnpDeviceEnumerationWorkItem
82f3dd48  816507e0 nt!PnpDeviceEnumerationWorkItem
82f3dd68  8141a796 hal!KfLowerIrql+0x2c
82f3dd78  81524415 nt!PspSystemThreadStartup+0x4a
82f3dda4  81567bb9 nt!_except_handler4
82f3ddb4  815d0039 nt!KiThreadStartup+0x19
82f3ddb8  814e1747 nt!ExpWorkerThread
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120612-46441-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81a11000 PsLoadedModuleList = 0x81bfbde8
Debug session time: Thu Dec  6 15:28:30.736 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:24.475
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+14da2 )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
8b880958  81b92cab nt! ?? ::FNODOBFM::`string'+0xea93
8b88097c  81fae796 hal!KfLowerIrql+0x2c
8b880990  81a9df7d nt!KeInsertQueueDpc+0x1b0
8b8809ac  82bf0d61 usbohci!OHCI_InterruptService+0x85
8b8809c0  90014eb1 USBPORT!USBPORT_InterruptService+0x73
8b8809c8  81a9c49b nt!KeUpdateRunTime+0x4c
8b8809f0  81fbbfd4 hal!HalpTimerClockInterruptCommon+0x3c
8b8809f4  81ab1525 nt!KxWaitForLockOwnerShip+0x1f
8b880a0c  81fcd5fd hal!HalpTimerClockInterrupt+0x199
8b880a1c  81ab1525 nt!KxWaitForLockOwnerShip+0x1f
8b880a38  81fae796 hal!KfLowerIrql+0x2c
8b880a4c  81a9df7d nt!KeInsertQueueDpc+0x1b0
8b880a80  81ab1525 nt!KxWaitForLockOwnerShip+0x1f
8b880a94  828cf7c4 storport!StorPortNotification+0x8a
8b880aa0  828d115a storport!StorPortWriteRegisterUlong+0x11
8b880aac  828bdb89 nvstor+0x14b89
8b880ab4  828bdda2 nvstor+0x14da2
8b880ad4  828ace91 nvstor+0x3e91
8b880af4  828aca02 nvstor+0x3a02
8b880afc  828acabd nvstor+0x3abd
8b880b10  828ac5ca nvstor+0x35ca
8b880b30  828b89bd nvstor+0xf9bd
8b880b5c  828bb239 nvstor+0x12239
8b880b6c  81a6d4ab nt!KiExecuteAllDpcs+0x1f2
8b880b7c  828b8956 nvstor+0xf956
8b880ba0  828b8956 nvstor+0xf956
8b880bd0  828bb226 nvstor+0x12226
8b880bdc  81a9d56f nt!PpmIdleExecuteTransition+0x755
8b880be8  81a9d5a0 nt!PpmIdleExecuteTransition+0x786
8b880bf8  81fb61ea hal!KeQueryPerformanceCounter+0xbe
8b880c08  81ad7beb nt!KeGetNextTimerExpirationDueTime+0x2e
8b880c24  81a6d0e6 nt!KiRetireDpcList+0xed
8b880c78  828bb226 nvstor+0x12226
8b880cc0  81b49e5b nt!PpmIdlePrepare+0xca
8b880ce0  81b4a108 nt!PoIdle+0x213
8b880d08  81b4a180 nt!PoIdle+0x28b
8b880d44  81b80eb4 nt!KiIdleLoop+0x38
8b880d54  81b02182 nt!KiGetXSaveSupportedFeatures+0x23
8b880d84  81c315e7 nt!KiInitializeXSave+0x78
8b880d98  81c3162c nt!KiInitializeXSave+0xbd
8b880dac  81b81020 nt!KiThreadStartup
8b880db4  81b80e7c nt!KiIdleLoop
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120612-34101-01.dmp]
Could not match Dump File signature - invalid file format
Could not open dump file [120612-34101-01.dmp], Win32 error 0n87
    "The parameter is incorrect."
Debuggee initialization failed, Win32 error 0n87
    "The parameter is incorrect."
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120612-37627-01.dmp]
Could not match Dump File signature - invalid file format
Could not open dump file [120612-37627-01.dmp], Win32 error 0n87
    "The parameter is incorrect."
Debuggee initialization failed, Win32 error 0n87
    "The parameter is incorrect."
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\BSODDmpFiles\VindicoAtrum\Windows7_Vista_jcgriff2\120612-36395-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80e71000 PsLoadedModuleList = 0x8105bde8
Debug session time: Thu Dec  6 13:36:55.740 2012 (UTC - 7:00)
System Uptime: 0 days 3:39:29.479
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+13aed )
3: kd> kd: Reading initial command '!niemiro.rawstack; !niemiro.rawstack -dc; !niemiro.auto_errrec; q'
82280918  80ff2cab nt! ?? ::FNODOBFM::`string'+0xea93
82280950  80e401d4 hal!HalpTscQueryCounter+0x2
82280984  80efc49b nt!KeUpdateRunTime+0x4c
822809ac  80e38fd4 hal!HalpTimerClockInterruptCommon+0x3c
822809b0  80e4b4bf hal!READ_PORT_UCHAR+0x7
822809c8  80e4a5fd hal!HalpTimerClockInterrupt+0x199
822809cc  80e34402 hal!HalpTimerStallExecutionProcessor+0xf0
822809d8  80e4b4bf hal!READ_PORT_UCHAR+0x7
82280a3c  80e4b4bf hal!READ_PORT_UCHAR+0x7
82280a48  81cd74eb storport!StorPortReadPortUchar+0xe
82280a54  81caaaed nvstor+0x13aed
82280a64  81ca6676 nvstor+0xf676
82280a70  81c9c6f5 nvstor+0x56f5
82280a80  81c9bd52 nvstor+0x4d52
82280a90  81c9bebe nvstor+0x4ebe
82280aa4  81c9faa1 nvstor+0x8aa1
82280acc  81c9c5f8 nvstor+0x55f8
82280aec  81c9a302 nvstor+0x3302
82280af4  81c9bf5b nvstor+0x4f5b
82280b10  81c9a5ca nvstor+0x35ca
82280b30  81ca69bd nvstor+0xf9bd
82280b5c  81ca9239 nvstor+0x12239
82280b6c  80ecd4ab nt!KiExecuteAllDpcs+0x1f2
82280b7c  81ca6956 nvstor+0xf956
82280b8c  810483c0 nt!ExNode0
82280ba0  81ca6956 nvstor+0xf956
82280bd0  81ca9226 nvstor+0x12226
82280bdc  80efd56f nt!PpmIdleExecuteTransition+0x755
82280be8  80efd5a0 nt!PpmIdleExecuteTransition+0x786
82280bf8  80e331ea hal!KeQueryPerformanceCounter+0xbe
82280c08  80f37beb nt!KeGetNextTimerExpirationDueTime+0x2e
82280c24  80ecd0e6 nt!KiRetireDpcList+0xed
82280c78  81ca9226 nvstor+0x12226
82280cc0  80fa9e5b nt!PpmIdlePrepare+0xca
82280ce0  80faa108 nt!PoIdle+0x213
82280d08  80faa180 nt!PoIdle+0x28b
82280d44  80fe0eb4 nt!KiIdleLoop+0x38
82280d54  80f62182 nt!KiGetXSaveSupportedFeatures+0x23
82280d84  810915e7 nt!KiInitializeXSave+0x78
82280d98  8109162c nt!KiInitializeXSave+0xbd
82280dac  80fe1020 nt!KiThreadStartup
82280db4  80fe0e7c nt!KiIdleLoop
82280c28  82269330 82280c68 8478fd40 82269330  0.&.h.(.@.x.0.&.
82280cf8  82280d2c 82280d30 8478fd40 82269330  ,.(.0.(.@.x.0.&.
 
Under IDE ATA/ATAPI there is no Nvidia options as far as I can see. Unless you mean the two Nvidia ATA options under storage controllers?
 
My apologies, I was not familiar with where NVIDIA places their devices. It would make sense that they would be under storage controllers based on the driver name: "nVidia Storage Drivers"

Follow the procedure in my previous post for the NVIDIA devices under storage controllers instead of IDE ATA/ATAPI controllers.

Thanks for teaching me something new. :-}
 
Ok, did that. When I restarted, they must have re-installed because nothing came up, so I checked the device management again and they're back as they were. In theory, if it has just installed the latest drivers for this, then nvstor.sys should not cause any more issues, right?
 
Correct.

Were you given the option to delete the driver software for the devices when uninstalling them through device manager?
 
That probably means the nvstor driver that was originally installed came packaged in the Windows 8 original drivers. If there is no option to delete those drivers during uninstall, then you will not have control over them being re-installed during next boot. Do not manually delete the drivers from the Windows driverstore; that may have unforeseen consequences such as being unable to boot Windows in the future.

If you continue to have problems related to nvstor, you may need to contact Microsoft AnswerDesk for support since those drivers were provided by Microsoft during Windows 8 installation.
 
Looking into that now. Just to check - this is the only fault you've detected and should be the cause of these DPC_WATCHDOG_VIOLATION errors?

Thanks.
 
It is the most likely cause of the crashes, yes. Some of your crashes blame nvstor.sys directly, others just have it in the stack. The driver is the most likely cause. Other causes include: an underlying driver issue conflicting with the nvstor.sys driver, hard disk file system corruption, a virus, bad hard disk sectors, RAM faults, a faulty motherboard controller, or other hardware faults.

Since this started with the install of Windows 8 and did not occur with Windows 7, the first suspect is a driver issue. If you continue to have crashes after doing the re-install procedure you did today, I would suggest enabling Driver Verifier - BSOD related to see if another driver is causing conflicts with nvstor.sys


EDIT: Forgot to mention one other cause that I see in your software installed: registry damage due to using a registry cleaner. I see you have ccleaner and little registry cleaner apps installed. Are you using the registry cleaning features of each?
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top