BSOD on Different Times and Different Errors

shriekyphantom · 09 Apr 2012

Sorry for not replying early. Our family went on a vacation and there's no internet connection in the place we went to. During the vacation, I've got one BSoD and a BSoD earlier.

I'll try doing the things you said above first.

EDIT: I can't update the HUAWEI since I can't find the proper driver. The device with HUAWEI is for the internet connection. Tried memtest again and no faults. Ran a DISC CHECK, no problem.

EDIT (again): I think I got a blue screen while updating windows after I reformat. I'm not sure if it is a blue screen since I didn't see it. I just saw the laptop restarting.

BSoD after reformat: 041412-67423-01

ePeen · 14 Apr 2012

Sorry, been very busy.

One out of the three dumps points to the culprit RTKVHD64.sys, which is the Realtek High Definition Audio Function Driver. I recommend updating your audio drivers: Realtek

Dump for reference:

Code:

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


Loading Dump File [C:\Users\Icarus\Downloads\040812-17955-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Sun Apr  8 11:26:39.183 2012 (UTC - 4:00)
System Uptime: 0 days 0:14:48.573
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002e9e7ff, fffff880030626c8, fffff88003061f20}

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
Probably caused by : RTKVHD64.sys ( RTKVHD64+36d9f9 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e9e7ff, The address that the exception occurred at
Arg3: fffff880030626c8, Exception Record Address
Arg4: fffff88003061f20, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiDeliverApc+a7
fffff800`02e9e7ff 498b4a30        mov     rcx,qword ptr [r10+30h]

EXCEPTION_RECORD:  fffff880030626c8 -- (.exr 0xfffff880030626c8)
ExceptionAddress: fffff80002e9e7ff (nt!KiDeliverApc+0x00000000000000a7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003061f20 -- (.cxr 0xfffff88003061f20)
rax=0000000000000002 rbx=fffffa800abdeb60 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa800abdebb0 rdi=fffff88003164180
rip=fffff80002e9e7ff rsp=fffff88003062900 rbp=0000000000000000
 r8=ffe9fa800abdebb0  r9=0000000000000000 r10=ffe9fa800abdeba0
r11=fffff88003164180 r12=0000000000000001 r13=0000000000000000
r14=fffffa8006a015f0 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xa7:
fffff800`02e9e7ff 498b4a30        mov     rcx,qword ptr [r10+30h] ds:002b:ffe9fa80`0abdebd0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f80e0
 ffffffffffffffff 

FOLLOWUP_IP: 
RTKVHD64+36d9f9
fffff880`077739f9 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002e73ba9 to fffff80002e9e7ff

STACK_TEXT:  
fffff880`03062900 fffff800`02e73ba9 : 00000000`00000000 00000000`00000000 fffff880`03062a38 fffff880`07406b05 : nt!KiDeliverApc+0xa7
fffff880`03062980 fffff800`02ecaf80 : fffff880`03062a38 fffff800`046a0080 00000000`00000000 00000000`00000004 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`030629b0 fffff880`077739f9 : 00000000`00000000 00000000`00000001 fffffa80`0aac1e00 fffffa80`0abf8c00 : nt!KeReleaseMutant+0x3c0
fffff880`03062a60 00000000`00000000 : 00000000`00000001 fffffa80`0aac1e00 fffffa80`0abf8c00 fffff880`03164180 : RTKVHD64+0x36d9f9


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+36d9f9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee727f6

STACK_COMMAND:  .cxr 0xfffff88003061f20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_RTKVHD64+36d9f9

BUCKET_ID:  X64_0x7E_RTKVHD64+36d9f9

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

shriekyphantom · 15 Apr 2012

High Definition Audio Codecs, right?

Got BSoDs earlier. Sorry for the trouble.

shriekyphantom · 15 Apr 2012

Another BSoD. OTL
And another one. GAAAAH!
And again. :'(((((((((((((
And today again. :'(

ePeen · 17 Apr 2012

Sorry for the lack of a response, I have been dealing with annoying technical issues of my own and just got a break for once.

All attached dumps are a *3b bugcheck with ntkrnlmp.exe as the culprit.

One thing I've noticed in your drivers list you have dtsoftbus01.sys which is a Daemon Tools driver. Please fully uninstall Daemon Tools from your system as its a big causer of BSODs. If after uninstalling Daemon Tools you're still crashing, please do the following:

Memtest, test your memory for any errors or faults.

Run CMD as admin (elevated command prompt), and type CHKDSK /R to check your HDD for any bad sectors.

If both of these show nothing, we're going back to Driver Verifier.

Dump for reference:

Code:

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


Loading Dump File [C:\Users\BSOD\Downloads\041612-25334-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS 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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a6650
Debug session time: Mon Apr 16 10:32:18.267 2012 (UTC - 4:00)
System Uptime: 0 days 0:32:17.141
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ed15e4, fffff8800ddf08c0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ed15e4, Address of the instruction which caused the bugcheck
Arg3: fffff8800ddf08c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiDeliverApc+d4
fffff800`02ed15e4 498b4a30        mov     rcx,qword ptr [r10+30h]

CONTEXT:  fffff8800ddf08c0 -- (.cxr 0xfffff8800ddf08c0)
rax=0000000000000002 rbx=fffffa800c2c3b60 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa800c2c3bb0 rdi=0000000000000000
rip=fffff80002ed15e4 rsp=fffff8800ddf12a0 rbp=0000000000000000
 r8=ff49fa800c2c3bb0  r9=0000000000000000 r10=ff49fa800c2c3ba0
r11=fffffffffffffd80 r12=0000000000000001 r13=fffff8a0032a8c00
r14=fffffa80095b6060 r15=fffff8800ddf1ae0
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xd4:
fffff800`02ed15e4 498b4a30        mov     rcx,qword ptr [r10+30h] ds:002b:ff49fa80`0c2c3bd0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ed15e4

STACK_TEXT:  
fffff880`0ddf12a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0xd4


FOLLOWUP_IP: 
nt!KiDeliverApc+d4
fffff800`02ed15e4 498b4a30        mov     rcx,qword ptr [r10+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiDeliverApc+d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

STACK_COMMAND:  .cxr 0xfffff8800ddf08c0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

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

shriekyphantom · 18 Apr 2012

The CHKDSK said that it's clean. I got BSoD again after the CHKDSK was done.

I'll try Memtest again.

ePeen · 18 Apr 2012

You still have Daemon Tools installed, remove it.

3b bugcheck pointing to a Microsoft file as usual.

1. Remove Daemon Tools.

2. Run Memtest.

shriekyphantom · 18 Apr 2012

Ran a Memtest (Daemon is already uninstalled) and comes clean.

Here's some shots if you wanna see. Sorry for the crappy photos. I don't have a good camera.

EDIT: Off-Topic Side Question: Should I change my PCI Latency Timer to 64 when I'm using a 64-bit OS?

ePeen · 19 Apr 2012

Keep me updated with any dumps. To answer your question, I'm not so sure.

shriekyphantom · 19 Apr 2012

Ok. I'll update you. Thanks for helping me. :)

EDIT: Here's a dump.