Bluescreen bei Windows 7 - Fehleranalyse, Treiberproblem oder Hardwarebeschädigung?

Hallo,

habe mir ein neues PC-System zugelegt:

• AMD Athlon 640 X4 Prozessor
• 4GB DDR3 RAM
• ASRock N68C-S UCC Mainboard
• DVD
• 500GB S-ATA
• Line 6 UX1 Audiointerface

Plötzlich bekam ich während des surfens (benutze Google Chrome Webbrowser) einen Bluescreen. Habe mir danach "Debugging Tools für Windows" heruntergeladen und die DUMP Datei des Bluescreens gecheckt, folgende Ergebnisse bekam ich:





Microsoft (R) Windows Debugger Version 6.4.0007.2

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\121210-19515-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 Longhorn Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50

Debug session time: Sun Dec 12 15:51:33.237 2010 (GMT+1)

System Uptime: 0 days 2:34:43.800

Loading Kernel Symbols

...............................................................................................................................................................

Loading unloaded module list

.....

Loading User Symbols

Unable to load image \SystemRoot\System32\Drivers\L6UX164.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for L6UX164.sys

*** ERROR: Module load completed but symbols could not be loaded for L6UX164.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 1000007E, {ffffffffc0000005, fffff8800524cd21, fffff88004a5e9d8, fffff88004a5e240}



Probably caused by : L6UX164.sys ( L6UX164+19d21 )



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: fffff8800524cd21, The address that the exception occurred at

Arg3: fffff88004a5e9d8, Exception Record Address

Arg4: fffff88004a5e240, Context Record Address



Debugging Details:

------------------





ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.



FAULTING_IP:

L6UX164+19d21

fffff880`0524cd21 66814b0a0020 or word ptr [rbx+0xa],0x2000



EXCEPTION_PARAMETER1: fffff88004a5e9d8



CONTEXT: fffff88004a5e240 -- (.cxr fffff88004a5e240)

rax=fffffa80079d5270 rbx=0000000000000000 rcx=fffffa80065c73a8

rdx=0000000000000000 rsi=fffffa80079d5270 rdi=fffffa80065c70b8

rip=fffff8800524cd21 rsp=fffff88004a5ec10 rbp=fffff88008c6c748

r8=fffffa8003acb400 r9=0000000000000000 r10=0000000000000000

r11=0000000000000000 r12=fffffa80046da600 r13=0000000000000000

r14=0000000000000000 r15=fffff80004117080

iopl=0 nv up ei ng nz na pe nc

cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282

L6UX164+0x19d21:

fffff880`0524cd21 66814b0a0020 or word ptr [rbx+0xa],0x2000 ds:002b:000a=????

Resetting default scope



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: DRIVER_FAULT



BUGCHECK_STR: 0x7E



CURRENT_IRQL: 0



LAST_CONTROL_TRANSFER: from fffffa8003ac3610 to fffff8800524cd21



STACK_TEXT:

fffff880`04a5ec10 fffffa80`03ac3610 : fffff880`08c6c748 fffffa80`03a1c4e0 fffffa80`065c70b8 fffff880`04a5ec40 : L6UX164+0x19d21

fffff880`04a5ec18 fffff880`08c6c748 : fffffa80`03a1c4e0 fffffa80`065c70b8 fffff880`04a5ec40 fffffa80`07323b60 : 0xfffffa80`03ac3610

fffff880`04a5ec20 fffffa80`03a1c4e0 : fffffa80`065c70b8 fffff880`04a5ec40 fffffa80`07323b60 fffffa80`000001b9 : 0xfffff880`08c6c748

fffff880`04a5ec28 fffffa80`065c70b8 : fffff880`04a5ec40 fffffa80`07323b60 fffffa80`000001b9 00000000`00000000 : 0xfffffa80`03a1c4e0

fffff880`04a5ec30 fffff880`04a5ec40 : fffffa80`07323b60 fffffa80`000001b9 00000000`00000000 00000000`00000000 : 0xfffffa80`065c70b8

fffff880`04a5ec38 fffffa80`07323b60 : fffffa80`000001b9 00000000`00000000 00000000`00000000 fffff800`02ac2cff : 0xfffff880`04a5ec40

fffff880`04a5ec40 fffffa80`000001b9 : 00000000`00000000 00000000`00000000 fffff800`02ac2cff fffff800`04117080 : 0xfffffa80`07323b60

fffff880`04a5ec48 00000000`00000000 : 00000000`00000000 fffff800`02ac2cff fffff800`04117080 00000000`00000000 : 0xfffffa80`000001b9

fffff880`04a5ec50 00000000`00000000 : fffff800`02ac2cff fffff800`04117080 00000000`00000000 fffff880`00000000 : 0x0

fffff880`04a5ec58 fffff800`02ac2cff : fffff800`04117080 00000000`00000000 fffff880`00000000 fffffa80`05617080 : 0x0

fffff880`04a5ec60 fffff880`052360ef : fffffa80`065c70b8 00000000`00000080 fffffa80`036ca040 00000000`00000000 : nt!KeWaitForSingleObject+0x19f

fffff880`04a5ed00 fffffa80`065c70b8 : 00000000`00000080 fffffa80`036ca040 00000000`00000000 fffff880`02f63180 : L6UX164+0x30ef

fffff880`04a5ed08 00000000`00000080 : fffffa80`036ca040 00000000`00000000 fffff880`02f63180 00000000`00000000 : 0xfffffa80`065c70b8

fffff880`04a5ed10 fffffa80`036ca040 : 00000000`00000000 fffff880`02f63180 00000000`00000000 fffff800`02c41c40 : 0x80

fffff880`04a5ed18 00000000`00000000 : fffff880`02f63180 00000000`00000000 fffff800`02c41c40 fffff800`02d5dc06 : 0xfffffa80`036ca040

fffff880`04a5ed20 fffff880`02f63180 : 00000000`00000000 fffff800`02c41c40 fffff800`02d5dc06 00000000`03ebc62f : 0x0

fffff880`04a5ed28 00000000`00000000 : fffff800`02c41c40 fffff800`02d5dc06 00000000`03ebc62f fffff800`02c33e80 : 0xfffff880`02f63180

fffff880`04a5ed30 fffff800`02c41c40 : fffff800`02d5dc06 00000000`03ebc62f fffff800`02c33e80 fffffa80`07323b60 : 0x0

fffff880`04a5ed38 fffff800`02d5dc06 : 00000000`03ebc62f fffff800`02c33e80 fffffa80`07323b60 00000000`00000001 : nt!KiInitialThread

fffff880`04a5ed40 fffff800`02a97c26 : fffff800`02c33e80 fffffa80`07323b60 fffff800`02c41c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`04a5ed80 00000000`00000000 : fffff880`04a5f000 fffff880`04a59000 fffff880`04a5e920 00000000`00000000 : nt!KxStartSystemThread+0x16





FOLLOWUP_IP:

L6UX164+19d21

fffff880`0524cd21 66814b0a0020 or word ptr [rbx+0xa],0x2000



SYMBOL_STACK_INDEX: 0



FOLLOWUP_NAME: MachineOwner



SYMBOL_NAME: L6UX164+19d21



MODULE_NAME: L6UX164



IMAGE_NAME: L6UX164.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 4900fd81



STACK_COMMAND: .cxr fffff88004a5e240 ; kb



FAILURE_BUCKET_ID: X64_0x7E_L6UX164+19d21



BUCKET_ID: X64_0x7E_L6UX164+19d21



Followup: MachineOwner

---------


Kann mir anhand dieser Auswertung nun jemand sagen wo das Problem liegt? Ich blicke da leider nicht durch!
Vielen Dank!

 

Wenn es sich hier um einen Fertig-PC handelt ab zum Händler und Garantie beanspruchen.