Windows 10: Brand new PC keeps crashing (ntkrlrmp.exe & nvlddkm.sys)

Not since the one this morning. But they do tend to be random. In that I can go a few days without any, and then get three or four in quick succession. Do the minidumps reveal anything else apart from the nvidia driver and network drivers?

ps., how do I sort out the Bios bug? Stick with the beta?

 

Something went wrong with my post.

I was trying to say:
The minidumps don't reveal much at all, but the nvidia driver is all I saw.
You would need a full memory dump for more information, but I can do just a little few things with a minidump, I wouldn't get much more from a memory dump.

This BIOS bug is a minor one, I wouldn't worry about it.

 

No worries mate, I appreciate the help. If DDU nvidia reinstall sorts it out, I will return and mark the thread as solved.

One last thing. Is the issues I have been having software/driver related, or could a component be failing? It is a new rig built with hi-end gear, so I'd be surprised of it was.

 

If it is a hardware issue is currently difficult to tell.
You can try

• various of drivers,
• run a stress test,
• change the BIOS settings of the GPU regarding overclocking and possibly? voltages,
• put the GPU in a different slot and
• use another GPU

before you can tell it is a hardware issue.

 

Hi Axe, I ran a few stress tests, they all came out fine.
I will report back if I get anymore bsods.

 

OK everything fine for a day then:
On Wed 02/12/2015 08:20:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120215-10906-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x8D, 0x18410, 0x450001, 0xFFFFF680CBB22C60)
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.

Same module as the others. I did a clean DDU nvidia driver install. The DISM and scf /scannow showed no violations. Is it time I start RMA'ing the card & RAM? It is a new PC barely 2 months old, and I've had freezing issues from day one, however it would be fine for a week or two, then the odd freeze no bsods. Last month the bsods typical of the ones we have been dealing have started happening more regularly. I did a clean install and upgrade from Windows 10 Home to Pro yet the bsods if anything are getting more frequent. My suspicion is that this must be failing RAM or GTX 980 card. Again just now all I was doing was watching a YouTube video, I have only frozen once while gaming. Time to start replacing parts?

 

You're using Bitdefender 2015 and 2016?
Code: Start Menu\Programs\Bitdefender 2015 Public:Start Menu\Programs\Bitdefender 2015 Public Start Menu\Programs\Bitdefender 2016 Public:Start Menu\Programs\Bitdefender 2016 Public[/quote] The 0x4E(PFN_LIST_CORRUPT) is either caused by bad drivers or memory.
Since no driver has been flagged the memory needs to be tested.
According to my research you have DDR4, DDR4 is not supported by the test I usually suggest so we are using MemTest86
MemTest86 - Offical Site of the x86 Memory Testing Tool
Unfortunately, I do not really know the requirements for MemTest86 and I also have no idea how long it might take.
I suggest to do a couple of passes, like at least 8 passes or until you find an error.

 

The 0x4E(PFN_LIST_CORRUPT) is either caused by bad drivers or memory.
Since no driver has been flagged the memory needs to be tested.
According to my research you have DDR4, DDR4 is not supported by the test I usually suggest so we are using MemTest86
MemTest86 - Offical Site of the x86 Memory Testing Tool
Unfortunately, I do not really know the requirements for MemTest86 and I also have no idea how long it might take.
I suggest to do a couple of passes, like at least 8 passes or until you find an error.[/quote] Hi, I was initially using Bitdefender 2015, then upgraded to 2016. I uninstalled both using their uninstall utility and am now with Windows Firewall & Defender.
I ran MemTest86 for 12 hours+ till it completed, it showed no errors. I have read that that test only checks for physical errors and does not pick up all RAM issues. Could Bitdefender be causing registry issues despite uninstalling it?

I spoke to the firm that built my rig. They are going to send out new RAM and a replacement GTX 980 card. I fear it might still be a driver or AV causing issues.

 

Something that isn't installed can't do anything...

 

Well in that case. I have done a clean install, DISM and SFC turns out fine. I am left with components. They are sending me out replacement RAM and graphics card. Hopefully that will sort out the problems. Appreciate your help.

 

Two more crashes today:

On Thu 03/12/2015 12:58:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120315-12328-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8013F481D6E, 0xFFFFD00023AFFE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 03/12/2015 07:47:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120315-12468-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x30, 0x2, 0x0, 0xFFFFF8009508C5FE)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

I have uploaded the latest dm_log_collector files. *prays the offending driver reveals itself*

I am running Driver Verifier and got another crash, I have uploaded the file.


Latest Crash:

On Thu 03/12/2015 13:34:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120315-11828-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltpGetNormalizedFileNameWorker+0x10E)
Bugcheck code: 0xC1 (0xFFFFCF801D398FE0, 0xFFFFCF801D398540, 0xBF0020, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
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.

 

The 0x1A and 0x4E are memory crashes, the 0xA and 0x3B are caused by memory corruption.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

OK I shall run it again. It did pass all the stages, 12 I think when I did it a few weeks ago. I shall run it again before I go to work. New RAM is also on its way... But a mild downgrade...

 

Stages?
In MemTest86+ there are 10 tests in each pass, every test tests something else.

 

All ten. It completed with zero errors when I got back from work. I ran the Windows Diagnostic Memory test today too, not extended. No errors again.