Immer wieder Bluescreen! Woran liegts?!

danke für deinen freundlichen beitrag

damit ich dir das sagen kann: wenn du es 100000mal runterlädst bekomme ich 1cent und überhole damit bill gates

ja ich hab überhaupt keine ahnung aber ihr sollt alle vor neid erblassen weil ich einen super computer habe und nicht einige details nennen wollte in der kurzen zeit die ich zu der zeit noch hatte >.<
der pc wurde zusammengebaut

Das System wurde neu gestartet, ohne dass es zuvor ordnungsgemäß heruntergefahren wurde. Dieser Fehler kann auftreten, wenn das System nicht mehr reagiert hat oder abgestürzt ist oder die Stromzufuhr unerwartet unterbrochen wurde.
BugcheckCode 30
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80002e870c1
BugcheckParameter3 0x0
BugcheckParameter4 0xffffffffffffffff
SleepInProgress false
PowerButtonTimestamp 0

icq7.4 wurde zuletzt installiert
treiber sind aktuell sp1 ist installiert
temperaturen cpu 30 gpu 50 hdd 30

beim nächsten bluescreen der folgt kann ich die fehlermeldung abschreiben


mfg marabunta

IRQL_NOT_LESS_OR_EQUAL
0x0000000A
beim nächsten mal kam
0x0000001E

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


Loading Dump File [C:\Users\Marabunta\Desktop\040911-38345-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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`0305ae90
Debug session time: Sat Apr 9 20:29:10.131 2011 (UTC + 2:00)
System Uptime: 0 days 0:02:46.052
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*

• *
• Bugcheck Analysis *
• *

*

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002e890c1, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )

Followup: MachineOwner

0: kd> !analyze -v
*

• *
• Bugcheck Analysis *
• *

*

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e890c1, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:


EXCEPTION_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:
nt!KiApcInterrupt+1f1
fffff800`02e890c1 48cf iretq

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c60e8
ffffffffffffffff

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: mscorsvw.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ee1028 to fffff80002e95640

STACK_TEXT:
fffff880`0bb7b9c8 fffff800`02ee1028 : 00000000`0000001e ffffffff`c0000005 fffff800`02e890c1 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bb7b9d0 fffff800`02e94cc2 : fffff880`0bb7c1a8 00000000`0000004f fffff880`0bb7c250 00000000`00000014 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0bb7c070 fffff800`02e935ca : 00000000`00000000 fffffa80`0654b670 fffffa80`0654c990 00000000`00000014 : nt!KiExceptionDispatch+0xc2
fffff880`0bb7c250 fffff800`02e890c1 : fffffa80`06544177 00000000`00000000 00000000`00000200 00000001`0bb7c410 : nt!KiGeneralProtectionFault+0x10a
fffff880`0bb7c3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x1f1


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiApcInterrupt+1f1
fffff800`02e890c1 48cf iretq

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!KiApcInterrupt+1f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiApcInterrupt+1f1

BUCKET_ID: X64_0x1E_c0000005_nt!KiApcInterrupt+1f1

Followup: MachineOwner

Hallo,

nein kann passiert genauso nach reset oder wenn selbst wenn es stundenlang läuft kann man es durch installation von amd treibern oder hypercam "auslösen".

nicht von anfang an es lief ca. 1monat lang gut. neu aufsetzen bringt nur solang was wie grafikkarten treiber nicht drauf ist.

nein


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 09.04.2011 19:05:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-31340-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0x9, 0x2, 0x0, 0xFFFFF80002EA8194)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 09.04.2011 19:05:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0xA123)
Bugcheck code: 0xA (0x9, 0x2, 0x0, 0xFFFFF80002EA8194)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 09.04.2011 18:52:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-34335-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002EFD194)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 09.04.2011 18:29:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-38345-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E890C1, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 09.04.2011 17:58:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-30451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002EC20C1, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 09.04.2011 17:53:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-34023-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0x3010276, 0x2, 0x0, 0xFFFFF80002EE4015)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 09.04.2011 14:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-20997-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E870C1, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.