Plagued by BSODs - sometimes stuck on BSOD at 0% or random restarts

Hi all,

So maybe last year December or November, I had a PC custom built for me so I could pursue music production and game a little as well. It's nothing extreme or high-end, pretty middle of the road and decent enough for my needs. Here's my problem: ever since I've gotten that PC, I've been plagued with BSODs. Three main ones have been reoccuring -

• WHEA_UNCORRECTABLE_ERROR
• UNEXPECTED_KERNEL_MODE_TRAP
• IRQL_NOT_LESS_OR_EQUAL

But there are also others such as

• KMODE_EXCEPTION_NOT_HANDLED
• DPC_WATCHDOG_VIOLATION

After one or two months of this I sent my computer in to see what the trouble was, and it so happened that Windows was massively corrupted. So after a clean reinstall, I was given back the computer and told that everything was now fine. It wasn't. I'm still hounded relentlessly by the BSODs and I'm at the end of my rope. In addition to this, sometimes the computer will restart with no warning and no dump file, or go to the BSOD and stay at 0% for hours (leaving me to manually reboot the PC). About 15 minutes before posting this thread, I got another WHEA_UNCORRECTABLE_ERROR again.

Here are my specs. I'm also including a link to a filesharing website where I've uploaded a zip file of the 2 most recent minidumps I was able to save and a text file that I recorded many of my crashes in. Hope that helps. I should also mention - the main drivers I'm getting errors from are:

• hal.dll
• ntoskrn

l



- SPECS -

• OS Name: Microsoft Windows 10 Home
• Version: 10.0.18362 Build 18362
• OS Manufacturer: Microsoft Corporation
• System Name: DESKTOP-FDI9OJ7
• System Manufacturer: Gigabyte Technology Co., Ltd.
• System Model: H310M H
• System Type: x64-based PC
• System SKU: Default string
• Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)
• BIOS Version/Date: American Megatrends Inc. F12, 14-Mar-19
• SMBIOS Version: 2.8
• Embedded Controller Version: 255.255
• BIOS Mode: Legacy
• BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
• BaseBoard Product H310M H
• BaseBoard Version x.x
• Disk drives: WDC WD10EZEX-22MFCA0 + WDC WDS120G2G0A-00JH30
• Display: NVIDIA GeForce GTX 1050-Ti

- LINK -

WeTransfer

As an example, here are three analysis messages I received from WhoCrashed:

***

On Sun 16-Jun-19 7:47:28 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\061619-8218-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)

Bugcheck code: 0x7F (0x8, 0xFFFF8A80AB092150, 0xFFFFAB0AB3649000, 0xFFFFF8023A3D9800)

Error: UNEXPECTED_KERNEL_MODE_TRAP
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 indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 16-Jun-19 8:23:28 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\061619-7968-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)

Bugcheck code: 0xA (0xFFFFDD8095E889F0, 0xFF, 0xAF, 0xFFFFF8043026723C)
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 Sun 16-Jun-19 9:52:47 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\061619-8109-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)

Bugcheck code: 0x7F (0x8, 0xFFFFC5816DA0B150, 0xFFFF82853B049020, 0xFFFFF804477DA800)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.

Can't seem to edit my original post, so here is the file I got from DM Log Collector.

The V2 Log Collector doesn't seem to want to run on my PC, and no zip file appears on my desktop after the DM Log Collector finishes its operations

No, just a .vbs file - the command prompt window tells me the process is complete and a zipped file is available on my desktop, but no file appears. And V2 Log Collector just refuses to run at all. The shortcut is apparently 1kb in size and I get an error window whenever I attempt to run it.