[SOLVED] Random BSOD On New Computer

Status
Not open for further replies.

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0
I have been getting several BSODs on my newly built PC. The error codes are IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA. Parts list here.

WhoCrashed says its a software bug but this is my 8th clean install of Windows 10. I have downgraded to Windows 1703 and it stopped the crashes for a while but they came back shortly after. I should state that it crashes at completely random times. I have ran Memtest86+ for 10 passes with no errors and I have tested both my HDD and my SSD (boot drive) and they're both clean. chkdsk /f returns no errors and sfc /scannow does nothing. I removed my 1 TB HDD while I troubleshoot this issue. Here is the WhoCrashed info:

On Tue 6/19/2018 9:44:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061918-4781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xA (0x100000003F, 0x2, 0x1, 0xFFFFF800D16E1211)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 6/19/2018 9:36:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061918-4953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xA (0xFFFFF8014DA70108, 0xE, 0x0, 0xFFFFF8014C783E0C)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 6/19/2018 8:48:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061918-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0x50 (0xFFFFC0009BCE1434, 0x2, 0xFFFFF801DD6FEACF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 6/18/2018 6:04:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xA (0x40000000000, 0xFF, 0x0, 0xFFFFF802974DC87E)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 6/18/2018 5:45:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061818-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0x50 (0xFFFFA6815E78439A, 0x0, 0xFFFFF8024B63DD9F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.


As of now, I only have Windows 10 and CSGO (to test if it crashes, as it always crashes when in game) installed on the PC. Also, all of my drivers are completely up to date. Please let me know if anything else is needed. All help is appreciated :)
 

Colif

Win 10 Master
Moderator
Do you have latest bios? Often on new PC new BIOS versions include memory comparability updates that might fix the errors.

Can you go to C:\Windows\Minidump
copy the files here to another folder
uploiad the copies to a file sharing web site and show a link here
I will ask someone to convert tham into a format I can read and see what drivers might actually be the cause

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause, it was likely asked to do something by a driver it can't and took windows down with it.

Both can be drivers or hardware. Only other hardware involved is the CPU since memory controller is on there.

Have you had same errors on all 5 installs? Where do you get the drivers from?
 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0


Here are the dump files.
BIOS is also up to date.

 

gardenman

Distinguished
Moderator
Hi, I ran the 15 dump files through the debugger and got the following information: https://pste.eu/p/aXam.html

File: 061918-5250-01.dmp (Jun 20 2018 - 01:48:33)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 03 Min(s), and 37 Sec(s)

File: 061918-5171-01.dmp (Jun 19 2018 - 23:48:03)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: nvcontainer.exe)
Uptime: 0 Day(s), 1 Hour(s), 13 Min(s), and 02 Sec(s)

File: 061918-4953-01.dmp (Jun 20 2018 - 00:36:04)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 47 Min(s), and 21 Sec(s)

File: 061918-4781-01.dmp (Jun 20 2018 - 00:44:25)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 06 Min(s), and 43 Sec(s)

File: 061818-5171-01.dmp (Jun 18 2018 - 21:04:28)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 02 Sec(s)

File: 060818-7296-01.dmp (Jun 8 2018 - 18:22:55)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 17 Hour(s), 19 Min(s), and 49 Sec(s)

File: 060818-7015-01.dmp (Jun 8 2018 - 22:42:45)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Battle.net.exe)
Uptime: 0 Day(s), 0 Hour(s), 42 Min(s), and 24 Sec(s)

File: 060818-6796-01.dmp (Jun 8 2018 - 21:44:16)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: xmr-stak-cpu.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 31 Sec(s)

File: 060818-5343-01.dmp (Jun 8 2018 - 23:47:25)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for SiLib.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 07 Sec(s)

File: 060818-5265-01.dmp (Jun 8 2018 - 23:41:49)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for SiUSBXp.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 10 Sec(s)

File: 060818-11062-01.dmp (Jun 8 2018 - 23:34:19)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 30 Min(s), and 47 Sec(s)

File: 060718-6578-01.dmp (Jun 8 2018 - 01:02:24)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 3 Hour(s), 32 Min(s), and 58 Sec(s)

File: 060718-5687-01.dmp (Jun 7 2018 - 20:41:04)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 19 Hour(s), 51 Min(s), and 39 Sec(s)

File: 060718-5562-01.dmp (Jun 7 2018 - 21:28:53)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 46 Min(s), and 53 Sec(s)

File: 060618-6203-01.dmp (Jun 7 2018 - 00:48:41)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 35 Min(s), and 11 Sec(s)
Motherboard: https://www.asrock.com/mb/AMD/970A-G3.1/
As you said, you have the latest BIOS installed.

I can't help you with this. Wait for additional replies. Good luck.
 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0


Alright. Thanks for checking the dump files.

 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0


I had it installed previously but uninstalled it while troubleshooting this issue. I'll run malwarebytes as soon as I can.

 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0


Malwarebytes reports no threats.

 

Colif

Win 10 Master
Moderator
2nd last error mentioned NVContainer.exe which is part of Nvidia drivers. Not a normal part to crash as in most cases. if Nvidia crashes its another file. Running this might fix it - http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

all your errors are all over the place, 2 are web based programs which made me think its lan drivers except yours are almost brand new. Makes me think its something else but you checked RAM already so lets check drives

try running HDTune on your boot drive (if oage file is on the hdd, test it as well). Check the health tab as it will see the SMART scores (SMART = Self Monitoring And Reporting Tool).

Only other hardware that normally has anything to do with data is the CPU itself.
 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0


I performed a clean install of the video card drivers and the blue screens still continue, although now it is only IRQL_NOT_LESS_OR_EQUAL. HDTune S.M.A.R.T. scores says both drives are healthy.

 
Apr 28, 2018
5
0
10
0
Try disabling Xbox game dvr. in 1803 they changed it to on by default. I turned this off and leave off my monitoring software & it's good. If I revert back to Nvidia 391.35 drivers everything is fine. I'm hoping the next driver update fixes this. alot of people with this driver and win 10 1803 are having issues.
 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0
I was fiddling with some BIOS settings when I realized the CPU v core default was substantially too high, at 1.35v for 3.6 GHz. I lowered it to 1.2625v and have yet to receive another blue screen.
 

juniorbaconator

Reputable
Jun 20, 2018
11
0
4,510
0
I was recently experiencing lots of BSODs on my new PC, and while I was troublshooting the endless issues it could be, I noticed the default/automatic VCore for my FX-8150 was set to 1.34v for 3.6 GHz. I'm pretty sure that's high for the stock speeds and I lowered it to 1.2625v. I'm wondering if this is a good voltage to keep it at or if I should change it at all. All of my temps are good (even better now) and I don't plan on overclocking until I get a new CPU.
 

shmoochie

Commendable
May 10, 2018
900
4
1,715
207
If you are not noticing any performance issues, then you are okay. Generally, when you mess with voltages, you want to compare benchmarks and stress tests to values taken before the change.

Try running some stress tests or gaming on it for a while to see if it is stable. You'll notice artifacts or bsod if it isn't.
 
Status
Not open for further replies.

ASK THE COMMUNITY