[SOLVED] Constant BSOD on new custom PC

Toggle sidebar Toggle sidebar
M

marauder144

Honorable
Nov 12, 2015
32
1
10,565
I just built a new PC with the following specs:

Ryzen 3700x
MSI MPG X570 GAMING PRO CARBON WIFI ATX AM4 Motherboard
GeIL EVO POTENZA 16 GB (2 x 8 GB) (from my old system)
Western Digital Blue 4 TB 3.5" 5400RPM Internal Hard Drive
ADATA Ultimate SU800 256 GB 2.5" Solid State Drive (from my old system)
EVGA GeForce GTX 1070 8 GB SC Gaming ACX 3.0 Video Card (from my old system)
EVGA 850 W 80+ Gold Certified Semi-modular ATX Power Supply

I cleared Windows 10 off of the SSD and installed a new copy. I am getting constant BSODs during normal web browsing. I used MSI LiveUpdate to pull the most recent drivers for my motherboard. I tried running OCCT and I get 16 errors within seconds. My suspicion is the RAM is bad but I checked and it is compatible with Ryzen so I would like someone to read the WhoCrashed reports and tell me what they think.

Thanks.

On Sun 10/6/2019 5:33:39 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100619-14390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1 (0x7FFCED73CEA4, 0x0, 0x1, 0xFFFF9F8533815B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Sun 10/6/2019 5:33:39 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8189)
Bugcheck code: 0x1 (0x7FFCED73CEA4, 0x0, 0x1, 0xFFFF9F8533815B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 Sun 10/6/2019 5:31:43 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100619-15437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80708A6B495, 0xFFFFDD800CF16FB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Sun 10/6/2019 5:28:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100619-14312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x3D (0xFFFFDB8043560D48, 0xFFFFDB8043560590, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 10/6/2019 1:48:17 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100619-15484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0xD1 (0xFFFFF80100000000, 0xFF, 0x0, 0xFFFFF80100000000)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 10/6/2019 1:40:19 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100619-15187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1 (0x7FF90AF7C2B4, 0x0, 0x1, 0xFFFFA48B83A51B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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.
 
Solution
M
So I did resolve my issue. I t turns out when I installed Windows 10, I did not format my old boot drive and there must have been leftover Windows pieces on the drive that was throwing off the new install. I formatted the SSD to remove all traces of Windows and reinstalled it.

However, I am having a new issue. I will post in the CPU section soon but when I run OCCT I get hundreds of errors within seconds.
Sort by date Sort by votes
SkyNetRising said:
Try increasing DRAM voltage to 1.35V.
Can you show screenshots from CPU-Z memory and spd sections?
Click to expand...
https://s1006.photobucket.com/user/btysa00/media/CPU-Z SPD 1.png.html?sort=3&o=0
https://s1006.photobucket.com/user/btysa00/media/CPU-Z SPD 1.png.html?sort=3&o=0
https://s1006.photobucket.com/user/btysa00/media/CPU-Z SPD 1.png.html?sort=3&o=0

Default RAM voltage is 1.20. I increased to 1.30 and the BSODs were way more frequent. I lowered the voltage to 1.15 and still got BSODs. Voltage is back to 1.20 right now.
 
Upvote 0 Downvote
Here are more crash dumps from today.

On Mon 10/7/2019 6:48:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100719-11625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1 (0x7FFEFB294904, 0x0, 0x1, 0xFFFFCC89EB125B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 10/7/2019 6:48:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8189)
Bugcheck code: 0x1 (0x7FFEFB294904, 0x0, 0x1, 0xFFFFCC89EB125B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 10/7/2019 6:46:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100719-11500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x3D (0xFFFFFA0C73E8B898, 0xFFFFC80192CEC930, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 10/7/2019 6:43:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100719-11390-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0xA (0x5F4, 0xD, 0x0, 0xFFFFF80357DC2B11)
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 10/7/2019 6:20:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100719-11390-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8055703DCC9, 0xFFFFC780E3346930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 10/7/2019 5:53:02 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100719-12359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80656A7BA3D)
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.
 
Upvote 0 Downvote
I noticed the RAM frequency yesterday after I took those screenshots and changed it to 2133 but it didn't affect anything.

Here is another task manager screenshot showing massive CPU usage by the task manager itself. https://s1006.photobucket.com/user/btysa00/media/taskmanager1_1.png.html?sort=3&o=0

On startup, when I get to the desktop, everything is normal. CPU usage is very low and nothing is wrong. As soon as I open any program, it all freaks out. It doesn't matter what program, CPU usage spikes to 100%. This is on a fresh reset of Windows 10 with the only third party software I installed being Firefox.
 
Upvote 0 Downvote
marauder144 said:
I also just noticed I am getting 100% CPU usage all the time. This has got to be the issue, when I try to do anything I BSOD because my CPU has no capacity left. How do I fix this?

https://s1006.photobucket.com/user/btysa00/media/Desktop2_1.png.html?filters=Array&sort=1&o=0
https://s1006.photobucket.com/user/btysa00/media/Desktop_1.png.html?filters=Array&sort=1&o=1
Click to expand...

Are we sure all mainboard drivers are installed correctly? (Hard to fathom an 8 core CPU being 100% busy all the time if so) Are we sure this was a full fresh install?

Within System Information is your CPU and mainboard identified correctly?

What RAM speed is currently enabled? (Try lower speed to test for stability, or, better yet, borrow two known good/name brand sticks from someone and try another pair...

As you already have memtest issues, we need to get that issue sorted before worrying excessively about others.
 
Upvote 0 Downvote
https://s1006.photobucket.com/user/btysa00/media/system%20info_2.png.html?sort=3&o=0

Mainboard drivers are not currently installed on my current setup after my fresh Windows 10 reset. Before I did the reset, I used MSI LiveUpdate to pull the current drivers but there is no change in performance.

The SSD I installed Windows 10 on was my boot drive on my old PC. I did not remove Windows 10 from it before installing the fresh copy I purchased. I got a message during installation that it would move the old Windows files to a new folder called Windows.old. I deleted this folder after I got the desktop the first time.

System information is linked above. The CPU and motherboard are correctly identified. You may notice there are only 8gb of RAM, I took one stick out and put the other in the DIMMA2 slot. I tested both sticks like this and still ahd 100% CPU. I do not have access to other clean RAM right now. The RAM is currently at 2133 mhz.
 
Upvote 0 Downvote
So I did resolve my issue. I t turns out when I installed Windows 10, I did not format my old boot drive and there must have been leftover Windows pieces on the drive that was throwing off the new install. I formatted the SSD to remove all traces of Windows and reinstalled it.

However, I am having a new issue. I will post in the CPU section soon but when I run OCCT I get hundreds of errors within seconds.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom