Random BSOD - Windows 7 Pro - Brand New PC Build - ntoskrnl.exe

G

Guest

Guest
Hi Guys,

This is my first attempt at building my own computer so I am not a pro by any means. I've been having issues with blue screens ever since I put it together. All the parts are new out of the box. When I first put the machine together I did some troubleshooting on my own and with a NewEgg tech. The tech couldn't pin point the issue so he advised me to RMA the motherboard and RAM.

I got the replacement motherboard and RAM a few days ago but the issue persists. I am using BlueScreenView to look at my minidump files. Before the RMA I would see "caused by driver" listings for multiple files. Since I got the new parts I am mostly seeing ntoskrnl.exe listed.

I have tried the Windows Memory Diagnostic tool a couple times and it says no errors have been found. I would really appreciate some help. Here are some specs on my machine and the download link to my minidump files. Thanks in advance.

http://leonardocarrion.com/minidump.htm

Windows 7 Professional Service Pack 1
i7 4770k CPU
Gigabyte GA-Z87X-OC Motherboard
ThermalTake TR2 600w Power supply
G. Skill 16GB DDR3 Memory
GeForce GTX 650 Ti Boost
Samsung 840 Pro SSD (C: Drive)
Seagate SV35 1TB HDD
ST1000VX000-1CU162 ATA HDD - (Old hdd from my last computer)
 
Solution


Have you overclocked your CPU at all? If so I...
G

Guest

Guest


Yea I did a fresh reinstall. That was before I did the RMA for the replacement parts.

 
G

Guest

Guest


Will reinstall. I'll let you know how it goes.
 

Leo340

Honorable
Aug 3, 2013
1
0
10,510




Hey,

Sorry for the delay. I just got done wiping and reinstalling the OS but I am still getting the BSOD. After reinstalling the OS I downloaded and installed just the latest/necessary drivers for my motherboard and graphics card. I got a blue screen shortly after. I then tried installing important windows updated only using windows update. That didn't help either.

I checked BlueScreen View to see what driver caused the crash and "ntoskrnl.exe" is listed for both crashes. Any ideas?
 

g-unit1111

Titan
Moderator


Have you overclocked your CPU at all? If so I would try going into your motherboard's BIOS and running your rig on default settings and see what that does.
 
Solution