Zurück   Trojaner-Board > Web/PC > Alles rund um Windows

Alles rund um Windows: Windows 8.1 Bluescreens

Windows 7 Hilfe zu allen Windows-Betriebssystemen: Windows XP, Windows Vista, Windows 7, Windows 8(.1) und Windows 10 - als auch zu sämtlicher Windows-Software. Alles zu Windows 10 ist auch gerne willkommen. Bitte benenne etwaige Fehler oder Bluescreens unter Windows mit dem Wortlaut der Fehlermeldung und Fehlercode. Erste Schritte für Hilfe unter Windows.

Antwort
Alt 29.07.2015, 18:11   #1
Tendalor
 
Windows 8.1 Bluescreens - Standard

Problem: Windows 8.1 Bluescreens



Guten Tag,

ich habe seit ca. einem Monat sehr unregelmäßige Bluescreens. Anfangs dachte ich es liegt an dem sich überhitzenden Prozessor. Nachdem ich neue Wärmeleitpaste aufgetragen hatte und der Prozessor wieder normal lief, blieben die Bluescreens dennoch nicht aus.

Ich bekomme die Bluescreens nur wenn ich ein Spiel am laufen hab. Da aber zu 90% der Zeit ein Spiel läuft weis, ich nicht ob man das berücksichtigen kann.

Diverse Programme zur Analyse habe ich bereits heruntergeladen und durchlaufen lassen.

Dies ist der Report von "WhoCrashed" :

System Information (local)
--------------------------------------------------------------------------------

computer name: TENDALOR
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8P67
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8565686272 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 24.07.2015 14:20:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072415-10875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0xA (0xFFFFFFFFFFFF00FF, 0x2, 0x1, 0xFFFFF802E3F20988)
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 that cannot be identified at this time.



On Thu 16.07.2015 16:04:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071615-18906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFC000443DA940)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 that cannot be identified at this time.



On Wed 15.07.2015 15:33:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071515-11140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x1A (0x5001, 0xFFFFF58010804000, 0xC3B, 0xC3CFFF18FE)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 30.06.2015 14:54:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-10890-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x21104)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001C8104, 0xFFFFD001F93F0E50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.



On Tue 30.06.2015 14:52:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-4953-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x32CDD0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80121FFBDD0, 0xFFFFF80274372A00, 0xB)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED









Dies sind die Daten von "BlueScreenView" :

==================================================
Dump File : 072415-10875-01.dmp
Crash Time : 24.07.2015 16:20:17
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`ffff00ff
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff802`e3f20988
Caused By Driver : portcls.sys
Caused By Address : portcls.sys+5ca7
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072415-10875-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 376.552
Dump File Time : 24.07.2015 16:21:23
==================================================

==================================================
Dump File : 071615-18906-01.dmp
Crash Time : 16.07.2015 18:04:35
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00001200
Parameter 3 : 00000000`00000000
Parameter 4 : ffffc000`443da940
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+24010
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071615-18906-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 314.816
Dump File Time : 16.07.2015 18:05:55
==================================================

==================================================
Dump File : 071515-11140-01.dmp
Crash Time : 15.07.2015 17:33:16
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005001
Parameter 2 : fffff580`10804000
Parameter 3 : 00000000`00000c3b
Parameter 4 : 000000c3`cfff18fe
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+150ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071515-11140-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 316.976
Dump File Time : 15.07.2015 18:56:48
==================================================

==================================================
Dump File : 063015-10890-01.dmp
Crash Time : 30.06.2015 16:54:19
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`001c8104
Parameter 3 : ffffd001`f93f0e50
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+21104
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\063015-10890-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 314.584
Dump File Time : 30.06.2015 17:08:50
==================================================

==================================================
Dump File : 063015-4953-01.dmp
Crash Time : 30.06.2015 16:52:29
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff801`21ffbdd0
Parameter 3 : fffff802`74372a00
Parameter 4 : 00000000`0000000b
Caused By Driver : ndis.sys
Caused By Address : ndis.sys+118d1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\063015-4953-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 359.680
Dump File Time : 30.06.2015 16:53:17
==================================================

Anbei hänge ich noch 2 Screenshots von "Open Hardware Monitor" an.

Falls etwas unverständlich oder "unschön" dargestellt ist, bitte sofort melden. Bin blutiger Anfänger.

Freue mich auf die Unterstützung

Lg Christian
Angehängte Grafiken
Dateityp: png Screenshot 1.PNG (40,8 KB, 164x aufgerufen)
Dateityp: png Screenshot 2.PNG (29,9 KB, 69x aufgerufen)

Alt 29.07.2015, 18:38   #2
felix1
/// Helfer-Team
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens Anleitung / Hilfe




und viel Spass hier.
Wie alt ist der Rechner?
__________________

__________________

Alt 29.07.2015, 19:24   #3
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens Details



Hey,

der Rechner ist jetzt ca 4 Jahre alt. Genau kann ich es nicht mehr sagen.
__________________

Alt 31.07.2015, 20:05   #4
felix1
/// Helfer-Team
 
Windows 8.1 Bluescreens - Standard

Lösung: Windows 8.1 Bluescreens



Also gehe ich davon aus, dass er ursprünglich mit W7 erworben wurde.
Damit sollten einige der mitgelieferten Treiber der auf der Board-CD/DVD nicht mehr aktuell- sein.
Besuche also die Site von Asustek und aktualisiere Deine Treiber.
__________________
LG

Der Felix

Keine Hilfe per PN und E-Mail

Alt 31.07.2015, 20:41   #5
Tendalor
 
Windows 8.1 Bluescreens - Standard

Wie Windows 8.1 Bluescreens



Damals war es noch ein selbst zusammengebauter mit Vista.

Ich bin nun auf diese Seite gegangen: https://www.asus.com/de/Motherboards/P8P67/HelpDesk_Download/

Wie es ausschaut sind aber keine neueren Treiber als 2013 vorhanden. Da ich den PC vor spätestens 1 1/2 Jahren, mit Win 8.1 aufgesetzt und alle Treiber heruntergeladen hatte wird es wohl nicht daran liegen. Oder schaue ich falsch?


Alt 31.07.2015, 22:01   #6
felix1
/// Helfer-Team
 
Windows 8.1 Bluescreens - Standard

Wo Windows 8.1 Bluescreens Lösung!



Zitat:
Zitat von Tendalor Beitrag anzeigen
Damals war es noch ein selbst zusammengebauter mit Vista.Oder schaue ich falsch?
Irgendwie stimmt hier nix, schon garnicht die Zeitschiene.
__________________
--> Windows 8.1 Bluescreens

Alt 31.07.2015, 22:21   #7
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens



Ich hab grad nochmal nachgeschaut, der Pc ist jetzt knapp 4 Jahre alt (gebaut Release von Battlefield 3).

Entschuldigung , was kann ich machen was eventuell weiterhilft?

Alt 01.08.2015, 21:05   #8
felix1
/// Helfer-Team
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens



Zitat:
Zitat von Tendalor Beitrag anzeigen
Oder schaue ich falsch?
Wahrscheinlich. Wenn ich bei Asus nachsehe, bekomme ich auch schon Treiber angeboten für Win8*-
Lade Dir hier HWINFO herunter und suche mit diesen Informationen bei Asus die entsprechenden Treiber.
__________________
LG

Der Felix

Keine Hilfe per PN und E-Mail

Alt 03.08.2015, 17:27   #9
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens



Heyho

Jupp, der Treiber hing 10 Updates zurück.

Hatte vor dem neusten Update jeden Tag Bluescreens bekommen. Bis jetzt läuft es 2 Tage ohne. Das wird es also gewesen sein

Ich bedanke mich für die Hilfe und wünsche noch viel Erfolg bei zukünftigen Fällen.

Falls das Problem wieder auftritt würde ich mich einfach wieder in diesem Thread melden?!

Grüße Christian

Alt 03.08.2015, 19:28   #10
felix1
/// Helfer-Team
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Wenn Du keine fehlerhafte Hardware hast, was durchaus auch auftreten kann und die Treiber aktuell hällst, wirst Du wohl in diesem Thread nicht mehr posten
__________________
LG

Der Felix

Keine Hilfe per PN und E-Mail

Alt 15.08.2015, 11:39   #11
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Einen wundervollen Guten Tag wünsch ich

Leider muss ich mich doch nochmal melden.
Hatte gestern erst einen eingefrorenen Bildschirm und heute dann wieder einen Bluescreen.

Alt 16.08.2015, 11:33   #12
burningice
/// Malwareteam
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Bitte lade dir die neuste Version von WhoCrashed auf deinen Computer: WhoCrashed Download
  • Installiere es
  • Starte es als Administrator
  • Klicke oben links auf den Button "Analyze"
  • Scrolle herunter, die Bereiche Crash Dump Analysis und Conclusion bitte ins Forum kopieren

Bitte poste dein Ergebnis zwischen Code-Tags
Wenn ein Log zu lange ist, teile ihn bitte auf mehrere Antworten.

Code-Tags?

Drücke einfach die # in Antwortfenster und füge den Log dazwischen ein


__________________
Mfg,
Rafael

~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~

Unterstütze uns mit einer Spende
......... Lob, Kritik oder Wünsche .........
.......... Folge uns auf Facebook ..........

Alt 16.08.2015, 14:23   #13
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Da sind sie und danke für das annehmen des Problems

Code:
ATTFilter
On Sun 16.08.2015 09:50:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081615-4531-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2F5EE9) 
Bugcheck code: 0xD1 (0xFFFFE00061DCD46C, 0x6, 0x1, 0xFFFFF801DA762EE9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12 
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation). 
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 16.08.2015 09:50:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2F5EE9) 
Bugcheck code: 0xD1 (0xFFFFE00061DCD46C, 0x6, 0x1, 0xFFFFF801DA762EE9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12 
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation). 
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 05.08.2015 20:13:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080615-6562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x50 (0xFFFFF6800F9D2400, 0x0, 0xFFFFF8039F8D23AD, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 that cannot be identified at this time. 



On Wed 05.08.2015 19:32:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080515-4484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x139 (0x3, 0xFFFFD0003CB93850, 0xFFFFD0003CB937A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sat 01.08.2015 13:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-4640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x139 (0x3, 0xFFFFF80386A90FA0, 0xFFFFF80386A90EF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 31.07.2015 19:18:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073115-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x19 (0xE, 0xFFFFE00158DBCDE0, 0x4006D7B5B0C00C9, 0x4006D7B5B0C58C9)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 31.07.2015 19:14:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073115-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41201, 0xFFFFF680019D3C68, 0xDB4000017A267847, 0xFFFFE001AD9C23E0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 31.07.2015 15:13:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073115-4609-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x26A9C9) 
Bugcheck code: 0xD1 (0xFFFFE001DE3B346C, 0x2, 0x1, 0xFFFFF8013A2EC9C9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12 
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation). 
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 24.07.2015 14:20:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072415-10875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xA (0xFFFFFFFFFFFF00FF, 0x2, 0x1, 0xFFFFF802E3F20988)
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 that cannot be identified at this time. 



On Thu 16.07.2015 16:04:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071615-18906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFC000443DA940)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 that cannot be identified at this time.
         

Alt 16.08.2015, 14:36   #14
burningice
/// Malwareteam
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Zitat:
NVIDIA Windows Kernel Mode Driver, Version 350.12
Deine NVIDIA Treiber Version ist ziemlich veraltet (okay aus April) - bitte unbedingt updaten Bei dem Setup den Haken bei "Neuinstallation" setzen

Weiters schau bitte, ob es für dein Mainboard einen neuen Chipsatztreiber gibt und installiere den

Alt 16.08.2015, 17:51   #15
Tendalor
 
Windows 8.1 Bluescreens - Standard

Windows 8.1 Bluescreens [gelöst]



Habe den Treiber erneuert.
Leider wieder mehrere Bluescreens hintereinander bekommen.
Und nur einer konnte ausgelesen werden.

Code:
ATTFilter
On Sun 16.08.2015 16:11:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081615-4453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0) 
Bugcheck code: 0x139 (0x3, 0xFFFFD00031A820E0, 0xFFFFD00031A82038, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
         

Antwort

Themen zu Windows 8.1 Bluescreens
bad_pool_caller, betriebssystem, bluescreen, bluescreen bad_pool_caller, bluescreen dispatch_level, bluescreen irql_not_less_or_equal, bluescreen kmode_exception_not_handled, bluescreen memory_management, bluescreen system_service_exception, bluescreens, information, irql_not_less_or_equal 0x0000000a, kmode_exception_not_handled 0x0000001e, ntoskrnl.exe, programme, software, standard, system32, unregelmäßige



Ähnliche Themen: Windows 8.1 Bluescreens


  1. Windows 7 Bluescreens
    Alles rund um Windows - 01.08.2015 (10)
  2. Windows 7 64 mit häufigen Bluescreens
    Alles rund um Windows - 05.04.2015 (30)
  3. Windows 7 Installation vom USB Stick verursacht verschiedene Bluescreens
    Alles rund um Windows - 11.11.2014 (19)
  4. Windows 8.1: Sporadische Bluescreens (meist ntoskrnl.exe) und häufige Abstürze
    Plagegeister aller Art und deren Bekämpfung - 03.11.2014 (7)
  5. Systemabstürze+Bluescreens bei Belastung, Windows 7, Infekt: Win32,Win64
    Log-Analyse und Auswertung - 22.09.2014 (23)
  6. sporadische Bluescreens + snap.do + keine Windows-Updates
    Log-Analyse und Auswertung - 24.02.2014 (18)
  7. Windows 8: regelmäßig bluescreens / Defender-Echtzeitschutz nicht aktivierbar
    Log-Analyse und Auswertung - 29.10.2013 (9)
  8. Massive Bluescreens durch Windows/Treiber
    Alles rund um Windows - 23.10.2013 (2)
  9. WIndows 7 stürzt mit Bluescreens ab, Malware beseitigt
    Alles rund um Windows - 24.05.2013 (11)
  10. Windows 7 Bluescreens
    Alles rund um Windows - 21.03.2013 (16)
  11. Bluescreens/Verlangsamtes Windows/MBytes bricht ab
    Plagegeister aller Art und deren Bekämpfung - 08.12.2012 (17)
  12. Windows 7 Bluescreens - Infected MBR ?
    Plagegeister aller Art und deren Bekämpfung - 07.11.2011 (18)
  13. TAN-Abfrage Trojaner und Bluescreens mit Windows 7 trotz antivir, malewarebytes und spybot
    Log-Analyse und Auswertung - 13.10.2010 (6)
  14. PC dreht am Rad. Bluescreens, Regedit defekt, Windows wie ausgehöhlt!
    Log-Analyse und Auswertung - 11.03.2010 (13)
  15. Symantec: Rootkit verursacht Windows-XP-Bluescreens
    Nachrichten - 15.02.2010 (0)
  16. Windows mit diversen Bluescreens und Abstürzen während Spielen
    Alles rund um Windows - 12.01.2010 (8)
  17. Windows spinnt rum Bluescreens on mass..
    Alles rund um Windows - 10.01.2008 (1)

Zum Thema Windows 8.1 Bluescreens - Guten Tag, ich habe seit ca. einem Monat sehr unregelmäßige Bluescreens. Anfangs dachte ich es liegt an dem sich überhitzenden Prozessor. Nachdem ich neue Wärmeleitpaste aufgetragen hatte und der Prozessor - Windows 8.1 Bluescreens...
Archiv
Du betrachtest: Windows 8.1 Bluescreens auf Trojaner-Board

Search Engine Optimization by vBSEO ©2011, Crawlability, Inc.