BSOD help (may be related to GPU temps.)

Bsbsod · 05 Feb 2012

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 · 05 Feb 2012

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

Bsbsod · 05 Feb 2012

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 · 05 Feb 2012

Code:


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?

Code:


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 · 05 Feb 2012

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 · 05 Feb 2012

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 · 05 Feb 2012

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

writhziden · 05 Feb 2012

Bsbsod said:

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 · 05 Feb 2012

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 · 05 Feb 2012

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!