Hoi allemaal
de laatste tijd heb ik weer erg vaak een bsod, ik had dit probleem bijna een half jaar geleden ook al. het zijn random bsod's dus de oorzaak weet ik niet.
met WhoCrashed krijg ik de volgende resultaten:
wie o wie kan mij hiervan verlossen
de laatste tijd heb ik weer erg vaak een bsod, ik had dit probleem bijna een half jaar geleden ook al. het zijn random bsod's dus de oorzaak weet ik niet.
met WhoCrashed krijg ik de volgende resultaten:
Code:
On Fri 23-3-2012 13:11:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-34304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x4E (0x99, 0xB5D40, 0x2, 0xB573F)
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 23-3-2012 13:11:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x16E0)
Bugcheck code: 0x4E (0x99, 0xB5D40, 0x2, 0xB573F)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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.
Laatst bewerkt door een moderator: