Question New Build PC Bluescreens Often

Toggle sidebar Toggle sidebar
A Gamer

A Gamer

Distinguished
Mar 29, 2016
68
2
18,545
Me and my brother did build a new computer for him. I was really happy he finally got a good computer for himself. Sadly the new build is having issues and bluescreens once every 3 days. I am trying to locate the issue, but didn't have any succes soo far.

BUILD:
MSI Pro B650-P WIFI
AMD Ryzen 6 7600
XFX Speedster MERC 319 AMD Radeon RX 6800 XT CORE
G. SKILL Ripjars S5 F5-6000J3040F16GX2-RS5K
WD Black SN770 500GB (Windows 10)
WD Black SN770 2TB (Games)
Seasonic Focus GX-850

We have swapped the memory because the bluescreen was pointing at a fault in the memory. The bluescreen isn't always the same and I pulled a .dmp recently. The issue is still there. Maybe the videocard is faulty, motherboard or even the psu?

Errors in Event Viewer and Security & Maintenance:
LiveKernelEvent - 141
LiveKernelEvent - 100001
BlueScreen - a
BlueScreen - a0

MEMORY.DMP
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff806354df06e, Address of the instruction which caused the BugCheck
Arg3: ffffed01d36065e0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2296

Key : Analysis.Elapsed.mSec
Value: 2299

Key : Analysis.IO.Other.Mb
Value: 14

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 18

Key : Analysis.Init.CPU.mSec
Value: 467

Key : Analysis.Init.Elapsed.mSec
Value: 15022

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x3b

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Failure.Bucket
Value: AV_nt!ObpCaptureHandleInformation

Key : Failure.Hash
Value: {3cadef4e-74b9-cad3-834a-68a23d2aac5a}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff806354df06e

BUGCHECK_P3: ffffed01d36065e0

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

CONTEXT: ffffed01d36065e0 -- (.cxr 0xffffed01d36065e0)
rax=0000000000000000 rbx=ffffa200fd6de700 rcx=ffffd901c79ba0f8
rdx=ffffa200fd314f00 rsi=ffffa200fd6de700 rdi=00000000000001c0
rip=fffff806354df06e rsp=ffffed01d3606fe8 rbp=ffffa200fd335980
r8=0000000000000000 r9=ffffa200fd314ed0 r10=000000000007a0c0
r11=ffffed01d3607030 r12=ffffd901c7940050 r13=ffffed01d36070c8
r14=fffff806354defc0 r15=000000000017fffc
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ObpCaptureHandleInformation+0xae:
fffff806`354df06e 8a4028 mov al,byte ptr [rax+28h] ds:002b:00000000`00000028=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: steam.exe

STACK_TEXT:
ffffed01`d3606fe8 fffff806`3554ee71 : 00000000`000001c0 00000000`00000000 ffff8b08`00000000 fffff806`34e86632 : nt!ObpCaptureHandleInformation+0xae
ffffed01`d3606ff0 fffff806`354def45 : fffff806`354defc0 ffffa200`fd335998 00000000`0017fffc ffffed01`d3607130 : nt!ExpSnapShotHandleTables+0x131
ffffed01`d3607080 fffff806`3554c4f1 : ffffed01`d3607130 00000000`0007a0c0 00000000`0017fffc 00000000`00000001 : nt!ObGetHandleInformation+0x39
ffffed01`d36070c0 fffff806`352096bf : 00000000`0cb2f050 00000000`00020000 ffffd901`c7940050 ffff8b08`6b625360 : nt!ExpGetHandleInformation+0x5d
ffffed01`d3607100 fffff806`35208447 : 00000000`00000002 00000000`00018002 00000000`00000001 00000000`00180010 : nt!ExpQuerySystemInformation+0x112f
ffffed01`d3607440 fffff806`3500f8f8 : ffff8b08`61f20000 00000000`00000000 ffffed01`d3607500 ffffffff`ff676980 : nt!NtQuerySystemInformation+0x37
ffffed01`d3607480 00007ff9`da42d6a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`09c3df18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`da42d6a4


SYMBOL_NAME: nt!ObpCaptureHandleInformation+ae

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffffed01d36065e0 ; kb

BUCKET_ID_FUNC_OFFSET: ae

FAILURE_BUCKET_ID: AV_nt!ObpCaptureHandleInformation

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3cadef4e-74b9-cad3-834a-68a23d2aac5a}

Followup: MachineOwner
---------

Thanks for the help in advance! ❤️
 
Last edited:
If you're overclocking the RAM at 6,000MT/s with XMP/EXPO values, disable overclocking and see if the system is stable at stock JEDEC speeds.

You might have to run a lower overclock than 6,000MT/s or relax some of the Primary memory timings under manual control.

Is the RAM mentioned in the motherboard QVL.
 
Misgar said:
If you're overclocking the RAM at 6,000MT/s with XMP/EXPO values, disable overclocking and see if the system is stable at stock JEDEC speeds.

You might have to run a lower overclock than 6,000MT/s or relax some of the Primary memory timings under manual control.

Is the RAM mentioned in the motherboard QVL.
Click to expand...
Motherboard has DDR5 support.

4DIMMs, Dual Channel DDR5-6400+MHZ (OC)

I checked the manual and they are in correct slots.
 
Last edited:
A Gamer said:
Me and my brother did build a new computer for him. I was really happy he finally got a good computer for himself. Sadly the new build is having issues and bluescreens once every 3 days. I am trying to locate the issue, but didn't have any succes soo far.

BUILD:
MSI Pro B650-P WIFI
AMD Ryzen 6 7600
XFX Speedster MERC 319 AMD Radeon RX 6800 XT CORE
G. SKILL Ripjars S5 F5-6000J3040F16GX2-RS5K
WD Black SN770 500GB (Windows 10)
WD Black SN770 2TB (Games)
Seasonic Focus GX-850

We have swapped the memory because the bluescreen was pointing at a fault in the memory. The bluescreen isn't always the same and I pulled a .dmp recently. The issue is still there. Maybe the videocard is faulty, motherboard or even the psu?

Errors in Event Viewer and Security & Maintenance:
LiveKernelEvent - 141
LiveKernelEvent - 100001
BlueScreen - a
BlueScreen - a0

MEMORY.DMP
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff806354df06e, Address of the instruction which caused the BugCheck
Arg3: ffffed01d36065e0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2296

Key : Analysis.Elapsed.mSec
Value: 2299

Key : Analysis.IO.Other.Mb
Value: 14

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 18

Key : Analysis.Init.CPU.mSec
Value: 467

Key : Analysis.Init.Elapsed.mSec
Value: 15022

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x3b

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Failure.Bucket
Value: AV_nt!ObpCaptureHandleInformation

Key : Failure.Hash
Value: {3cadef4e-74b9-cad3-834a-68a23d2aac5a}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff806354df06e

BUGCHECK_P3: ffffed01d36065e0

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

CONTEXT: ffffed01d36065e0 -- (.cxr 0xffffed01d36065e0)
rax=0000000000000000 rbx=ffffa200fd6de700 rcx=ffffd901c79ba0f8
rdx=ffffa200fd314f00 rsi=ffffa200fd6de700 rdi=00000000000001c0
rip=fffff806354df06e rsp=ffffed01d3606fe8 rbp=ffffa200fd335980
r8=0000000000000000 r9=ffffa200fd314ed0 r10=000000000007a0c0
r11=ffffed01d3607030 r12=ffffd901c7940050 r13=ffffed01d36070c8
r14=fffff806354defc0 r15=000000000017fffc
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ObpCaptureHandleInformation+0xae:
fffff806`354df06e 8a4028 mov al,byte ptr [rax+28h] ds:002b:00000000`00000028=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: steam.exe

STACK_TEXT:
ffffed01`d3606fe8 fffff806`3554ee71 : 00000000`000001c0 00000000`00000000 ffff8b08`00000000 fffff806`34e86632 : nt!ObpCaptureHandleInformation+0xae
ffffed01`d3606ff0 fffff806`354def45 : fffff806`354defc0 ffffa200`fd335998 00000000`0017fffc ffffed01`d3607130 : nt!ExpSnapShotHandleTables+0x131
ffffed01`d3607080 fffff806`3554c4f1 : ffffed01`d3607130 00000000`0007a0c0 00000000`0017fffc 00000000`00000001 : nt!ObGetHandleInformation+0x39
ffffed01`d36070c0 fffff806`352096bf : 00000000`0cb2f050 00000000`00020000 ffffd901`c7940050 ffff8b08`6b625360 : nt!ExpGetHandleInformation+0x5d
ffffed01`d3607100 fffff806`35208447 : 00000000`00000002 00000000`00018002 00000000`00000001 00000000`00180010 : nt!ExpQuerySystemInformation+0x112f
ffffed01`d3607440 fffff806`3500f8f8 : ffff8b08`61f20000 00000000`00000000 ffffed01`d3607500 ffffffff`ff676980 : nt!NtQuerySystemInformation+0x37
ffffed01`d3607480 00007ff9`da42d6a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`09c3df18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`da42d6a4


SYMBOL_NAME: nt!ObpCaptureHandleInformation+ae

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffffed01d36065e0 ; kb

BUCKET_ID_FUNC_OFFSET: ae

FAILURE_BUCKET_ID: AV_nt!ObpCaptureHandleInformation

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3cadef4e-74b9-cad3-834a-68a23d2aac5a}

Followup: MachineOwner
---------

Thanks for the help in advance! ❤️
Click to expand...
Put a copy of memtest86 on a flash stick.
Boot the stick and let it run.......no errors allowed.
 
Obviously the motherboard has DDR5 support, otherwise you wouldn't have purchased DDR5 RAM.

Whether or not you can get your system to run at speeds up to 6,400MT/s with two DIMMs, let alone 4 DIMMs, is an entirely different matter.

4 DIMMs are harder to overclock than 2 DIMMs, as many people on this forum have discovered. If you want a fast stable system fit two DIMMs. If you want a more "interesting" experience, with a greater risk of instability, fit four DIMMs.

AMD motherboards are more fussy about DDR5 RAM selection and timings than Intel systems. Is your RAM in the motherboard QVL?

You could buy RAM with EXPO overclock timings, specifically designed to work with AMD processors. Intel XMP timings may work with AMD, or they may not.

As stated earlier, if your system is unstable with XMP enabled, the first step is to disable the memory overclock, in the hope the problem will go away.

Then you can then start to manually overclock the RAM. You might achieve 6,000MT/s with looser Primary timings to those in SPD. Good luck.
 
Misgar said:
Obviously the motherboard has DDR5 support, otherwise you wouldn't have purchased DDR5 RAM.

Whether or not you can get your system to run at speeds up to 6,400MT/s with two DIMMs, let alone 4 DIMMs, is an entirely different matter.

4 DIMMs are harder to overclock than 2 DIMMs, as many people on this forum have discovered. If you want a fast stable system fit two DIMMs. If you want a more "interesting" experience, with a greater risk of instability, fit four DIMMs.

AMD motherboards are more fussy about DDR5 RAM selection and timings than Intel systems. Is your RAM in the motherboard QVL?

You could buy RAM with EXPO overclock timings, specifically designed to work with AMD processors. Intel XMP timings may work with AMD, or they may not.

As stated earlier, if your system is unstable with XMP enabled, the first step is to disable the memory overclock, in the hope the problem will go away.

Then you can then start to manually overclock the RAM. You might achieve 6,000MT/s with looser Primary timings to those in SPD. Good luck.
Click to expand...
We're running 2 DIMMs and tested 2 different sets on his computer. Both are XMP, will do a memtest first and after run them without the XMP after.
 
Bob.B said:
Ok that says your ram is in pretty good shape.
As mentioned run your stuff with xmp off and see if it makes a diff.

Does this crash happen with the same app/game?
Type WINVER in the search box what version is shown?
Click to expand...
I will run it without XMP (tested the memory with XMP enabled), the crashes seem mostly random. The crashes are during browsing, gaming and just different things.
 
I have readed some other minidumps from the computer and:
INTERNAL_POWER_ERROR (a0)
IRQL_NOT_LESS_OR_EQUAL (a)
SYSTEM_SERVICE_EXCEPTION (3b)
seem to be recurring.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom