BSOD on computer

William Dieu

Honorable
Mar 12, 2013
7
0
10,510
A few days ago, I began to get bsod daily and now it's starting to bug me. Previously when I had it, I used CCleaner but now it is no longer sufficient. I can give you the dump file read. Also my specs are: i7 3820 (yes just realised it couldn't a k series), Asus Rampage IV Formula with BF3, GTX 580 (670 was outta stock), Corsair 8GB 2x4 1600mhz (used memtest for a long time no probs), silverstone 1000w psu (yes too much) and ocz 120gb. Dump file:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022613-20467-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
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0340c000 PsLoadedModuleList = 0xfffff800`03650670
Debug session time: Tue Feb 26 20:31:12.074 2013 (UTC + 11:00)
System Uptime: 0 days 2:09:48.948
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..................................................
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88015a1bbf6, fffff8800cf4b708, fffff8800cf4af60}

Probably caused by : asmtxhci.sys ( asmtxhci+1bbf6 )

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

4: 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: fffff88015a1bbf6, The address that the exception occurred at
Arg3: fffff8800cf4b708, Exception Record Address
Arg4: fffff8800cf4af60, 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:
asmtxhci+1bbf6
fffff880`15a1bbf6 408ab1ec000000 mov sil,byte ptr [rcx+0ECh]

EXCEPTION_RECORD: fffff8800cf4b708 -- (.exr 0xfffff8800cf4b708)
ExceptionAddress: fffff88015a1bbf6 (asmtxhci+0x000000000001bbf6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000ec
Attempt to read from address 00000000000000ec

CONTEXT: fffff8800cf4af60 -- (.cxr 0xfffff8800cf4af60)
rax=0000000000000002 rbx=fffffa80113d7250 rcx=0000000000000000
rdx=fffffa80113d7250 rsi=0000000000000000 rdi=fffffa800cfcb2e8
rip=fffff88015a1bbf6 rsp=fffff8800cf4b940 rbp=fffffa800dc50660
r8=0000000000000000 r9=0000000000000409 r10=fffff88008962bf8
r11=fffffa800d130140 r12=fffffa800cfcb2d0 r13=0000000000000409
r14=0000000000000000 r15=fffffa80111b8fa8
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
asmtxhci+0x1bbf6:
fffff880`15a1bbf6 408ab1ec000000 mov sil,byte ptr [rcx+0ECh] ds:002b:00000000`000000ec=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 1

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: 00000000000000ec

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ba100
GetUlongFromAddress: unable to read from fffff800036ba1c0
00000000000000ec Nonpaged pool

FOLLOWUP_IP:
asmtxhci+1bbf6
fffff880`15a1bbf6 408ab1ec000000 mov sil,byte ptr [rcx+0ECh]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffffa80113d7250 to fffff88015a1bbf6

STACK_TEXT:
fffff880`0cf4b940 fffffa80`113d7250 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : asmtxhci+0x1bbf6
fffff880`0cf4b948 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`113d7250


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: asmtxhci+1bbf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: asmtxhci

IMAGE_NAME: asmtxhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4eb203c6

STACK_COMMAND: .cxr 0xfffff8800cf4af60 ; kb

FAILURE_BUCKET_ID: X64_0x7E_asmtxhci+1bbf6

BUCKET_ID: X64_0x7E_asmtxhci+1bbf6

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

harmster

Honorable
Dec 14, 2012
66
0
10,660
Hi there.

• 0x000007E System Thread Not Handled Memory / CPU

Normally if you get the 0x7E BSOD there are problems with memory or CPU. You could check it by swapping out memory / memory slots. Also try to set your BIOS to default factory settings ( if for example you are running on a OC ). To check if the problem is your CPU you can try run some CPU stress programs like Prime95.

Good luck.