BlueScreen Vista64

[f3rr1s]

Hallo mein Freund hat Probleme mit seinem PC er stürtzt öfters per BlueScreen ab.
Der gerne beim Surfen, Spielen abstürtzt, eigentlich nicht nachvollziebar warum, wirkt sehr willkürlich.
Das Problem war vor 1 Woche schlimmer, nach einer Systemwiederherstellung war 1 Woche nix jetzt fängt es wieder an, ohne das er was verändert hat.

HW:
AMD 9850 BE
Asus M3A78
Kingston HyperX 1066 4GB
ATI HD 4850 (Catalyst 09.7)

Win Vista64

Dann hat er mir noch einen Fehler bericht gegeben keine ahnung ob ihr vielleicht damit etwas anfangen könnt.

Vielleicht habt ihr ja eine Idee woran es liegt...

Gruß

"Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.0.6001.2.1.0.768.3
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 000000000000000B
BCP3: 0000000000000001
BCP4: FFFFF800024E2C99
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\Mini120709-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-61495-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WER1332.tmp.version.txt

Lesen Sie unsere Datenschutzrichtlinie:
Microsoft-Absturzanalyse





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


Loading Dump File [C:\Windows\Minidump\Mini120709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows Longhorn Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18304.amd64fre.vistasp1_gdr.090805-0102
Kernel base = 0xfffff800`02412000 PsLoadedModuleList = 0xfffff800`025d7db0
Debug session time: Mon Dec 7 20:25:12.140 2009 (GMT+1)
System Uptime: 0 days 0:08:26.420
Loading Kernel Symbols
................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, b, 1, fffff800024e2c99}

Probably caused by : ntkrnlmp.exe ( nt!EtwGetInterruptTimeStamp+29 )

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

3: kd> g
^ No runnable debuggees error in 'g'
3: kd> gh
^ No runnable debuggees error in 'gh'
3: 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: 0000000000000000, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800024e2c99, address which referenced memory

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


WRITE_ADDRESS: unable to get MiSystemVaType - probably bad symbols
0000000000000000

CURRENT_IRQL: b

FAULTING_IP:
nt!EtwGetInterruptTimeStamp+29
fffff800`024e2c99 4c891b mov [rbx],r11

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff8000246646e to fffff800024666d0

STACK_TEXT:
fffffa60`019f97e8 fffff800`0246646e : 00000000`0000000a 00000000`00000000 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx
fffffa60`019f97f0 fffff800`0246534b : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`019f9930 fffff800`024e2c99 : fffffa60`019f9cb0 fffffa60`019f9bd0 00000000`00000000 00000001`b04dd296 : nt!KiPageFault+0x20b
fffffa60`019f9ac0 fffff800`0246758d : fffffa80`04a25a88 fffffa80`06357050 00000000`00000000 fffffa80`04a25a80 : nt!EtwGetInterruptTimeStamp+0x29
fffffa60`019f9b00 fffff800`024673c2 : 00000000`00000001 fffffa60`019f9bd0 fffffa60`019d5a00 00000000`00000000 : nt!KiScanInterruptObjectList+0x3d
fffffa60`019f9b50 fffffa60`00d53552 : fffffa60`00d52435 00000001`b04dd330 fffffa60`019f9d50 fffffa60`019d2180 : nt!KiChainedDispatch+0x112
fffffa60`019f9ce8 fffffa60`00d52435 : 00000001`b04dd330 fffffa60`019f9d50 fffffa60`019d2180 fffff800`024489b9 : processr!C1Halt+0x2
fffffa60`019f9cf0 fffff800`02481ab8 : fffffa80`06e0c040 fffffa60`019dbd40 fffffa60`019f9db0 fffff800`02469d6d : processr!C1Idle+0x9
fffffa60`019f9d20 fffff800`02470e31 : fffffa60`019d2180 00000000`0004c0be 00000000`00000000 00000000`00000000 : nt!PoIdle+0x148
fffffa60`019f9d80 fffff800`0263f5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x21
fffffa60`019f9db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


FOLLOWUP_IP:
nt!EtwGetInterruptTimeStamp+29
fffff800`024e2c99 4c891b mov [rbx],r11

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!EtwGetInterruptTimeStamp+29

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a796b09

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_0xA_W_nt!EtwGetInterruptTimeStamp+29

BUCKET_ID: X64_0xA_W_nt!EtwGetInterruptTimeStamp+29

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

 

[f3rr1s]

OC hat er nicht.
Memtest habe ich ihm auch schon, zu geraten...

Er versucht jetzt erst mal Win7 ob es damit wieder funktioniert... mal schaun :]
Danke für die Hilfe