[SOLVED] BSOD/Not Running Well After New CPU Motherboard + RAM

A

Alex97

Member
Joined
Jan 6, 2020
Posts
16
I decided to get a new CPU/MotherBoard/Ram for Christmas and it's been a real hassle. My pc worked fully before this with no blue screens in over a year.

Specs: i7 9700k, Z390-A Pro Motherboard, 16gb Corsair Vengence LPX, EVGA 1080ti. (Old CPU i7 4790k Msi Z97 Gaming 5 mobo)

I installed the new hardware fine and it just randomly blue screens and it is giving me multiple blue screen errors, all of the errors seem to be linked with Drivers. My list of bluescreens:

-System_Thread_Exception_Not_Handled
-APC INDEX MISMATCH
-Critical Process Died
-System Service Exception
-Critical Structure Corruption


So I saw these issues and decided to use windows reset this PC function and chose to wipe all (I know I probably should've done this after I immediately installed the new hardware). I went to reinstall graphics drivers when I first booted it up (After the wipe) but It said I already had the graphics drivers installed.(so I'm wondering if I need to get a third party software to full wipe the PC or if drivers just get auto installed anyway as I wiped it to try and start fresh with the drivers)

Anyway since I wiped it I've not had as many blue screens, but I still get a lot of issues with trying to launch games even though they were fine before with my old CPU/Motherboard/RAM. This is my whocrashed log from earlier today:

"On Mon 06/01/2020 00:28:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010620-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042DA45A89, 0xFFFF9D89B57368C0, 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."

Here is a list of things I've checked/tried:

-Checking windows is up to date
-Installing GPU Drivers
-Using auto install drivers
-RAM/CPU is not Overclocked
-Installing chipset drivers directly
-Windows detects the CPU as genuine
-Doing an sfc /scannow test (It says it found corrupted files so I did the DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH) which seems to have fixed it although it gave me the same error after I wiped my pc and it repaired itself after the BSOD
-Running Malware/Anti-virus programmes
 
· OS - Windows 10, 8.1, 8, 7, Vista ?// OS - Windows 10 Pro
· · x86 (32-bit) or x64 (64-bit)?// x64 (64-bit)
· What was the originally installed OS on the system? // Windows 8.1? Either that or 8 it was a while ago
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? // No
· Age of system (hardware) // Oldest part is around 3 years old
· Age of OS installation - have you re-installed the OS? // Around 1.5 years

· CPU - New i7 9700k (Old i7 4790k)
· Video Card EVGA 1080ti
· MotherBoard - (if NOT a laptop) Z390-A Pro Motherboard
· Power Supply - brand & wattage (if laptop, skip this one) Corsair Tx-M Series 650 watt (I think, if needed I can double check but it's covered up)

· System Manufacturer N/A
· Exact model number (if laptop, check label on the bottom) N/A

· Laptop or Desktop? Desktop





I decided to get a new CPU/MotherBoard/Ram for Christmas and it's been a real hassle. My pc worked fully before this with no blue screens in over a year.


I installed the new hardware fine and it just randomly blue screens and it is giving me multiple blue screen errors, all of the errors seem to be linked with Drivers. My list of bluescreens:

-System_Thread_Exception_Not_Handled
-APC INDEX MISMATCH
-Critical Process Died
-System Service Exception
-Critical Structure Corruption


So I saw these issues and decided to use windows reset this PC function and chose to wipe all (I know I probably should've done this after I immediately installed the new hardware). I went to reinstall graphics drivers when I first booted it up (After the wipe) but It said I already had the graphics drivers installed.(so I'm wondering if I need to get a third party software to full wipe the PC or if drivers just get auto installed anyway as I wiped it to try and start fresh with the drivers)

Anyway since I wiped it I've not had as many blue screens, but I still get a lot of issues with trying to launch games even though they were fine before with my old CPU/Motherboard/RAM. This is my whocrashed log from earlier today:

"On Mon 06/01/2020 00:28:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010620-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8042DA45A89, 0xFFFF9D89B57368C0, 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."

Here is a list of things I've checked/tried:

-Checking windows is up to date
-Installing GPU Drivers
-Using auto install drivers
-RAM/CPU is not Overclocked
-Installing chipset drivers directly
-Windows detects the CPU as genuine
-Doing an sfc /scannow test (It says it found corrupted files so I did the DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH) which seems to have fixed it although it gave me the same error after I wiped my pc and it repaired itself after the BSOD
-Running Malware/Anti-virus programmes
 

Attachments

Send full memory dump (MEMORY.DMP in C:\Windows)
 
Rich (BB code): 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8042da45a89, Address of the instruction which caused the bugcheck
Arg3: ffff9d89b57368c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Rich (BB code): 
1: kd> !error 00000000c0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Rich (BB code): 
1: kd> .cxr 0xffff9d89b57368c0
rax=00000000000000e2 rbx=ffffb2073f79e050 rcx=fffff8042da00000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffdb2073c832cc0
rip=fffff8042da45a89 rsp=ffff9d89b57372b0 rbp=0000000000000078
 r8=0000000000000001  r9=0000000000000078 r10=0000000000000001
r11=ffff9d89b5737340 r12=fffdb2073c832c40 r13=0000000000000005
r14=0000000000000080 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!PspReturnQuota+0x49:
fffff804`2da45a89 488b1f          mov     rbx,qword ptr [rdi] ds:002b:fffdb207`3c832cc0=????????????????

Rich (BB code): 
1: kd> !pte fffdb2073c832cc0
                                           VA fffdb2073c832cc0
PXE at FFFFF5FAFD7EBB20    PPE at FFFFF5FAFD7640E0    PDE at FFFFF5FAEC81CF20    PTE at FFFFF5D9039E4190
Unable to get PXE FFFFF5FAFD7EBB20
WARNING: noncanonical VA, accesses will fault !

Non-canonical memory addresses will always result in a general protection fault, which in this case, has lead to the bugcheck.

If you switch to the thread's context and then dump it's call stack, you can even see a general protection fault was raised:

Rich (BB code): 
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffff9d89`b5735f88 fffff804`2dbd32e9 : 00000000`0000003b 00000000`c0000005 fffff804`2da45a89 ffff9d89`b57368c0 : nt!KeBugCheckEx
ffff9d89`b5735f90 fffff804`2dbd273c : ffff9d89`b5737078 ffff9d89`b57368c0 fffff804`2df43e14 ffff9d89`b5737600 : nt!KiBugCheckDispatch+0x69
ffff9d89`b57360d0 fffff804`2dbca30f : fffff804`2df11000 fffff804`2da00000 0005e548`00ab6000 00000000`0010001f : nt!KiSystemServiceHandler+0x7c
ffff9d89`b5736110 fffff804`2dac2fa5 : 00000000`00000070 00000000`00000000 ffff9d89`b5736680 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
ffff9d89`b5736140 fffff804`2dac753e : ffff9d89`b5737078 ffff9d89`b5736dc0 ffff9d89`b5737078 fffdb207`3c832cc0 : nt!RtlDispatchException+0x4a5
ffff9d89`b5736890 fffff804`2dbd341d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
ffff9d89`b5736f40 fffff804`2dbcf1a2 : 00000000`00000000 fffff804`2da0409d ffffb207`3c8621c8 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffff9d89`b5737120 fffff804`2da45a89 : ffffb207`3f7c9400 fffff804`2da39c1d ffffb207`3f7c9080 fffff804`2dacbb68 : nt!KiGeneralProtectionFault+0x322 (TrapFrame @ ffff9d89`b5737120)
ffff9d89`b57372b0 fffff804`2dffa389 : ffffb207`3f79e738 ffffb207`3f79e050 ffffb207`34cd00c0 ffffb207`3f79e030 : nt!PspReturnQuota+0x49
ffff9d89`b5737310 fffff804`2dffa0e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpFreeObject+0x249
ffff9d89`b5737370 fffff804`2da3a9a9 : 00000000`00000000 00000000`00000000 ffff9d89`b57374f9 ffffb207`3f79e080 : nt!ObpRemoveObjectRoutine+0x88
ffff9d89`b57373d0 fffff804`2dfec457 : 00000000`00000000 ffffb207`3f79e050 ffffb207`00000000 ffffb207`3d5cada0 : nt!ObfDereferenceObjectWithTag+0xc9
ffff9d89`b5737410 fffff804`2e0385a5 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObCloseHandleTableEntry+0x2c7
ffff9d89`b5737550 fffff804`2e038241 : 00000000`00000000 ffffb207`3f7c9080 ffffffff`ffffff01 ffffb207`3f7ad380 : nt!ExSweepHandleTable+0xd5
ffff9d89`b5737600 fffff804`2e038769 : ffffffff`ffffffff ffffb207`3f7ad080 ffff9d89`b5737650 ffffb207`00000000 : nt!ObKillProcess+0x35
ffff9d89`b5737630 fffff804`2e05e6d3 : ffffb207`3f7ad080 ffffd80d`4c3cb770 ffff9d89`b5737859 00000000`00000000 : nt!PspRundownSingleProcess+0x131
ffff9d89`b57376b0 fffff804`2e0cd143 : 00000000`40010004 fffff804`2973e101 00000082`947bf000 00000000`00000000 : nt!PspExitThread+0x60b
ffff9d89`b57377c0 fffff804`2da3e551 : ffffb207`3f7c9080 00000000`00000000 00000000`00000000 fffff804`00000000 : nt!KiSchedulerApcTerminate+0x33
ffff9d89`b5737800 fffff804`2dbc5a60 : 00000082`95050001 ffff9d89`b57378c0 00000000`00000000 fffff804`00000000 : nt!KiDeliverApc+0x481
ffff9d89`b57378c0 fffff804`2dbd2dbf : ffffb207`3f7c9080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffff9d89`b5737a00 00007ffa`d2e1c144 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f (TrapFrame @ ffff9d89`b5737a00)
00000082`9505fb88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`d2e1c144



For now, could you please ensure that the RAM sticks are matching and compatible with the motherboard? Have they been seated in the correct configuration?

I would also suggest running Driver Verifier as well - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

I would suggest removing the LGHUB program at least for troubleshooting purposes, since it was the last running process at the time of the crash, and "optimisation" programs like that can cause problems.
 
Since posting this my PC crashed again, I ran the error through whocrashed and it gave two reports (I don't know if this helps at all, just figured it would) (Also this was before I saw the last post so LGHub was still open

"Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 06/01/2020 18:25:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010620-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1 (0x7FF8C7F3C784, 0x0, 0xFFFF, 0xFFFF880D3CDAFA80)
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 06/01/2020 18:25:56 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+0x8149)
Bugcheck code: 0x1 (0x7FF8C7F3C784, 0x0, 0xFFFF, 0xFFFF880D3CDAFA80)
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. "

I linked the memory dump below.

The ram sticks (Corsair Vengence LPX DDR4 2400mhz) are matching and are compatible and are plugged into the 2nd and 4th slot like the manual suggests.

In regards to the driver verifier how long should I run it for, around 24 hours? And I assume if it doesn't pop up with anything in the allocated time there's no problems on this end?

I've also disabled LGHub.

I tried to link the Memory.DMP found in c:/ windows but it says it is too large for the server to process (931 mb) Is there a way round this?
 
Alex97 said:
The ram sticks (Corsair Vengence LPX DDR4 2400mhz) are matching and are compatible and are plugged into the 2nd and 4th slot like the manual suggests.
Click to expand...

Thanks for letting us know, there has been plenty of issues in the past due to incompatible RAM sticks.

Alex97 said:
In regards to the driver verifier how long should I run it for, around 24 hours? And I assume if it doesn't pop up with anything in the allocated time there's no problems on this end?
Click to expand...

Please run it for 48 hours, if you have another BSOD whilst Driver Verifier is running, then please stop Driver Verifier and upload the subsequent crash dumps.

Alex97 said:
I've also disabled LGHub.
Click to expand...

Thank you, I'm not sure if it is the definitely the cause of the crash, but always worth checking for the sake of troubleshooting.

Alex97 said:
I tried to link the Memory.DMP found in c:/ windows but it says it is too large for the server to process (931 mb) Is there a way round this?
Click to expand...

You'll need to zip the dump file and then upload it to a file sharing site such as OneDrive or Dropbox. Once you've uploaded it, then please post the URL of the file in your next post.

Could you also please run the BSOD collection tool again or zip up of the Minidumps and attach them to your next post?
 
Memory Dump: MEMORY.DMP

I tried uploading the Minidumps and it says that you don't have permission to open this file, it said the same for the memory dump but it let me copy and paste it to my desktop and it worked, but this isn't working for the minidumps
 
As advised by a colleague above (x BlueRobot) enable Driver Verifier. In Driver Verifier enable all standard options and 3 additional (force pending I / O request, IRP Logging and DDI Compliance checking (additional)) and of course you enable it for all drivers except Microsoft drivers
 
Alex97 said:
I tried uploading the Minidumps and it says that you don't have permission to open this file, it said the same for the memory dump but it let me copy and paste it to my desktop and it worked, but this isn't working for the minidumps
Click to expand...

Could you please provide a screenshot of the error message? Have you tried copying the Minidumps to your desktop as well?

Alex97 said:
I followed the driver verifier steps, thanks, no crashes yet
Click to expand...

Thanks, please ensure that you provide the MEMORY.DMP of the next crash as well, hopefully it will a Stop 0xC4. We'll need to check the critical region logs.
 
I did try to copy and paste the minidump like I did with the memory dump but it does not let me access it and gives me the following message: b8cdf62dd5a17b117249bca001817634.png
 
You must give appropriate permissions to the folder where the crash dump is located. I did it like this:
1. I clicked PPM on the folder and selected Properties
2. There I went to the Security tab and clicked Continue
3. In the next window I clicked on Continue
4. At the Owner field, I clicked Change and in the Enter object name field I entered Users and clicked on Check names and selected the Users group. I gave them full control and I could easily open files I couldn't access
 
This message may also appear when trying to share a file (at least I had it)
 
Yes it does show that same error when I try to copy it, I followed yours steps MrPepka and it still gives me the same issue, you said before BlueRobot that you would just want me to run the BSOD collection tool again instead of zipping the minidumps, if so there's been no errors since that and everything on there has been listed above.

I don't know if this is unusual with the verifier but audio etc is slightly delayed. Also when I try to launch a certain game it completely restarts my PC with no error message at all, could this be anything to do with it or is that normal with this software running?
 
Driver Verifier should not be turned on all the time because it may slow down your computer. As for the symptoms of restarting the computer when starting the game, it indicates some hardware problems. It is worth testing RAM memory with memtest, disks with SeaTools program, CPU with Prime95, OCCT and Intel Processor Diagnostic Tool, as well as GPU with FurMark program
Tutorials:
RAM - Test RAM with PassMark MemTest86
Disks - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
CPU - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT) How to Stress-Test CPUs and PCs (Like We Do)
GPU - FurMark Display Card Stress Test
 
So you wouldn't leave the verifier on for the entirety of the 48 hours then, do you think it would be worth for me just to do the CPU and RAM test as they're the only things I've added since I've been getting BSOD's
 
You can leave the verifier turned on even for 48 hours but I don't know what it would give if you don't have blue screens now. Yes you can test the processor and RAM memory as soon as you added these 2 elements to your computer
 
Alex97 said:
Yes it does show that same error when I try to copy it, I followed yours steps MrPepka and it still gives me the same issue, you said before BlueRobot that you would just want me to run the BSOD collection tool again instead of zipping the minidumps, if so there's been no errors since that and everything on there has been listed above.

I don't know if this is unusual with the verifier but audio etc is slightly delayed. Also when I try to launch a certain game it completely restarts my PC with no error message at all, could this be anything to do with it or is that normal with this software running?
Click to expand...

Yes this is normal behaviour, Driver Verifier runs a number of checks which can cause performance issues. Please continue to run DV for the recommended 48 hours, after that, then it may be worthwhile to run the other diagnostics tests. Although, Stop 0x1 is typically only due to drivers misbehaving.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top