Bluescreens ohne Ende

Computer Forum

Zurück   Computer Forum - PC Forum - ModernBoard.de > Computerprobleme > Hardware Probleme

RB

Sie betrachten gerade: Bluescreens ohne Ende


Antwort
Alt 21.08.2009, 22:45 Bluescreens ohne Ende #1
Neuer Benutzer
 
Registriert seit: 21.08.2009
Beiträge: 3
Standard Bluescreens ohne Ende

Hallo

Ich weiß mitlerweile echt nicht mehr weiter. Bekomme seit einer Weile immer wieder Bluescreens unterschiedlicher Natur.
Die Minidumps hab ich mal hochgeladen. Vielleicht wird da ja jemand schlau drauß.

http://www.fileuploadx.de/390440

http://www.fileuploadx.de/277058

http://www.fileuploadx.de/625308

Um ein wenig präziser zu werden. Die Bluescreens treten nicht reproduzierbar bei diversen Anwendungen auf oder auch schon mal beim runterfahren des PC´s.
Tätigkeiten die ich schon durchgeführt habe (alle ohne Erfolg)

-alle Treiber neu
-neuer RAM
-System komplett neu aufgesetzt

Ich werde auch aus den Minidumps nicht so richtig schlau.
Also wenn mir mal jemand einen Rat geben könnte wie ich dem Problem auf die Schliche kommen könnte wäre ich sehr dankbar.

MfG

Alt 21.08.2009, 23:53 Bluescreens ohne Ende #2
.
 
Benutzerbild von heinzl
 
Registriert seit: 29.01.2008
Beiträge: 6.955
Standard

Was steht denn in den Bluescreens?
Welche Hardware?
Welches Betriebssystem?

Du glaubst hoffentlich nicht wirklich, daß ich mir den fileupdings mit Wartezeit und Werbegedöns antue
Alt 22.08.2009, 00:22 Bluescreens ohne Ende #3
Neuer Benutzer
Themenstarter
 
Registriert seit: 21.08.2009
Beiträge: 3
Standard

Win XP Pro
Zotac GTX 295
ASUS P5N32-E SLI
Intel Core 2 Quad Q6600
Soundblaster X-Fi Xtrem Music

Nr1


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


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 21 21:53:45.656 2009 (GMT+2)
System Uptime: 0 days 0:03:40.656
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
..
Loading User Symbols
Loading unloaded module list
.................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 805cfa8d, adb72a98, 0}

Probably caused by : ntoskrnl.exe ( nt!ArbPruneOrdering+122 )

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

3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 805cfa8d, The address that the exception occurred at
Arg3: adb72a98, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
nt!ArbPruneOrdering+122
805cfa8d 8b3e mov edi,dword ptr [esi]

TRAP_FRAME: adb72a98 -- (.trap 0xffffffffadb72a98)
ErrCode = 00000000
eax=00563960 ebx=00000000 ecx=00000800 edx=8a8f3ca0 esi=00563970 edi=00563960
eip=805cfa8d esp=adb72b0c ebp=adb72b20 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ArbPruneOrdering+0x122:
805cfa8d 8b3e mov edi,dword ptr [esi] ds:0023:00563970=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: nvsvc32.exe

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805c1007 to 805cfa8d

STACK_TEXT:
adb72b20 805c1007 00563960 00000800 00000288 nt!ArbPruneOrdering+0x122
adb72b50 805bb47a 00000000 89cff5b0 89cff5c8 nt!PipCreateMadeupNode+0x470
adb72b68 805266da 89cff5c8 00000000 00000068 nt!IopInitializeDCB+0x132
adb72b98 805c29eb e3049370 89cff5c8 00000068 nt!PsReturnProcessPagedPoolQuota+0x10c
adb72ba4 00000000 00000000 001f03ff 00000001 nt!IopSetRegistryStringValue+0x1


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ArbPruneOrdering+122
805cfa8d 8b3e mov edi,dword ptr [esi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ArbPruneOrdering+122

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0x8E_nt!ArbPruneOrdering+122

BUCKET_ID: 0x8E_nt!ArbPruneOrdering+122

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


Nr2


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


Loading Dump File [C:\WINDOWS\Minidump\Mini082109-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 21 23:01:59.453 2009 (GMT+2)
System Uptime: 0 days 0:36:45.095
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
..
Loading User Symbols
Loading unloaded module list
................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {81d75d0, 2, 0, 8054bfcb}

*** WARNING: Unable to verify timestamp for NDIS.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1b3 )

Followup: Pool_corruption
---------

3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 081d75d0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8054bfcb, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+1b3
8054bfcb 8b06 mov eax,dword ptr [esi]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805c0da8 to 8054bfcb

STACK_TEXT:
b854bb98 805c0da8 00000000 00000001 e5726854 nt!ExDeferredFreePool+0x1b3
b854bbbc 805c14a6 881590e0 805bc300 00000000 nt!PipCreateMadeupNode+0x1d3
b854bbf0 805d0189 805bc300 8a8f3ca0 00000000 nt!MmGetSystemRoutineAddress+0x78
b854bd4c 805d1139 b854bdb4 001f03ff 00000000 nt!IopSetupArbiterAndTranslators+0x144
b854bd80 b7df3bd8 b854bdb4 001f03ff 00000000 nt!IopCreateCmResourceList+0x28
b854bdac 805cff70 000007d0 00000000 00000000 NDIS!ndisWorkerThread+0x4b
b854bddc 805460ee b7df3b85 00000000 00000000 nt!IopQueryReconfiguration+0x23
b854bdf8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x7b


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+1b3
8054bfcb 8b06 mov eax,dword ptr [esi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExDeferredFreePool+1b3

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+1b3

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+1b3

Followup: Pool_corruption
---------



Alt 22.08.2009, 00:22 Bluescreens ohne Ende #4
Neuer Benutzer
Themenstarter
 
Registriert seit: 21.08.2009
Beiträge: 3
Standard

Nr3

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


Loading Dump File [C:\WINDOWS\Minidump\Mini082109-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 21 23:14:49.781 2009 (GMT+2)
System Uptime: 0 days 0:11:54.433
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.
Loading User Symbols
Loading unloaded module list
.......................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 805cfa8d, b851bc30, b851b92c}

Probably caused by : ntoskrnl.exe ( nt!ArbPruneOrdering+122 )

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

3: 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: c0000005, The exception code that was not handled
Arg2: 805cfa8d, The address that the exception occurred at
Arg3: b851bc30, Exception Record Address
Arg4: b851b92c, Context Record Address

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


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

FAULTING_IP:
nt!ArbPruneOrdering+122
805cfa8d 8b3e mov edi,dword ptr [esi]

EXCEPTION_RECORD: b851bc30 -- (.exr 0xffffffffb851bc30)
ExceptionAddress: 805cfa8d (nt!ArbPruneOrdering+0x00000122)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0a4db208
Attempt to read from address 0a4db208

CONTEXT: b851b92c -- (.cxr 0xffffffffb851b92c)
eax=0a4db1f8 ebx=00000000 ecx=00000800 edx=8a8f3ca0 esi=0a4db208 edi=0a4db1f8
eip=805cfa8d esp=b851bcf8 ebp=b851bd0c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ArbPruneOrdering+0x122:
805cfa8d 8b3e mov edi,dword ptr [esi] ds:0023:0a4db208=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 0a4db208

READ_ADDRESS: 0a4db208

FOLLOWUP_IP:
nt!ArbPruneOrdering+122
805cfa8d 8b3e mov edi,dword ptr [esi]

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805c1007 to 805cfa8d

STACK_TEXT:
b851bd0c 805c1007 0a4db1f8 00000800 00000288 nt!ArbPruneOrdering+0x122
b851bd3c 805bb47a 00000000 87f83bb0 87f83bc8 nt!PipCreateMadeupNode+0x470
b851bd54 805266da 87f83bc8 00000000 806e7a3c nt!IopInitializeDCB+0x132
b851bdac 805cff70 00000000 00000000 00000000 nt!PsReturnProcessPagedPoolQuota+0x10c
b851bddc 805460ee 8053868e 00000002 00000000 nt!IopQueryReconfiguration+0x23
b851bdf8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x7b


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ArbPruneOrdering+122

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

STACK_COMMAND: .cxr 0xffffffffb851b92c ; kb

FAILURE_BUCKET_ID: 0x7E_nt!ArbPruneOrdering+122

BUCKET_ID: 0x7E_nt!ArbPruneOrdering+122

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

RB

Thema: Bluescreens ohne Ende


Themen-Optionen Thema durchsuchen
Thema durchsuchen:

Erweiterte Suche
Ansicht

Ähnliche Themen für: Bluescreens ohne Ende
Thema Autor Forum Antworten Letzter Beitrag
Witze ohne ende
Kräht der maulwurf auf dem dach liegt der hahn vor lachen flach. In alaska nennt man die leichten mädchen ja frostituierte. Mann sagt...
Trias Fun Box 63 25.05.2012 22:18
Mein PC am Ende ? (erst Bluescreens, dann einfrieren, jetzt bootet er nichtmals)
Hier meldet sich ein weiterer ratloser Pc Nutzer. Mein System hat jetzt ein gutes Jahr auf dem Buckel und irgendwo ist der Wurm drin. Ich habe in...
Xaero Hardware Probleme 1 01.01.2009 17:41
Win XP Bluescreens ohne ende!
Hallo, Ich hoffe ihr könnt mir weiterhelfen denn es ist echt dringend. Ich habe folgendes Problem: Ich habe meinen Rechner Neu installiert und...
HH-Keal Windows XP Probleme 2 20.08.2007 13:46
iPods ohne Ende
iPods verkaufen sich zur Zeit wie warme Semmeln. In den letzten drei Jahren stiegen die Verkaufszahlen um insgesamt 50%. Mit froher Miene verkündete...
Yannick News 18 30.01.2007 18:01
Was ist das?Garfikkartenpower ohne Ende
Hallo! Diese Grafikkarte hat es echt in sich, sie kostet ein Schweinegeld und hat in z.B CS 3400 FPS. Aber warum gibt es solche grafikkarten...
Black Hawk News 6 25.07.2006 15:17

Zurück   Computer Forum - PC Forum - ModernBoard.de > Computerprobleme > Hardware Probleme

Besucher kamen mit folgenden Begriffen auf die Seite

systemresourceslist->flink chain invalid. resource may be corrupted or already deleted.

,

ntoskrnl.exe system_thread_exception_not_handled_m (1000007e)

,

0xc0000005 - die anweisung in 0xlx verweist auf speicher 0xlx. der vorgang %s konnte nicht im speicher durchgef hrt werden.

Powered by vBadvanced CMPS v3.2.2


Sie betrachten gerade: Bluescreens ohne Ende