BSOD 0x00000050 and 0x00003b

ShaoLimper · 27 Mar 2012

I have windows 7 home edition, possibly x64 but I am unsure. Laptop that is only 8 months old, this is the original OS, there was warranty work done on it once in which the motherboard was replaced, but aside from, there has been no physical changes.

Only real software of note that I have used is Daemon Tools, Malwarebytes, M. Security Essentials, and Spybot S&D. Daemon Tools has been removed as it was suspect of causes some errors, however that did nothing to stop them.

I updated my video driver as that was also suspect, but since have still had problems. I will work on updating some other drivers whilst I await replies, but in the mean time, I have attached my dmp files as directed by the BSOD posting regulations.

We will have to do without the perfmon/report as when I run it it says "No path specified."

Thank you in advanced.

Added Note:
I think it might be worth to mention that these BSOD occur in and out of safemode. It also can occur before windows or even the boot menu loads. I find leaving it sit for ten minutes or so raises my chances of loading windows.

And occasionally it is not even a BSOD, but just the computer freezing and the image going... uh, wonky I think is the technical term. Red and green seem to do their own thing.

Again, thank you.

ePeen · 27 Mar 2012

Hello, all of the dumps are pointing to core Windows files, cdd.dll, ntkrnl, win32.sys, you name it. It's MORE THAN unlikely that these are the cause of the crash, Windows just cannot pinpoint the driver fault itself, so it's shooting false positives.

However, one dump file points to usbport.sys, so there may possibly be an issue with a device you have attached. For example, these errors can stem when mouse drivers on on the fritz, keyboard drivers, etc. A popular causer of the usbport.sys culprit is Razer's mouse drivers, specifiecally Lachesis... just giving you an example. There may be no issue at all regarding usb or devices, but I am just letting you know just in case :)

In the newest dump, it's showing a lack of drivers.. not sure why, but in the second to newest dump, the one dated the 26th, it shows you still have dtsoftbus01.sys, which is Daemon Tools' driver. Just double checking with you to make sure it's fully removed. No signs of sptd.sys which sometimes comes with Daemon Tools, so that's good.

Two things I want you to do:

Memtest:

Read the following to test your memory for errors.

There are no signs of memory corruption or any memory related errors, but I'd just like to be sure.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Dumps 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\Windows_NT6_BSOD_jcgriff2\032712-15537-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9e650
Debug session time: Tue Mar 27 11:58:08.619 2012 (UTC - 4:00)
System Uptime: 0 days 14:30:31.835
Loading Kernel Symbols
..............................................Unable to add module at ffffffff`ffffffff

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ccd861, fffff880029e5f70, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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: fffff80002ccd861, Address of the instruction which caused the bugcheck
Arg3: fffff880029e5f70, 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!memcpy+1d1
fffff800`02ccd861 668b040a        mov     ax,word ptr [rdx+rcx]

CONTEXT:  fffff880029e5f70 -- (.cxr 0xfffff880029e5f70)
rax=000000000000006e rbx=000000000000006e rcx=fffff8a012124c4c
rdx=007307c8ee64b493 rsi=fffff8a012124be0 rdi=fffff8a012124b90
rip=fffff80002ccd861 rsp=fffff880029e6958 rbp=fffff8a00b530f10
 r8=000000000000006e  r9=0073006900770073 r10=fffffa8004b44508
r11=fffff8a012124be0 r12=0000000000000000 r13=fffff8a0138d60d8
r14=0000000000000000 r15=fffff8a001aa9da8
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!memcpy+0x1d1:
fffff800`02ccd861 668b040a        mov     ax,word ptr [rdx+rcx] ds:002b:00730069`007700df=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ccd861

STACK_TEXT:  
fffff880`029e56a8 fffff800`02cd62e9 : 00000000`0000003b 00000000`c0000005 fffff800`02ccd861 fffff880`029e5f70 : nt!KeBugCheckEx
fffff880`029e56b0 fffff800`02cd5c3c : fffff880`029e6718 fffff880`029e5f70 00000000`00000000 fffff800`02d01f60 : nt!KiBugCheckDispatch+0x69
fffff880`029e57f0 fffff800`02d01a6d : fffff800`02ef2724 fffff800`02e17634 fffff800`02c5a000 fffff880`029e6718 : nt!KiSystemServiceHandler+0x7c
fffff880`029e5830 fffff800`02d00845 : fffff800`02e20638 fffff880`029e58a8 fffff880`029e6718 fffff800`02c5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`029e5860 fffff800`02d117c1 : fffff880`029e6718 fffff880`029e5f70 fffff880`00000000 fffff8a0`12124b90 : nt!RtlDispatchException+0x415
fffff880`029e5f40 fffff800`02cd63c2 : fffff880`029e6718 00000000`0000006e fffff880`029e67c0 fffff8a0`12124be0 : nt!KiDispatchException+0x135
fffff880`029e65e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`02cd5c3c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032512-24289-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e46650
Debug session time: Sun Mar 25 20:42:53.140 2012 (UTC - 4:00)
System Uptime: 0 days 6:52:14.371
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff90000e3e823, 0, fffff96000610a85, 2}

Unable to load image cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll

Could not read faulting driver name
Probably caused by : cdd.dll ( cdd+10a85 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff90000e3e823, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000610a85, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb0100
 fffff90000e3e823 

FAULTING_IP: 
cdd+10a85
fffff960`00610a85 80bb0308000000  cmp     byte ptr [rbx+803h],0

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880037f8320 -- (.trap 0xfffff880037f8320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff900c2878638
rdx=0000000000000226 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000610a85 rsp=fffff880037f84b0 rbp=0000000000000226
 r8=0000000000000163  r9=0000000000000000 r10=fffffa8006cb1c30
r11=fffffa8006d51b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
cdd+0x10a85:
fffff960`00610a85 80bb0308000000  cmp     byte ptr [rbx+803h],0 ds:f8a0:00000000`00000803=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c29c50 to fffff80002c7ed40

STACK_TEXT:  
fffff880`037f81b8 fffff800`02c29c50 : 00000000`00000050 fffff900`00e3e823 00000000`00000000 fffff880`037f8320 : nt!KeBugCheckEx
fffff880`037f81c0 fffff800`02c7ce6e : 00000000`00000000 fffff900`00e3e823 00000000`00000300 fffff900`00e3e020 : nt! ?? ::FNODOBFM::`string'+0x43d76
fffff880`037f8320 fffff960`00610a85 : 00000000`00000000 fffff900`c00c0010 00000000`00000163 fffff800`02c87ef2 : nt!KiPageFault+0x16e
fffff880`037f84b0 00000000`00000000 : fffff900`c00c0010 00000000`00000163 fffff800`02c87ef2 00000000`00000000 : cdd+0x10a85


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd+10a85
fffff960`00610a85 80bb0308000000  cmp     byte ptr [rbx+803h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cdd+10a85

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x50_cdd+10a85

BUCKET_ID:  X64_0x50_cdd+10a85

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


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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032412-29952-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c650
Debug session time: Sat Mar 24 20:11:44.702 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:46.949
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa80a913c978, 0, fffff80002f79dcc, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80a913c978, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f79dcc, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb6100
 fffffa80a913c978 

FAULTING_IP: 
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`02f79dcc 0fb64518        movzx   eax,byte ptr [rbp+18h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ae228a0 -- (.trap 0xfffff8800ae228a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80a913c961 rbx=0000000000000000 rcx=fffffa80a913c960
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f79dcc rsp=fffff8800ae22a30 rbp=fffffa80a913c960
 r8=fffff8a001221000  r9=0000000000000000 r10=fffff80002f90f30
r11=fffff8800ae22ba8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObReferenceObjectByHandleWithTag+0x10c:
fffff800`02f79dcc 0fb64518        movzx   eax,byte ptr [rbp+18h] ss:0018:fffffa80`a913c978=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2fc1f to fffff80002c84d40

STACK_TEXT:  
fffff880`0ae22738 fffff800`02c2fc1f : 00000000`00000050 fffffa80`a913c978 00000000`00000000 fffff880`0ae228a0 : nt!KeBugCheckEx
fffff880`0ae22740 fffff800`02c82e6e : 00000000`00000000 fffffa80`a913c978 fffff8a0`020fac00 fffff8a0`01164fb0 : nt! ?? ::FNODOBFM::`string'+0x43d41
fffff880`0ae228a0 fffff800`02f79dcc : 00000000`c0000034 00000000`00000017 fffff8a0`0118ce80 fffff880`0ae22a88 : nt!KiPageFault+0x16e
fffff880`0ae22a30 fffff800`02f90fa1 : 00000000`00000000 00000000`00000001 fffffa80`04bdd9a0 00000000`00000001 : nt!ObReferenceObjectByHandleWithTag+0x10c
fffff880`0ae22b00 fffff800`02c83fd3 : fffffa80`04fae810 fffff880`0ae22ca0 00000000`00000002 00000000`0144e960 : nt!NtAlpcSendWaitReceivePort+0x71
fffff880`0ae22bb0 00000000`76ed1b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0144e228 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ed1b6a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`02f79dcc 0fb64518        movzx   eax,byte ptr [rbp+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+10c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+10c

BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+10c

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


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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032412-25334-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e9a650
Debug session time: Sat Mar 24 20:14:52.565 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:38.641
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001a3f62, fffff880029ec0c0, 0}

Probably caused by : win32k.sys ( win32k!TimersProc+126 )

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

1: 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: fffff960001a3f62, Address of the instruction which caused the bugcheck
Arg3: fffff880029ec0c0, 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: 
win32k!TimersProc+126
fffff960`001a3f62 ff80e4010000    inc     dword ptr [rax+1E4h]

CONTEXT:  fffff880029ec0c0 -- (.cxr 0xfffff880029ec0c0)
rax=0000000300000000 rbx=fffff900c2106f80 rcx=0000000000000003
rdx=fffff900c2106fe0 rsi=0000000000000026 rdi=fffff900c2106f98
rip=fffff960001a3f62 rsp=fffff880029ecaa0 rbp=000000000000001f
 r8=fffffa8007aa94a0  r9=000000000000000d r10=fffff80002c56000
r11=fffff880029ec9d0 r12=0000000000000000 r13=fffff960003c54e0
r14=0000000000000002 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!TimersProc+0x126:
fffff960`001a3f62 ff80e4010000    inc     dword ptr [rax+1E4h] ds:002b:00000003`000001e4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff960001a49a7 to fffff960001a3f62

STACK_TEXT:  
fffff880`029ecaa0 fffff960`001a49a7 : 00000000`00000000 fffff960`003c5cb0 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x126
fffff880`029ecaf0 fffff960`00135028 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000728 : win32k!RawInputThread+0x9ab
fffff880`029ecbc0 fffff960`001b529a : fffffa80`00000002 fffff880`029abf40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`029ecbf0 fffff800`02cd1fd3 : fffffa80`06dd83b0 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`029ecc20 000007fe`fde31eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0121f8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fde31eea


FOLLOWUP_IP: 
win32k!TimersProc+126
fffff960`001a3f62 ff80e4010000    inc     dword ptr [rax+1E4h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!TimersProc+126

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f2b63bd

STACK_COMMAND:  .cxr 0xfffff880029ec0c0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+126

BUCKET_ID:  X64_0x3B_win32k!TimersProc+126

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


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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032412-24694-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02053000 PsLoadedModuleList = 0xfffff800`02297650
Debug session time: Sat Mar 24 20:19:26.533 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:04.173
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {54, 2, 0, fffff8000200f3eb}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a )

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

1: 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: 0000000000000054, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8000200f3eb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002301100
 0000000000000054 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!IoMapTransfer+7
fffff800`0200f3eb 756e            jne     hal!IoMapTransfer+0x77 (fffff800`0200f45b)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009fb840 -- (.trap 0xfffff880009fb840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800649b5c0
rdx=fffffa80074ab660 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000200f3eb rsp=fffff880009fb9d0 rbp=fffffa8006fd5230
 r8=fffffa80064b0040  r9=fffffa8006491b70 r10=fffff880009e8dc0
r11=fffff880009fbab0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
hal!IoMapTransfer+0x7:
fffff800`0200f3eb 756e            jne     hal!IoMapTransfer+0x77 (fffff800`0200f45b) [br=1]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800020cf2e9 to fffff800020cfd40

STACK_TEXT:  
fffff880`009fb6f8 fffff800`020cf2e9 : 00000000`0000000a 00000000`00000054 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009fb700 fffff800`020cdf60 : fffffa80`06a28940 00000000`0000000c fffffa80`062e4950 fffffa80`06fd5238 : nt!KiBugCheckDispatch+0x69
fffff880`009fb840 fffff800`0200f3eb : fffffa80`06a28d18 fffffa80`064b0040 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009fb9d0 fffff800`0200e94f : 00000000`00000000 fffff800`0200bfb9 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x7
fffff880`009fba10 fffff800`0200f13d : fffffa80`06052050 fffffa80`0649b5c0 fffffa80`06491b00 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`009fbab0 fffff800`0200e71f : fffffa80`06fd51f0 00000000`00000008 fffffa80`0649b5c0 fffffa80`074ab660 : hal!HalAllocateAdapterChannel+0x101
fffff880`009fbaf0 fffff800`0200e420 : fffffa80`06052050 00000000`00000008 fffffa80`000000a0 fffff880`02346e6b : hal!HalBuildScatterGatherList+0x2f3
fffff880`009fbb60 fffff880`02345586 : fffffa80`06052050 00000000`00000000 fffffa80`06052d28 fffffa80`07489c20 : hal!HalGetScatterGatherList+0x44
fffff880`009fbbc0 fffff880`02342ea6 : fffffa80`06dac2b0 fffffa80`06052050 fffff800`0200e3dc fffffa80`060521a0 : USBPORT!USBPORT_Core_iMapTransfer+0x24a
fffff880`009fbc40 fffff880`02333f89 : fffffa80`06052050 00000000`00000000 fffffa80`06052d02 fffffa80`06052d28 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
fffff880`009fbca0 fffff800`020da51c : fffff880`009e8180 fffffa80`06052d28 fffffa80`06052d40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009fbcd0 fffff800`020c7a6a : fffff880`009e8180 fffff880`009f2f40 00000000`00000000 fffff880`02333db0 : nt!KiRetireDpcList+0x1bc
fffff880`009fbd80 00000000`00000000 : fffff880`009fc000 fffff880`009f6000 fffff880`009fbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iMapTransfer+24a
fffff880`02345586 4c63c0          movsxd  r8,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  USBPORT!USBPORT_Core_iMapTransfer+24a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iMapTransfer+24a

BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iMapTransfer+24a

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

ShaoLimper · 27 Mar 2012

I am going to run the ramtest and the driver find you reccomended, but am going to provide additional info for now.

I do use a Logitec mouse and an Omnitech cooling pad, but I have been using both of those since I bought the computer. You mentioned that it seems there is a USB device that is mucking up, could either of these be it?

ePeen · 27 Mar 2012

It depends, let's do memtest and driver verifier first :)

ShaoLimper · 27 Mar 2012

I did the memtest and it passed with 0 errors. I turned on verifier and am doing the 24 hour act normal thing.

ePeen · 27 Mar 2012

I would recommend doing at least 6-7 passes of Memtest. Memtest usually shows errors within the first few passes, but it's best to do at least 6-7 to be sure. I've seen Memtest not strike an error until the sixth pass a few times.

ShaoLimper · 28 Mar 2012

I have had a friend loom at it and he suspects that it is an overheating issue in the psu. lots of evidence to support that so I will just take it for warranty work. I will keep this topic open for when i get it back i case the problem persists.