New
#11
Hey there, just a update i was just playing Starcraft 2 and im pritty sure i got a new BSOD? then on restart kept getting a bsod just before the login screen, so now im in safemode... the minidump files attached, thanks jordon.
Hey there, just a update i was just playing Starcraft 2 and im pritty sure i got a new BSOD? then on restart kept getting a bsod just before the login screen, so now im in safemode... the minidump files attached, thanks jordon.
At least one of these blame your RTKVHD64.sys. That is your video driver and shouldnt be loaded in safe mode. If not the driver, or the OS (because sfc was run) youhave to start looking at the card, heat, and power.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\042511-21606-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;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0204b000 PsLoadedModuleList = 0xfffff800`02288e50 Debug session time: Mon Apr 25 18:53:06.903 2011 (GMT-4) System Uptime: 0 days 0:00:22.590 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D5, {fffff98002f82d60, 0, fffff88008fe48ba, 0} Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHD64.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys Could not read faulting driver name Probably caused by : RTKVHD64.sys ( RTKVHD64+e58ba ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5) Memory was referenced after it was freed. This cannot be protected by try-except. When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff98002f82d60, memory referenced Arg2: 0000000000000000, value 0 = read operation, 1 = write operation Arg3: fffff88008fe48ba, if non-zero, the address which referenced memory. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800022f30e0 fffff98002f82d60 FAULTING_IP: RTKVHD64+e58ba fffff880`08fe48ba 8b4630 mov eax,dword ptr [rsi+30h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD5 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800ab052b0 -- (.trap 0xfffff8800ab052b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800ab054d8 rdx=fffff8800ab05440 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88008fe48ba rsp=fffff8800ab05440 rbp=0000000000000002 r8=0000000000000000 r9=fffff88008fe48ba r10=0000000000000000 r11=fffff80002235e80 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc RTKVHD64+0xe58ba: fffff880`08fe48ba 8b4630 mov eax,dword ptr [rsi+30h] ds:5e80:00000000`00000030=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000213bf14 to fffff800020bb740 STACK_TEXT: fffff880`0ab05148 fffff800`0213bf14 : 00000000`00000050 fffff980`02f82d60 00000000`00000000 fffff880`0ab052b0 : nt!KeBugCheckEx fffff880`0ab05150 fffff800`020b982e : 00000000`00000000 fffff8a0`0334010a fffffa80`0911c000 fffff800`020ee33f : nt! ?? ::FNODOBFM::`string'+0x42837 fffff880`0ab052b0 fffff880`08fe48ba : fffff880`0ab054d8 00000000`00000000 fffff8a0`0334010a fffffa80`0990a2c0 : nt!KiPageFault+0x16e fffff880`0ab05440 fffff880`0ab054d8 : 00000000`00000000 fffff8a0`0334010a fffffa80`0990a2c0 00000000`00000000 : RTKVHD64+0xe58ba fffff880`0ab05448 00000000`00000000 : fffff8a0`0334010a fffffa80`0990a2c0 00000000`00000000 fffff800`00000000 : 0xfffff880`0ab054d8 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHD64+e58ba fffff880`08fe48ba 8b4630 mov eax,dword ptr [rsi+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: RTKVHD64+e58ba FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHD64 IMAGE_NAME: RTKVHD64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d9c1679 FAILURE_BUCKET_ID: X64_0xD5_VRF_RTKVHD64+e58ba BUCKET_ID: X64_0xD5_VRF_RTKVHD64+e58ba Followup: MachineOwner --------- 0: kd> lmvm RTKVHD64 start end module name fffff880`08eff000 fffff880`091af880 RTKVHD64 T (no symbols) Loaded symbol image file: RTKVHD64.sys Image path: \SystemRoot\system32\drivers\RTKVHD64.sys Image name: RTKVHD64.sys Timestamp: Wed Apr 06 03:30:01 2011 (4D9C1679) CheckSum: 002B89C1 ImageSize: 002B0880 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4