Vraag & Antwoord

OS Windows

blauwe schermen....

4 antwoorden
  • Ben weer een stukje verder wat mijn blauwe schermen betreft door het programma WhoCrashed, maar als leek weet ik eigenlijk nog niet hoe nu verder, wie kan me tips geven, zal zelf nog even Googlen op onderstaande tip voor een zogenaamde memory dump : On Fri 8-2-2013 23:05:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\020913-70184-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x50 (0xFFFFF88015692938, 0x0, 0xFFFFF8000E46BBAB, 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 Fri 8-2-2013 23:05:09 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x50 (0xFFFFF88015692938, 0x0, 0xFFFFF8000E46BBAB, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 Fri 8-2-2013 22:43:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\020813-24523-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x50 (0xFFFFF8800DEF00C5, 0x0, 0xFFFFF8000E9B7BAD, 0x0) 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 Fri 8-2-2013 21:32:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\020813-126516-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x4E (0x99, 0xBB024, 0x2, 0xBBE23) 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 that cannot be identified at this time. On Fri 8-2-2013 6:53:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\020813-19656-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0xFFFFF8004D3239AC, 0x2, 0x0, 0xFFFFF8000E4E78A2) 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
  • http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx De boel maar eens gaan controleren met de opties in bovenstaande link.
  • [quote:6de686d73e="Lange Pier"]http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx De boel maar eens gaan controleren met de opties in bovenstaande link.[/quote:6de686d73e] Bedankt zal gelijk even checken...
  • [quote:e5087bb6d4="Trancetiger"][quote:e5087bb6d4="Lange Pier"]http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx De boel maar eens gaan controleren met de opties in bovenstaande link.[/quote:e5087bb6d4] Bedankt zal gelijk even checken...[/quote:e5087bb6d4] Nee helaas kwam geen stap verder...Format C gedaan en alles loopt weer als een trein....

Beantwoord deze vraag

Weet jij het antwoord op deze vraag? Registreer of meld je aan met je account

Dit is een gearchiveerde pagina. Antwoorden is niet meer mogelijk.