Question Help needed! New build crashes. Over thousands of errors in OCCT CPU test.

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
So few months ago I built a new system. Since I was a bit short on money I decided not to buy a new GPU and stick with the old one (GT 620). The built came out extremely unstable, I had a lot of different BSOD. Since every component in the system was brand new I blamed the GPU for all the crashes. I bought new a new GPU few days ago, installed it, but the system still crashes. Today I ran OCCT test on RAM and it crashed. Then I ran CPU test and within few minutes it reported for over 3k errors and then suddenly my PC BSODed. I'm looking for a help. I don't know what can be the cause for all the BSODs. I updated all drivers on my PC with Driver Easy. I update BIOS to the latest version, went to the UEFI settings enabled the XMP 2.0 profile, but the system still crashes.

I have ran out of guesses, I don't know what may cause all of the BSODs. Maybe I need to configure CPU settings in UEFI?
Most of the errors are MEMORY_MANAGMENT, PAGE_FAULT_IN_NONPAGES_AREA and IRQL_NOT_LESS_OR_EQUAL.
Here is the content of one the dump files analyzed with WinDbg:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022621-1268281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8051ba00000 PsLoadedModuleList = 0xfffff8051c62a390
Debug session time: Fri Feb 26 17:07:15.284 2021 (UTC + 4:00)
System Uptime: 0 days 0:38:29.974
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8051bdf5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe70fa81481e0=0000000000000050
10: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff8b9aedbf8050, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8051bc611d6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4061

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-3MF977B

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 18195

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 50

BUGCHECK_P1: ffff8b9aedbf8050

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8051bc611d6

BUGCHECK_P4: 2

READ_ADDRESS: fffff8051c6fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8051c60f330: Unable to get Flags value from nt!KdVersionBlock
fffff8051c60f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff8b9aedbf8050

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: firefox.exe

TRAP_FRAME: ffffe70fa8148480 -- (.trap 0xffffe70fa8148480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000062970 rbx=0000000000000000 rcx=ffff8b9aedbf8080
rdx=00000000746c6644 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8051bc611d6 rsp=ffffe70fa8148610 rbp=ffffe70fa8148709
r8=0000000000000003 r9=00000000ffffffff r10=fffff8051bc48710
r11=ffffe70fa8148768 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObfDereferenceObjectWithTag+0x26:
fffff8051bc611d6 f0480fc15ed0 lock xadd qword ptr [rsi-30h],rbx ds:ffffffffffffffd0=????????????????
Resetting default scope

STACK_TEXT:
ffffe70fa81481d8 fffff8051be1ebbb : 0000000000000050 ffff8b9aedbf8050 0000000000000002 ffffe70fa8148480 : nt!KeBugCheckEx
ffffe70fa81481e0 fffff8051bc0c960 : ffffb600e8800180 0000000000000002 ffffe70fa8148500 0000000000000000 : nt!MiSystemFault+0x1f43ab
ffffe70fa81482e0 fffff8051be03c5e : 0000000000000000 0000000000000000 ffffb600e88af180 0000000000000cbe : nt!MmAccessFault+0x400
ffffe70fa8148480 fffff8051bc611d6 : 0000000000000001 000000005246704e ffffe70fa81487a0 0000000000000000 : nt!KiPageFault+0x35e
ffffe70fa8148610 fffff8051bc6119e : ffff8b8af2204850 0000000000000000 000000005246704e 0000000000000002 : nt!ObfDereferenceObjectWithTag+0x26
ffffe70fa8148650 fffff8051bc48e52 : ffff8b8ae59d9760 0000000000000000 0000000000000040 fffff8052c58dc9a : nt!HalPutDmaAdapter+0xe
ffffe70fa8148680 fffff8051bc48727 : 0000000000000001 0000000000000002 ffff8b8af1339b50 ffff8b8af006c388 : nt!IopfCompleteRequest+0x712
ffffe70fa8148770 fffff8052c58d834 : fffff80500000000 00000172110cfb40 ffff8b8af006c270 ffff8b8aeedac080 : nt!IofCompleteRequest+0x17
ffffe70fa81487a0 fffff8051bc52f55 : ffff8b8ae59d9760 ffff8b8ae59d9760 0000000000000001 ffff8b8af006c270 : Npfs+0xd834
ffffe70fa8148810 fffff8051afe4906 : 0000000000000000 0000000000000000 0000000000000000 fffff8051afe4906 : nt!IofCallDriver+0x55
ffffe70fa8148850 fffff8051bc52f55 : ffff8b8af006c270 0000000000000001 ffff8b8af1339b50 fffff80500000000 : FLTMGR!FltpDispatch+0xd6
ffffe70fa81488b0 fffff8051bffd878 : ffff8b8af006c270 0000000000000000 ffff8b8af006c270 0000000000000000 : nt!IofCallDriver+0x55
ffffe70fa81488f0 fffff8051bfe454f : ffffd68900000000 ffffe70fa8148b80 0000000c29bff630 ffffe70fa8148b80 : nt!IopSynchronousServiceTail+0x1a8
ffffe70fa8148990 fffff8051be074b8 : ffff8b8aeedac080 0000000000000000 0000000000000000 0000017208c3c798 : nt!NtWriteFile+0x66f
ffffe70fa8148a90 00007fff4638c724 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000000c29bff5b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff`4638c724


SYMBOL_NAME: Npfs+d834

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: d834

FAILURE_BUCKET_ID: AV_INVALID_Npfs!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5997191b-9534-6e03-7650-35d9877524bb}

Followup: MachineOwner
---------
Please, help me with the issue.
Here's is the link to the first post I opened because of the BSODs. The PC stopped crashing for few days, so I assumed that it's fixed, but then it started crashing again. The memtest didn't find any errors.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Have you tried disabling XMP?
It was disabled from the beginning, the RAM timing didn't match with the timings provided on the official webpage of the ram sticks, so I enabled the XMP profile. I'm extremely confused. I swear I ran the OCCT test few hours and and returned over 3k errors within few minutes and then crashed. Now It's been running for 30mins and no errors found.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Your motherboard requires a bios update to level P2.0 to support your processor.
https://www.asrock.com/mb/AMD/B450M Pro4-F/#CPU
The motherboard had BIOS version P2.0 from the beginning, but the system was crashing, that's why I updated it.
Ok. I just checked the older post and BIOS version was P1.60. For some reason I thought it was P2.0. Then I'll probably downgrade the BIOS version to P2.0. Sorry for the confusion.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
The OCCT CPU stress test has finished running and it found 190 errors.
Now i'm going to download the bios P2.0 version and downgrade it. Hope it helps.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I downgraded the bios to the version p2.0, booted the pc and it froze. I restarted it again, it booted up and now I'm starting the OCCT test. I'll post here any update.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Don't. Install drivers manually either from the manufacturers' websites.

Have you reinstalled windows when building the new system or simply reused a drive that had it installed already?
I reinstalled Windows several times. I also installed Xubuntu and it also has been reporting some system errors.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
After downgrading the BIOS version to the version P2.0, I ran the OCCT CPU stress for an hour and it didn't found any errors.

Thanks everyone for your input. Thank you @geofelt . I really hope it was the problem with the BIOS version, as you said, and downgrading it has fixed the issue. I'll run the system for a weak, see if it crashes again and post an update.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I find people on different forums and Amazon listing are complaining that their cmk16gx4m2a2400c16 aren't stable, and results with random BSODs, just like in my case. The ram has Hynix's chip which apparently doesn't get along with AMDs products. I suspect it's the RAM's issue. Unfortunately for me I don't have another RAM stick just to determine whether or not my suspicion is correct.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Run memtest86
It boots from a usb stick and does not use windows.
You can download the free edition here:
If you can run a full pass with NO errors, your ram should be ok.

Running several more passes will sometimes uncover an issue, but it takes more time.
Probably not worth it unless you really suspect a ram issue.
I remember running the memtest for overnight and it didn't find any errors. I just don't know what else can cause all the BSOD's I had 2 more BSODs after I downgraded the BIOS version. Event though the memtest didn't find any errors the OCCT CPU and RAM stress tests do found errors (even though not always, sometimes it does find errors, sometimes it doesn't), and sometimes results in system crash. I'll probably run another memtest later and see if it finds something. It didn't find anything when I ran it previously.
I disabled the Spread Spectrum option in BIOS. I'm not sure if it help, but I literally have no clue why the system crashes.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0

I ran the memtest with force multithreading (F2) enabled. I guess it means that the RAM sticks are either incompatible with the motherboard or defective, right?
 

Vic 40

Titan
Ambassador
Tested each stick on it's own? Might wel be worth it to rma/return the set and get a better one, but has little to do with the chips used, my G.Skill set uses Hynix as well and works fine. Likeley more to do with being these series from Corsair.

One thing you could still do is swap the sticks from slots as well, use slots two and four from the cpu out, also set timings and speed manually.

For best bios would i first update chipset drivers to the latest,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops
after that update the bios to the latest.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Tested each stick on it's own? Might wel be worth it to rma/return the set and get a better one, but has little to do with the chips used, my G.Skill set uses Hynix as well and works fine. Likeley more to do with being these series from Corsair.

One thing you could still do is swap the sticks from slots as well, use slots two and four from the cpu out, also set timings and speed manually.

For best bios would i first update chipset drivers to the latest,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops
after that update the bios to the latest.
I don't think I might be able to return those sticks. I bought them back in 2020 on ebay. They were brand new. The CPU fan blocked access to the A1 slot, so I installed those sticks in A2 and B2 slots. I tested them both together.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Try and remove all old gpu drivers (AMD and /or Nvidia) with DDU and reinstall the latest from the maker you have now. (which is?)
I booted in safe mode, uninstalled the old driver (GT 620) with DDU then the PC restarted into normal mode and I installed the latest driver for my new graphic card (Radeon RX 560). The driver crashes once in a while with the following message

And my PC just crashed while I was typing. The level of frustration I have with the new build is unspeakable.
Can video driver crashes be related to faulty RAM sticks? RAM voltage is set to 1.2v, what happens if I increase it to say 1.3v? May I damage the motherboard or CPU with higher voltage? I'm not that worried about damaging those RAM sticks, since don't work .properly anyway.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
You can set the voltage for the ram to 1.35V and be within the safe parameters. So you can try it and see if it will give more stability.

Might be good to get another kit to test with.
I set voltage to 1.3v and it made the system even more unstable.
I tested each stick at a time and both of them failed the memtest. Does it mean that I have two faulty RAM sticks or it can be something else?
 
Last edited:

ASK THE COMMUNITY