Themabewertung:
  • 0 Bewertung(en) - 0 im Durchschnitt
  • 1
  • 2
  • 3
  • 4
  • 5
Bluescreens Win 7
#1
Ich hab heute irgendwie ständig Bluescreens und irgendwie jedesmal eine andere Ursache dafür. Daran beteiligt ist scheinbar immer die ntoskrnl.exe aber das ist auch schon die einzige gemeinsamkeit...

Hier mal das Log von whocrashed:
Zitat:On Tue 14.08.2012 18:00:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-18220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3ED1FE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034031FE, 0xFFFFF880033AF318, 0xFFFFF880033AEB70)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Tue 14.08.2012 18:00:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: serscan.sys (serscan+0x12D7)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800034031FE, 0xFFFFF880033AF318, 0xFFFFF880033AEB70)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\serscan.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Serieller Bildverarbeitungs-Gerätetreiber
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Tue 14.08.2012 17:50:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF680023BA338, 0x0, 0xFFFFF80003079B2B, 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 which cannot be identified at this time.


On Tue 14.08.2012 11:37:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-17394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x4E (0x99, 0x13C2A8, 0x2, 0x134967)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.


On Fri 10.08.2012 15:30:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081012-17846-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x411, 0xFFFFF680000A2248, 0xA2100001303B4886, 0xFFFFF6FC80610341)
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 which cannot be identified at this time.
Hat jemand eine ahnung woran das liegen könnte?
Antworten
#2
Was sagen deine Ereignisse aus der MMC?
Kellnerin:
Well, there's egg and bacon; egg sausage and bacon; bacon sausage and
spam; spam egg spam spam bacon and spam; spam sausage spam spam bacon
spam tomato and spamspam spam spam egg and
spam.

Mann: I don't like spam!
Antworten
#3
Ohne genauer die Logs oben durchzulesen, tippe ich auf einen Hardwaredefekt, sollten zuvor keine Gerätetreiber oder ähnliches ausgetauscht oder aktualisiert worden sein.

(CPU/Mainboard/RAM)
Gruß
GatesKiller
Antworten
#4
MMC?

Getauscht worden ist nichts, das einzige war das ich Spybot mal gegen die 2er RC1 getauscht hatte die gefiehl mir aber nicht so das ich die 1.6.irgendwas wieder installiert habe. Das trat allerdings auch davor und danach auf, daran sollte es also in meinen Augen nicht liegen...

Was mich halt wundert das da irgendwie kein "Roter Faden" zu erkennen ist...

Achja, bis jetzt kam das auch nicht wieder vor...
Antworten
#5
Windows Taste + R -> mmc ->strg +m -> Ereignisanzeige
Da auf abbrecher und warnungen, kurz vorm ungewollten herunterfahren, achten.


BlackFly schrieb:Achja, bis jetzt kam das auch nicht wieder vor...
[X] fixed! Wink
Kellnerin:
Well, there's egg and bacon; egg sausage and bacon; bacon sausage and
spam; spam egg spam spam bacon and spam; spam sausage spam spam bacon
spam tomato and spamspam spam spam egg and
spam.

Mann: I don't like spam!
Antworten
#6
Nicht ganz, es war wirklich so das beide Speichersets defekt waren...
Den ersten Satz (2x2GB) der beim Kauf drinne war hatte dann irgendwann kurz drauf ganz den Geist aufgegeben das nur noch einer der beiden Riegel erkannt wurde
Den zweiten Satz (2x4GB) habe ich dann "auf gut Glück" bei Atelco ausgetauscht und seitdem hatte ich dann keine Probleme mehr...

Also:
[ ] einfach nur Glück gehabt
[X] wirklich fixed
Antworten


Gehe zu:


Benutzer, die gerade dieses Thema anschauen: 1 Gast/Gäste