BSOD help (may be related to GPU temps.)

[writhziden]

Ok, got the newer version installed,

should I now uninstall the drivers for the GPU or just leave it be (they are the current ones), update the DirectX and test it that way?

Realized I never answered this. Just do your normal routine and see how things go once you clean out the GPU of any dust. We'll worry about re-installing drivers if you continue to have crashes. Best wishes that ASACPI.SYS and dust were the only problems.

 

[Bsbsod]

yeah same hopes here, i will play and do my normal routine for a week, if i see no issues, i will make sure to post back and let you all know. Thanks sooooo much for your help.

 

[writhziden]

You're very welcome. Before doing so, what are your idle temperatures now? Any better after cleaning out the dust?

 

[Bsbsod]

well its a mixed bag, temps did drop to around 60 degrees, but i've read everywhere, that apparently having dual high-res displays can make the gtx570 idle very hot. To counteract this most people make sure that when gaming they use a single monitor, or for those that game in extended monitors they have after-market cooling. So far so good.

 

[writhziden]

Well at least your temperatures dropped a bit. That is a good sign. Good luck!

 

[Bsbsod]

Looks like I spoke too soon. Here's the new dump file with the .html file thingy.

Hopefully you can interpret it and point me in the right direction...

In other news, its not the temperatures. At least not now. When I crashed I happened to be conveniently looking at EVGA precision dashboard and my GPU was at about 55 C and my CPU was around 50.

Let me know what you think.

 

[writhziden]

I notice drivermax installed on your system. Do you use it to keep all your drivers up to date, or only the ones that are actually causing problems? Using it for all drivers can cause system instability and lead to the crashes you are experiencing. Many of the drivers software like drivermax will download are actually for other devices than the ones on your computer, so while the driver is updated, it supports the wrong hardware. If you are using drivermax, the fastest course of action is to http://www.sevenforums.com/tutorials/3413-repair-install.html Windows 7.

If you do not need to or want to do a repair install, proceed through the rest of this post. I am including the Driver Verifier steps for troubleshooting in case you decide not to do the repair install even though you are using drivermax for all your drivers.

I also notice that you have not yet installed all Windows updates. Please proceed to do so.

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


Loading Dump File [K:\Kingston\BSODDmpFiles\bsbsod\Windows_NT6_BSOD_jcgriff2\020312-26317-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03297670
Debug session time: Fri Feb  3 21:43:11.816 2012 (GMT-7)
System Uptime: 0 days 4:20:13.845
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff880488fbc8b, 2, 1, fffff80003124bf7}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff880488fbc8b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003124bf7, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003301100
 fffff880488fbc8b 

CURRENT_IRQL:  2

FAULTING_IP: 
nt! ?? ::FNODOBFM::`string'+2ac7
fffff800`03124bf7 d2740441        sal     byte ptr [rsp+rax+41h],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff880088f34b0 -- (.trap 0xfffff880088f34b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040008602 rbx=0000000000000000 rcx=000000000ac59188
rdx=fffffa800ac59170 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003124bf7 rsp=fffff880088f3648 rbp=fffff880088f3b00
 r8=fffffa800ae5c130  r9=fffff880088f3690 r10=0000000000000000
r11=0000000040000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt! ?? ::FNODOBFM::`string'+0x2ac7:
fffff800`03124bf7 d2740441        sal     byte ptr [rsp+rax+41h],cl ss:0018:fffff880`488fbc8b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030ce1e9 to fffff800030cec40

STACK_TEXT:  
fffff880`088f3368 fffff800`030ce1e9 : 00000000`0000000a fffff880`488fbc8b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`088f3370 fffff800`030cce60 : 00000000`00000000 fffffa80`09b39370 fffff880`0111ba00 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`088f34b0 fffff800`03124bf7 : fffff800`03166607 fffff880`088f36f0 fffffa80`0adbbc28 fffffa80`0adbbc28 : nt!KiPageFault+0x260
fffff880`088f3648 fffff800`03166607 : fffff880`088f36f0 fffffa80`0adbbc28 fffffa80`0adbbc28 fffff880`088f39e0 : nt! ?? ::FNODOBFM::`string'+0x2ac7
fffff880`088f3650 fffff800`03072ec1 : 00000000`00000000 00000000`00000000 fffffa80`0adbbc28 fffffa80`07c618f0 : nt!FsRtlPrivateCheckForExclusiveLockAccess+0x37
fffff880`088f3690 fffff880`0128556a : 00000000`00000000 fffffa80`0ac19b00 00000000`00000000 00000000`00000001 : nt!FsRtlPrivateLock+0x189
fffff880`088f3760 fffff880`011094a1 : fffffa80`0ac19b00 fffffa80`09b393f0 fffff880`088f3b48 fffffa80`0a687740 : Ntfs!NtfsFastLock+0x182
fffff880`088f3980 fffff880`0110c8ba : fffff880`088f3a50 fffffa80`09b39388 fffffa80`0a687700 fffff880`088f3b00 : fltmgr!FltpPerformFastIoCall+0x491
fffff880`088f39e0 fffff880`0112ddda : fffff880`088f3b48 00000000`00000000 fffff880`088f3b58 fffff880`088f3b38 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`088f3a20 fffff800`03341cc7 : fffffa80`0ac19b00 fffffa80`0a687740 fffffa80`06d1c800 fffffa80`0a687740 : fltmgr!FltpFastIoLock+0x19a
fffff880`088f3ad0 fffff800`030cded3 : fffffa80`097f7660 00000000`00a2e168 00000000`00000000 00000000`00000000 : nt!NtLockFile+0x2c5
fffff880`088f3bb0 00000000`7793214a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00a2e138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7793214a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
4 errors : !nt (fffff80003124bc0-fffff80003124bf0)
fffff80003124bc0 *cf  41  18  73  06  48  8d  41  18  eb  04  49  8d  40  08  48 [email protected]
fffff80003124bd0 *b0  00  48  89  02  c3  90  90  90  90  90  90  90  90  90  90 ..H.............
fffff80003124be0 *20  85  db  74  08  e9  d3  e8  f4  ff  48  8b  da  4d  85  c9  ..t......H..M..
fffff80003124bf0 *9f  03  49  89  09  4d  85  d2  74  04  41  c6  02  01  48  8b ..I..M..t.A...H.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Antivirus Software...


Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Install all Windows updates.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

 

[Bsbsod]

Ok, I've done all the updates I could do through Windows update (the one missing was for definitions for Security Essentials). I will now try the memtest boot version to see if it detects any issues. I will try the extended Microsoft Memory diagnostic later tonight when I'm going to bed so as to leave it run over-night. Will post again tomorrow with the results unless memtest comes back with something sooner than that.

 

[Bsbsod]

Well, I left Mem-test running all night and most of the morning, it completed 7 passes, with no errors. I will run the extended version of the memory diagnostic tool for windows tonight to see if that brings up anything. in the meantime I've managed to use the system for hours, I mean hours on end and had only one BSOD when I stepped away and there was nothing running (no games, apps or anything). I have since turned on the driver verifier and am now hoping another crash will occur that might shed on a potential driver issue.

My question:

If it really is the ram chips would it not fail sooner, or while under load?

It seems odd the systems BSODs when I'm not doing anything that might cause undue stress on the RAM.

I will get back to you again soon hopefully. I'm making sure to push the system to fail now. I've got both my displays on, games going, music streaming, whole enchilada in the hopes that I may trigger the BSOD.

See you all soon, and thanks for your continued patience.

 

[writhziden]

It depends on the problems with the RAM. obvious symptoms do not always present themselves. If it happens when you are away from the computer, it could also be a power management issue causing the fault, and sleep mode puts information into the memory, so it could be RAM as well.

 

[Bsbsod]

Excellent point!

I've so far had my computer set for "performance" under the power options, i've now set it for the normal setting.

In addition to this I've also set my sleep and other options to just off. I will now dictate when the screens and computer shut off.

 

[writhziden]

Alright, upload a new crash report after you've had a few crashes accumulate so we can look for patterns.

 

[Bsbsod]

Ok then, how about a quadruple BSOD with cheese?

System crashed after uh...I dont know? 45 mins?

I've compile a new crash file and am now operating on just one (1) 2gb ram stick instead of my usual 4 (in hopes of finding the culprit that way if it is truly related to memory).

While doing the perfmon/ report thing I just now saw a red X with the following statement next to it on the report:

The device driver for Unibrain 1394 PC has not been installed. This device will not be available until the correct device driver is installed.

I would also like to say that while I completely removed Norton 360 using the removal tool, I would like to know if there's any way to verify there isn't a trace of the program left around (any way to check for drivers left behind for it? a list of some sort or a place I should look in?)

Please let me know if you see anything in the dump file that may describe a driver may be the issue, or any programs I have to remove. Anything.

Thanks again,

Rico

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Kingston\BSODDmpFiles\BSBSOD\Windows_NT6_BSOD_jcgriff2\020512-23524-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`03262670
Debug session time: Sun Feb  5 16:14:25.332 2012 (GMT-7)
System Uptime: 0 days 0:00:18.330
Loading Kernel Symbols
.....................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff800030bff00}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030bff00, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cc100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`030bff00 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b3670 -- (.trap 0xfffff880030b3670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000007d30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030bff00 rsp=fffff880030b3800 rbp=fffffa800138a800
 r8=fffff800032cf4c0  r9=0000000000000000 r10=000000000023ffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiReplenishPageSlist+0xc0:
fffff800`030bff00 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:7580:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030991e9 to fffff80003099c40

STACK_TEXT:  
fffff880`030b3528 fffff800`030991e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b3530 fffff800`03097e60 : 00000000`00000010 fffff800`0352cadc 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b3670 fffff800`030bff00 : fffffa80`06d6e040 fffff800`0309c9e5 00000000`02a587fd fffff880`03164180 : nt!KiPageFault+0x260
fffff880`030b3800 fffff800`031b65ac : fffffa80`06c00a00 00000000`00000016 00000000`00000000 00000000`00000000 : nt!MiReplenishPageSlist+0xc0
fffff880`030b3870 fffff800`031b6dc1 : 00000000`00000080 00000000`00000020 00000000`00000000 00000000`0023ffff : nt!MiAllocateMdlPagesByLists+0x60c
fffff880`030b39a0 fffff800`031b76c9 : 00000000`00000001 fffffa80`08ba7000 00000000`00000041 00000000`00000001 : nt!MiAllocatePagesForMdl+0x451
fffff880`030b3a90 fffff880`01b18fd3 : fffffa80`08b8a118 fffff880`01b26519 00000000`00000001 fffff880`08fef000 : nt!MmAllocatePagesForMdlEx+0x89
fffff880`030b3ad0 fffff880`01b263da : fffffa80`08b8a118 fffffa80`08b8a118 fffff880`030b03e0 fffffa80`08b8a118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+0x9b
fffff880`030b3b30 fffff880`01b2459e : fffffa80`08b8a118 00000000`00000010 00000000`00000010 fffff800`03224348 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageFindSpace+0x4a
fffff880`030b3b60 fffff880`01b23773 : fffffa80`08f81150 fffffa80`08fba150 00000000`00000000 fffffa80`08b8a118 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x2e
fffff880`030b3c20 fffff880`01b2362e : fffffa80`08f81150 00000000`00010000 00000000`00000080 fffffa80`08b8a0b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`030b3c80 fffff880`01b2241a : fffffa80`08f81150 00000000`00000080 00000000`00000080 fffffa80`08b8af88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`030b3ce0 fffff800`03334fee : 00000000`00000000 fffff880`00000000 fffffa80`08a8f8e0 fffffa80`06cc4b30 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`030b3d40 fffff800`0308b5e6 : fffff880`03164180 fffffa80`08a8f8e0 fffffa80`06d6e040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`030b3d80 00000000`00000000 : fffff880`030b4000 fffff880`030ae000 fffff880`030b3810 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b
fffff880`01b18fd3 488be8          mov     rbp,rax

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0xA_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b

BUCKET_ID:  X64_0xA_rdyboost!ST_STORE_SMD_TRAITS_::StDmCurrentRegionSet+9b

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

Using a ReadyBoost drive?

Loading Dump File [F:\Kingston\BSODDmpFiles\BSBSOD\Windows_NT6_BSOD_jcgriff2\020512-18532-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`032a1670
Debug session time: Sun Feb  5 12:01:01.848 2012 (GMT-7)
System Uptime: 0 days 2:20:51.877
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800030cece8}

Unable to load image 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+1e9be2 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030cece8, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330b100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueue+a8
fffff800`030cece8 49890f          mov     qword ptr [r15],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c560 -- (.trap 0xfffff80000b9c560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff800032792c0
rdx=fffffa8009f3d730 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030cece8 rsp=fffff80000b9c6f0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff8000324f880
r11=fffffa800a069c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueue+0xa8:
fffff800`030cece8 49890f          mov     qword ptr [r15],rcx ds:a1d3:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d81e9 to fffff800030d8c40

STACK_TEXT:  
fffff800`00b9c418 fffff800`030d81e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c420 fffff800`030d6e60 : fffffa80`09800000 fffff880`0f49d1aa 00000000`00000001 fffff800`032792b8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c560 fffff800`030cece8 : fffffa80`00000271 00000000`000007ff 126fa1d3`c67deca0 00000000`00000112 : nt!KiPageFault+0x260
fffff800`00b9c6f0 fffff800`030e51f4 : fffff880`00000000 fffffa80`09f3d730 00000000`00000000 fffffa80`00000000 : nt!KiInsertQueue+0xa8
fffff800`00b9c770 fffff880`0f47cbe2 : fffffa80`08317480 00000000`00000000 fffff880`0fa2be9c fffffa80`00000000 : nt!ExQueueWorkItem+0x44
fffff800`00b9c7b0 fffffa80`08317480 : 00000000`00000000 fffff880`0fa2be9c fffffa80`00000000 fffffa80`09800000 : nvlddmkm+0x1e9be2
fffff800`00b9c7b8 00000000`00000000 : fffff880`0fa2be9c fffffa80`00000000 fffffa80`09800000 fffff880`0fa2cb07 : 0xfffffa80`08317480


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1e9be2
fffff880`0f47cbe2 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nvlddmkm+1e9be2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f2128ab

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+1e9be2

BUCKET_ID:  X64_0xA_nvlddmkm+1e9be2

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

Graphics card driver...


And I did look for any drivers residing on your system from Norton. Clean bill of health there.

 

[Bsbsod]

I have no idea what a ReadyBoost drive is. What course of action should I pursue?

As for the graphics card driver I'm just about ready to pull my hair out...I'm current on the newest drive, and have removed and re-installed a few times. What can I do about that?

 

[writhziden]

I've seen ReadyBoost crashes occur for no known reason. I would not worry about that one at the moment.

I'm wondering if the graphics card is bad and that is why the driver keeps popping up. Do you have access to another card (one you own, a friend owns, etc) that you could test in the machine?

 

[Bsbsod]

unfortunately I do not. Is there a similar test to Memtest for a GPU that I could use to detect issues?

 

[writhziden]

unfortunately I do not. Is there a similar test to Memtest for a GPU that I could use to detect issues?

post #18 contains the tests you are looking for.

 

[Bsbsod]

Terribly sorry, I will now attempt those tests and hopefully come back with an indication of the GPU being the source of the problems.

 

[writhziden]

You may want to disable Verifier first. It's up to you. You could test both with Verifier on and with it off and see what the results are in each case. Good luck!