BSOD after sleep

impy101

Reputable
Oct 11, 2014
2
0
4,510
Hi all,

I have been having this problem for a week or two now and it basically came out of nowhere; my pc gets a BSOD after awakening from sleep, after which it restarts and boots into Windows 7 normally again.

I read that I have to generate a crush dump so here it is:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03614000 PsLoadedModuleList = 0xfffff800`03857890
Debug session time: Sat Oct 11 05:07:38.300 2014 (UTC - 4:00)
System Uptime: 1 days 0:47:08.143
*******************************************************************************
* *
* 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: fffff880075902ef, The address that the exception occurred at
Arg3: fffff88004fdb598, Exception Record Address
Arg4: fffff88004fdadf0, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:
asmtxhci+162ef
fffff880`075902ef 488b0f mov rcx,qword ptr [rdi]

EXCEPTION_RECORD: fffff88004fdb598 -- (.exr 0xfffff88004fdb598)
ExceptionAddress: fffff880075902ef (asmtxhci+0x00000000000162ef)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000019
Attempt to read from address 0000000000000019

CONTEXT: fffff88004fdadf0 -- (.cxr 0xfffff88004fdadf0)
rax=00000000c0000056 rbx=fffffa80109e6e50 rcx=fffffa80109e6e50
rdx=fffffa800f9cca08 rsi=0000000000000005 rdi=0000000000000019
rip=fffff880075902ef rsp=fffff88004fdb7d0 rbp=0000000000000001
r8=0000000000000012 r9=0000000000000001 r10=00000000fffffff7
r11=fffff88004fdb980 r12=0000000000000008 r13=fffff880075c0000
r14=0000000000000000 r15=0000000000000100
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
asmtxhci+0x162ef:
fffff880`075902ef 488b0f mov rcx,qword ptr [rdi] ds:002b:00000000`00000019=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

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: 0000000000000019

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c1100
GetUlongFromAddress: unable to read from fffff800038c11c0
0000000000000019 Nonpaged pool

FOLLOWUP_IP:
asmtxhci+162ef
fffff880`075902ef 488b0f mov rcx,qword ptr [rdi]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff880075902ef

STACK_TEXT:
fffff880`04fdb7d0 00000000`00000001 : fffff880`075c1afc fffffa80`0f557c01 00000000`00000000 fffffa80`0f539a68 : asmtxhci+0x162ef
fffff880`04fdb7d8 fffff880`075c1afc : fffffa80`0f557c01 00000000`00000000 fffffa80`0f539a68 00000000`00000001 : 0x1
fffff880`04fdb7e0 fffffa80`0f557c01 : 00000000`00000000 fffffa80`0f539a68 00000000`00000001 fffffa80`40a40088 : asmtxhci+0x47afc
fffff880`04fdb7e8 00000000`00000000 : fffffa80`0f539a68 00000000`00000001 fffffa80`40a40088 fffff880`075c3289 : 0xfffffa80`0f557c01


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: asmtxhci+162ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: asmtxhci

IMAGE_NAME: asmtxhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d709ad3

STACK_COMMAND: .cxr 0xfffff88004fdadf0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_asmtxhci+162ef

BUCKET_ID: X64_0x7E_asmtxhci+162ef

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

Baget

Reputable
Oct 11, 2014
1
0
4,510
it seem like a problem with your USB 3.0 Controller...
did you tried to update the driver?