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

Hello, my brand new Skylake (Scan 3XS) PC keeps crashing. I had Windows 10 Home originally, but upgraded to 64-bit Pro version and a fresh install. I thought it was down to Bitdefender. Everything seemed fine once I uninstalled it. However the BSODs are back. A common theme is that PC seems to be running for a long time when this happens.

I would get random freezes from day 1, and suspect it might be the RAM, despite memtest86 showing no errors. Please can someone help me?

Thanks you.

:)

 

Troubleshooting Windows 8 and 10 Failure to Start

Hi, I am building a brand new PC and bought Win10 Pro USB Stick for $199. Win10 keeps crashing within less than a minute with different BSOD error message each time.

I replaced the RAM thinking of bad RAM to no avail. I also replaced the Motherboard thinking it was bad motherboard, but again to no avail. Created a brand new USB stick using Media creation tool and tried "Clean Install" with "Custom Install" option, but
Win10 still keeps crashing either on startup or within 1min once I login. On phone customer tech support (sounds outside of USA from accent) don't understand that that it's a brand new PC build with brand new Win10 install and keep asking me about the upgrade.
Can you provide me any help?? Is there an phone number I can call where I can talk to expert who can walk me step by step to troubleshoot Win10 crashes?? Here's my PC config -

Processor: Intel i7-4700K (New Retail box)

Motherboard: ASRock Z97 Extreme6 (New Retail box)

RAM: G.Skill Ripjaw X series 2x8GB 1866 DDR3 (New Retail)

OS: Windows 10 Pro (Retail USB stick)

Thanks.

 

Having an issue with the Microsoft Photo App on Windows 10 Mobile

I am having an issue where my Microsoft Photo app on my brand new AT&T Microsoft Lumia 950 keeps crashing upon opening the app

the app needs to be updated to fix this issue

any help would be much appreciated

 

I have enabled Driver Verifier. Hopefully that can throw up the culprit(s). And reset BIOS OC to defaults. Can someone please help me with this?

I just purchased some G. Skill Ram to replace the Corsair Dominator 3300. Still hoping this is a random software/driver issue.

I know you guys don't like WhoCrashed...*Wink but here are the analysis:

On Mon 30/11/2015 21:24:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-27046-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!DrvUpdateGraphicsDeviceList+0x13A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8012F651528, 0x1, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
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.
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.



On Mon 30/11/2015 18:21:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-25281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFFE001E5D818D0, 0xFFFFE001E5D81A40, 0x4170008)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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 Mon 30/11/2015 18:18:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-26531-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800EDD24275, 0xFFFFD000219EFD60, 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 Mon 30/11/2015 18:17:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-25421-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80154CF4484, 0xFFFFD0004A3E6DC0, 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 Wed 25/11/2015 12:29:36 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x394D5A)
Bugcheck code: 0xD1 (0x74, 0x2, 0x0, 0xFFFFF800DFDE4D5A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 359.00
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 359.00
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.00 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




Conclusion
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.00 , NVIDIA Corporation)

ps., the PC just crashed in Google after I posted this, rebooted. No Minidump text was generated. Think I will use DDU to uninstall Nvidia driver, see if that helps.

A common theme I have noticed is that the crashes tend to happen when the PC has been running for a while, and I am inactive. I have Hibernation switched off from the Command Prompt and Power Management settings.

Latest crash minidumps added.

 

Hello, can anyone help me with this please? I know it is a bit convoluted, sorry...

 

I would try deleting anything from nvidia and just reload the latest driver and test it. If u still have the problem remove the nvidia driver and your card. Connect your monitor to the internal graphic and try it.

 

Hello, yes I just deleted the Nvidia driver using Display Driver Uninstall. I always do a clean install of these drivers. Though I did use Windows Update when a reinstalled Windows 10 Pro initially. Are all the crash reports related to Nvidia?

 

One states that it an nvidia problem. The first just says it's a graphics problem. Not sure about the other two. That's why I said remove the card and try with just the internal. That would help you see if it was your card. In the past removing the card and having Windows redetect it fixed some issues.

 

Cheers, I shall try that. Nvidia top end cards in my experience tend to be pretty good. This one is barely a year old. It never crashes whilst playing games. The bsods tend to happen whilst on desktop, watching YouTube videos. Not the most intensive environment. I have my motherboard Bios settings on Auto for internal graphics. Maybe try and disable that?

 

I suggest to remove the drivers as follow:
Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.

I'll take a look at the files later when I have time.

 

Thank you. I did that yesterday, though not in Safe Mode, because the last time I did that I had to reinstall Windows on another PC. Appreciate the help.

It is the other bsods that worry me. I did a search and driver issues and RAM seems to be a common theme. As the PC is only two months old, replacing the RAM would be the easiest option barring any driver issues that is. The weird thing is that the crashes rarely happen when I'm playing games, rather I'd just be doing some random thing on desktop. Normally switching to my other screen to watch YouTube video or just in Chrome.

 

The files you see, ntkrnlmp.exe, win32kbase.sys are files from Windows self.
Windows files are only marked as 'the cause' when they are the last active, this makes that they, in most cases, aren't the cause because the root cause doesn't have to be the last active.

Because of that, you can assume 99% of the time a 3rd party driver is causing the issue.

The crash 0xD1 hasn't been saved, as you said.

The Nvidia Video driver has been flagged in the 0x1E(KMODE_EXCEPTION_NOT_HANDLED) crash
Code: ffffd000`23eba2c0 fffff801`78490000Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm[/quote] I noticed this kind of activity
The tcpip.sys is a network related driver, meaning the network drivers or drivers trying to connect to the internet are involved/causing issues.
I suggest to check Gigabyte (the manufacturer of the laptop according to the logs) for network driver updates.
Code: ffffd000`219ef928 fffff801`e72862e3 tcpip!IppFindPathUnderLock+0x67[/quote] Please make sure your system specs are about the computer that is having the problems.
Your specs show desktop, but the logs show a laptop.
Code: Platform Role Mobile[/quote]

 

Hi, that is weird because I have a gaming desktop. Could this be the issue? I do have the latest network driver from Gigabyte. I could revert to the default Windows driver but the Gigabyte one has dual-shot utility that is a feature I would like to keep.

 

From what computer have you ran the dm log collector?

 

This one. The only pc I have. I just checked System Info and indeed under Platform Role it says Mobile... Something I did wrong during installation of Windows Pro or a Bios setting?