Answered by:
Blue Screen after i changed computer case

Question
-
So i wanted to get a new computer case so i did. It got here, i changed all my hardware to the new case now windows gives me a blue screen as soon as it shows my desktop.
Heres my dump files. Please help ASAP. Thanks
http://www.mediafire.com/?3zwp6o9zl512edj
http://www.mediafire.com/?y0bccygoccedf2z
http://www.mediafire.com/?j33mhm82bb0hjrp
http://www.mediafire.com/?pyfsa7i1t1x74pp
Saturday, December 29, 2012 8:54 PM
Answers
-
Hi,
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa8c0aab15b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007bb0e34, address which referenced memoryDebugging Details:
------------------
READ_ADDRESS: fffffa8c0aab15b8CURRENT_IRQL: 2
FAULTING_IP:
EtronXHCI+4e34
fffff880`07bb0e34 418b8c818c000000 mov ecx,dword ptr [r9+rax*4+8Ch]CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: audiodg.exe
TRAP_FRAME: fffff8800cd12c40 -- (.trap 0xfffff8800cd12c40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002fffffffd rbx=0000000000000000 rcx=00000000000000c0
rdx=0000000000000024 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007bb0e34 rsp=fffff8800cd12dd0 rbp=0000000000000c00
r8=0000000000000000 r9=fffffa800aab1538 r10=00000000000000c0
r11=fffffa800a848130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
EtronXHCI+0x4e34:
fffff880`07bb0e34 418b8c818c000000 mov ecx,dword ptr [r9+rax*4+8Ch] ds:fffffa8c`0aab15b8=????????
Resetting default scopeLAST_CONTROL_TRANSFER: from fffff80003285b29 to fffff800032865c0
STACK_TEXT:
fffff880`0cd12af8 fffff800`03285b29 : 00000000`0000000a fffffa8c`0aab15b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0cd12b00 fffff800`032847a0 : 00000000`00000001 00000000`00000000 fffff880`0cd12cc0 fffff8a0`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0cd12c40 fffff880`07bb0e34 : fffffa80`08e74bb0 00000000`0000001e fffffa80`09752b40 fffffa80`0991ec60 : nt!KiPageFault+0x260
fffff880`0cd12dd0 fffffa80`08e74bb0 : 00000000`0000001e fffffa80`09752b40 fffffa80`0991ec60 00000000`0000001e : EtronXHCI+0x4e34
fffff880`0cd12dd8 00000000`0000001e : fffffa80`09752b40 fffffa80`0991ec60 00000000`0000001e fffffa80`09752b40 : 0xfffffa80`08e74bb0
fffff880`0cd12de0 fffffa80`09752b40 : fffffa80`0991ec60 00000000`0000001e fffffa80`09752b40 00000000`00000000 : 0x1e
fffff880`0cd12de8 fffffa80`0991ec60 : 00000000`0000001e fffffa80`09752b40 00000000`00000000 fffff880`07bb44a6 : 0xfffffa80`09752b40
fffff880`0cd12df0 00000000`0000001e : fffffa80`09752b40 00000000`00000000 fffff880`07bb44a6 00000000`00000000 : 0xfffffa80`0991ec60
fffff880`0cd12df8 fffffa80`09752b40 : 00000000`00000000 fffff880`07bb44a6 00000000`00000000 fffffa80`0991ec60 : 0x1e
fffff880`0cd12e00 00000000`00000000 : fffff880`07bb44a6 00000000`00000000 fffffa80`0991ec60 fffffa80`08e74a60 : 0xfffffa80`09752b40
STACK_COMMAND: kbFOLLOWUP_IP:
EtronXHCI+4e34
fffff880`07bb0e34 418b8c818c000000 mov ecx,dword ptr [r9+rax*4+8Ch]SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: EtronXHCI+4e34
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: EtronXHCI
IMAGE_NAME: EtronXHCI.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e2de090
FAILURE_BUCKET_ID: X64_0xD1_EtronXHCI+4e34
BUCKET_ID: X64_0xD1_EtronXHCI+4e34
Followup: MachineOwner
The culprit is EtronXHCI.sys which is the Etron eXtensible Host Controller Driver. You can uninstall the driver and reinstall the latest driver for check. If the issue perisist, I suggest for now that you disable the EtronXHCI.sys driver.
This will show whether it is really the cause (I suspect it is) or is just being blamed. The easiest way to disable it is to go to your drivers folder in C:\Windows\System32 and rename it by changing the .sys extension to something else like .old. Be aware this will also "break" the software that uses this driver.
Spencer
TechNet Community Support- Marked as answer by Spencer Xi Monday, January 7, 2013 5:02 AM
Monday, December 31, 2012 4:54 AM