IRQL_NOT_LESS_OR_EQUAL Bluescreen (new motherboard)

[ranged66]

Greetings!

My old motherboard broke recently so I replaced it, but now I've been getting bluescreens whenever I play games or run other resource intensive processes. Normally browsing, youtube, skype et cetera all works fine, but as soon as I play a game it gives me a bluescreen either minutes in or simply at the start. I'm hoping it's not a hardware issue and just drivers, but I've been trying for hours now (changing BIOS settings mostly) and it's still not working. I've run sfc /scannow in CMD but it came up with nothing.

Specs:
Motherboard: ASRock Fatal1ty 970 Performance
CPU: AMD FX-8350
GPU: MSI GTX-1060 6GB
RAM: 12GB DDR3
PSU: Be quiet! PURE POWER 10 600W
Storage: 200GB SSD + 500GB HDD

WhoCrashed logs:

On Fri 6-10-2017 22:00:18 your computer crashed
crash dump file: C:\Windows\Minidump\100617-5109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580) 
Bugcheck code: 0xA (0xFFFFF800CF738B0E, 0x2, 0x0, 0xFFFFF8014B2C6A25)
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. 



On Fri 6-10-2017 22:00:18 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: 0xA (0xFFFFF800CF738B0E, 0x2, 0x0, 0xFFFFF8014B2C6A25)
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. 



On Fri 6-10-2017 21:17:27 your computer crashed
crash dump file: C:\Windows\Minidump\100617-6015-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x7160) 
Bugcheck code: 0xA (0xFFFF8B8080621F00, 0xFF, 0x63, 0xFFFFF80232B102E1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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 Fri 6-10-2017 21:09:56 your computer crashed
crash dump file: C:\Windows\Minidump\100617-5375-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Fri 6-10-2017 20:59:52 your computer crashed
crash dump file: C:\Windows\Minidump\100617-5218-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x32E01) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFDD8D5D3D2E01, 0xFFFFBA803B71C040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Base Win32k Kernel-stuurprogramma
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 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 amdppm.sys crash has been coming up most frequently, but not the last few times.

Google drive link to dumps:
(zipped) https://drive.google.com/file/d/0B0WViAU2P9JPYUx2dDdhbm9NZms/view?usp=sharing

Help would be really appreciated!

 

[weberdarren97]

Is the new motherboard the same model as the old one?

 

[ranged66]

It is not. Previous motherboard was a MSI 760GA-P43.

 

[weberdarren97]

It is not. Previous motherboard was a MSI 760GA-P43.

That's why it's acting up.

The motherboard is the core of your hardware. If that is changed, Windows gets super confused.

The way to remedy this is to back up everything you want to keep, install a fresh copy of Windows from install media created on a different computer, and then install a new copy of Windows.

The reason I say to create install media on a different computer is because this copy of Windows is unstable. I wouldn't trust it to create a stable copy of Windows.

To create install media, you'll need a flash drive of at least 8GB which you don't mind being wiped, and you can download the Media Creation Tool by clicking the blue Download Tool Now button in this link: https://www.microsoft.com/en-us/software-download/windows10

 

[weberdarren97]

Don't use the disc that came with your motherboard to install drivers. They're outdated.

Use this link to get drivers for your board: http://www.asrock.com/mb/AMD/Fatal1ty%20970%20Performance/#osW1064

Use this link to get drivers for your graphics card: https://www.geforce.com/drivers

 

[ranged66]

Reinstalling Windows will be hours and hours of work, I assume all programs currently installed will stop working after all?

When I got this motherboard there was no disk to install drivers with. Could this perhaps be the problem?

 

[weberdarren97]

Reinstalling Windows will be hours and hours of work, I assume all programs currently installed will stop working after all?

When I got this motherboard there was no disk to install drivers with. Could this perhaps be the problem?

That is not the problem. It's good that there's no disc, because it would be outdated.

When Windows installs, it sets itself up based on the current hardware. A motherboard is a big part of that. Changing the board changes the way Windows needs to be set up. Unfortunately, the only way to change that, other than chasing errors for days on end, is to fresh install Windows.

There are users on here that may be able to guide you through changing your motherboard drivers, but I cannot guarantee that that will resolve your issue.

 

[ranged66]

Alright then. What would be the best way to go about reinstalling windows? Do I need to clear every installed program and every file first? How would I do that so I don't end up with two harddrives full of rubbish and a fresh windows installation?

 

[ranged66]

Or will my old programs and files work under a fresh windows install? How would I do this?

 

[ranged66]

Reinstalling windows has not fixed the problem. I used a windows 10 USB created on a different computer but I did use the 'keep existing programs and files' option on the Windows install.

It still works fine for doing anything else, but after playing a game, any game for more than a few minutes it bluescreens again.

On Sat 7-10-2017 15:11:08 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-5500-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x7063) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8054F6B7063, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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 Sat 7-10-2017 15:11:08 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x7063) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8054F6B7063, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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.

https://drive.google.com/file/d/0B0WViAU2P9JPaFNtQ29HdE9adDQ/view?usp=sharing

Could it perhaps be a faulty board? Or do I have to completely wipe everything on my harddrives instead of keeping them during the install?

 

[ranged66]

It's fixed now.

With help from a friend I re-ran sfc /scannow which found nothing. Then chkdsk /f in CMD, rebooted, re-installed every driver and installed the complete package from http://www.asrock.com/mb/AMD/Fatal1ty%20970%20Performance/#osW1064 , rebooted again and now it is no longer bluescreening.

 

[weberdarren97]

It's fixed now.

With help from a friend I re-ran sfc /scannow which found nothing. Then chkdsk /f in CMD, rebooted, re-installed every driver and installed the complete package from http://www.asrock.com/mb/AMD/Fatal1ty%20970%20Performance/#osW1064 , rebooted again and now it is no longer bluescreening.

You've eliminated the symptoms, but I'm not entirely sure that your issue is completely solved. If this works out for you in the long run, then congrats, you won the lucky lottery.

If you start getting errors again, I did say that a fresh install is the safest bet to get it stable.