SBMfromLA :
TheMultiRugga :
SBMfromLA :
Not entirely sure... but it sounded like a driver you installed caused this crash. Did you go to Device Manager to see if all your drivers are correct? How much RAM do you have installed? I saw something about Page File being access incorrectly. If you have more than 6GB of RAM why not simply turn it off?
Sorry I didn't really get what you men't there. I have 12 gigs of RAM. And also how do you mean about looking at the driver thing?
This is Page File:
This is the Device Manager:
Note, the yellow icons in Device Manager tells you the driver is either corrupted or not properly installed. You need to check to see if you have that.
No paging file was ticked on what do I do now. Everything checked out fine in device manager.
And then I have got some other crashes all in one go - this was when turning PC on.
On Sun 20/12/2015 9:56:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122115-8375-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x2, 0x111DFD, 0x33FFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 Sun 20/12/2015 9:56:15 PM 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: 0x4E (0x2, 0x111DFD, 0x33FFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 Sun 20/12/2015 2:06:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122015-8000-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3F5A13)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80125375A13, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 359.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 359.06
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 359.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED
Facebook
Twitter
Instagram