Daily Random BSOD's

theTBG

New member
Joined
Nov 15, 2021
Posts
3
Hello!
My custom build is BSOD'ing randomly. I haven't been trigger the BSOD manually. It happens when gaming, or web browsing, or any normal PC usage.
I'm leaning towards PSU or Motherboard. I have run Memtest, Window Memory Diagnostics, Furmark, WD Data Lifeguard HD Test, Intel Processor Test, all have passed.
Thanks in Advance!
-Toby

Screenshot of Reliability Monitor and Problem Reports and msinfo32:
A brief description of your problem (but you can also include the steps you tried)
BSOD random couple times a day

System Manufacturer?
Custom Build

Laptop or Desktop?
Desktop

OS ? (Windows 10, 8.1, 8, 7, Vista)
10 21H1

x86 (32bit) or x64 (64bit)?
x64

(Only for Vista, Windows 7) Service pack?
21H1

What was original installed OS on system?
10

Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Age of system? (hardware)
Retail

Age of OS installation?
August/September 2021

Have you re-installed the OS?
Yes - since the started BSOD's

CPU
Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz, 3696 Mhz, 10 Core(s), 20 Logical Processor(s)


RAM (brand, EXACT model, what slots are you using?)
4x - G.Skill F4-3600C14-8GTZNB

Video Card
NVIDIA GeForce RTX 3080

MotherBoard - (if NOT a laptop)
MEG Z490 UNIFY (MS-7C71) Motherboard

Power Supply - brand & wattage (if laptop, skip this one)
Corsair RM1000I

Is driver verifier enabled or disabled?
Enabled

What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
Windows Defender

Are you using proxy, vpn, ipfilters or similar software?
No

Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
No

Are you currently under/overclocking? Are there overclocking software installed on your system?
No
 
Hello!
My custom build is BSOD'ing randomly. I haven't been able to trigger the BSOD manually. It happens when gaming, or web browsing, or any normal PC usage, multiple times a week/day.
I'm leaning towards PSU or Motherboard. I have run Memtest, Window Memory Diagnostics, Furmark, WD Data Lifeguard HD Test, Intel Processor Test, all have passed.
Thanks in Advance!
-Toby

Screenshot of Reliability Monitor and Problem Reports and msinfo32:
A brief description of your problem (but you can also include the steps you tried)
BSOD random couple times a day

System Manufacturer?
Custom Build

Laptop or Desktop?
Desktop

OS ? (Windows 10, 8.1, 8, 7, Vista)
10 21H1

x86 (32bit) or x64 (64bit)?
x64

(Only for Vista, Windows 7) Service pack?
21H1

What was original installed OS on system?
10

Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Age of system? (hardware)
Retail

Age of OS installation?
August/September 2021

Have you re-installed the OS?
Yes - since the started BSOD's

CPU
Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz, 3696 Mhz, 10 Core(s), 20 Logical Processor(s)


RAM (brand, EXACT model, what slots are you using?)
4x - G.Skill F4-3600C14-8GTZNB

Video Card
NVIDIA GeForce RTX 3080

MotherBoard - (if NOT a laptop)
MEG Z490 UNIFY (MS-7C71) Motherboard

Power Supply - brand & wattage (if laptop, skip this one)
Corsair RM1000I

Is driver verifier enabled or disabled?
Enabled

What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
Windows Defender

Are you using proxy, vpn, ipfilters or similar software?
No

Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
No

Are you currently under/overclocking? Are there overclocking software installed on your system?
No
 

Attachments

Last edited:
Hello Toby :-)

I've had a look at your crash dumps - quite a few of them are hardware related errors.

Code:
Debug session time: Sat Nov 13 18:23:55.038 2021 (UTC + 0:00)
Loading Dump File [C:\Users\philc\SysnativeBSODApps\111321-7953-01.dmp]
System Uptime: 0 days 0:56:31.678
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments:
Arg1: 0000000000000051, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801720934bb, address which referenced memory
PROCESS_NAME:  System
Probably caused by: ntkrnlmp.exe ( nt!EtwWriteEx+ab )
FAILURE_BUCKET_ID:  AV_nt!EtwWriteEx
MaxSpeed:     3700
CurrentSpeed: 3696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Nov 11 18:40:52.066 2021 (UTC + 0:00)
Loading Dump File [C:\Users\philc\SysnativeBSODApps\111121-6984-01.dmp]
System Uptime: 0 days 4:10:43.707
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffdd882f3c8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
PROCESS_NAME:  System
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed:     3700
CurrentSpeed: 3696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Nov 10 04:22:20.794 2021 (UTC + 0:00)
Loading Dump File [C:\Users\philc\SysnativeBSODApps\110921-8421-01.dmp]
System Uptime: 0 days 14:29:35.435
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8050be97b93, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
PROCESS_NAME:  System
Probably caused by: kbdhid.sys ( kbdhid!KbdHid_ReadComplete+16a )
FAILURE_BUCKET_ID:  0x1E_c0000096_STACKPTR_ERROR_kbdhid!KbdHid_ReadComplete
MaxSpeed:     3700
CurrentSpeed: 3696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov  9 03:25:38.960 2021 (UTC + 0:00)
Loading Dump File [C:\Users\philc\SysnativeBSODApps\110821-8187-01.dmp]
System Uptime: 0 days 13:01:47.243
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9105aa8b7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
PROCESS_NAME:  System
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed:     3700
CurrentSpeed: 3696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Nov  4 15:44:50.153 2021 (UTC + 0:00)
Loading Dump File [C:\Users\philc\SysnativeBSODApps\110421-7656-01.dmp]
Built by: 19041.1.amd64fre.vb_release.191206-1406
System Uptime: 0 days 0:15:57.793
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff97811afe4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
*** WARNING: Unable to verify timestamp for win32k.sys
PROCESS_NAME:  System
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed:     3700
CurrentSpeed: 3696
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

There are also a number of entries in the logs which indicate that the Operating System is concerned about memory failure.

Code:
Event[7]:
  Log Name: System
  Source: Microsoft-Windows-MemoryDiagnostics-Schedule
  Date: 2021-11-15T14:41:44.6640000Z
  Event ID: 1002
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-215025436-620530648-2466873364-1001
  User Name: RAR-GAMING\Bryan
  Computer: RAR-Gaming
  Description:
The Windows Memory Diagnostic scheduled the testing of the computer's memory to run the next time the computer starts

Taking all this into consideration I would start by looking into the way you have set up your RAM. You have set the RAM clock sped to 3600MHz. This is overclocked for the system and can lead to BSODs. Before doing too much more diagnostics please revert the settings to the recommended memory speed for the CPU you are using.

1637050369575.png

Test your system at the RAM clock speed of 2933MHz and report back on whether you are still getting BSODs. If you are, we can do further tests.
 

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

Back
Top