Intermittent BSOD

[XxKINGxX40]

Sorry guys, don't know if this is the right thread for this topic. I've been having intermittent BSODs with my new PC. It always happens right after it boots to Windows. Sometimes it does it twice or three times in a row.

At first I thought it was the overclock, but I returned everything back to stock.

PC specs:

i7 7700K

Asus Z270i

2x8GB Team Vulcan RAM

GTX 1080

 

[RileyTheFox]

9 minutes ago, XxKINGxX40 said:

Sorry guys, don't know if this is the right thread for this topic. I've been having intermittent BSODs with my new PC. It always happens right after it boots to Windows. Sometimes it does it twice or three times in a row.

At first I thought it was the overclock, but I returned everything back to stock.

PC specs:

i7 7700K

Asus Z270i

2x8GB Team Vulcan RAM

GTX 1080

1

 

Could you find the .dmp file in C:\Windows\Minidump and attach it? I can look at the crash in more detail then.

[XxKINGxX40]

9 hours ago, EvilCat70 said:

Could you find the .dmp file in C:\Windows\Minidump and attach it? I can look at the crash in more detail then.

 

032017-5281-01.dmp

[RileyTheFox]

14 hours ago, XxKINGxX40 said:

 

032017-5281-01.dmp

 

 

 

So, from using Bluescreen View (from Nirsoft) I can evaluate that you are getting the bug check code 0x000000da. This can mean any of the following: 

 

Wrongly configured, old, or damaged system drivers.

Windows registry database corruption.

Malware infection.

Drivers crashing after adding new hardware to your system.

Damaged hard disk.

SYSTEM_PTE_MISUSE STOP error due to RAM corruption.

 

If it is bad system drivers, DDU or a fresh install of Windows will work.

If it is the Windows registry, clean install of Windows.

If it is a malware infection, run your Anti-Virus and Anti-Malware (Malwarebytes is very good)

If it is the drivers of new hardware (or existing), DDU the drivers and fresh install them. If that doesn't work, it's faulty hardware.

If you suspect you have a faulty hard disk, download CrystalDisk Info and see if there are any cautions such as unreadable sector counts. (You can also run chkdsk on the C: drive from an Admin privileged command prompt)

If you think it's due to a RAM issue, test each stick of RAM in each slot available on your motherboard. If a stick turns out to be bad, snap it (so no one else can end up getting it either through an electronic dump site or second-hand shop) and throw it away.

 

I hope any of these fixes your issues. If not, quote me and I'll try and help you

 

EDIT: The driver that caused the issue was ntoskrnl.exe. So there was some sort of 'kernel panic' and it shut off.