Solved Random BSOD's ntoskrnl.exe new PC build

[bsodddd]

Hi, I built a new pc but since putting it together and installing windows7 i have been getting BSOD's with varying bug check string values, but is nearly always caused by the driver "ntoskrnl.exe". not sure what to do and it's really starting to annoy me as I thought it could be the wireless driver so I updated it and had no bsod for a week or so but they have started occurring again, any help provided would be much appreciated. Attached are my dump files and other stuff the program deemed important.

 

[Arc]

Multiple bugcheck codes in a small time interval. It indicates to a memory malfunction. Not necessarily the physical memory, a misbehaving driver may also do it.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________

BugCheck 18, {0, fffffa8007e9a7b0, 2, fffffa8006b1c780}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )

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

BugCheck 50, {ffffd6fb7ea00118, 0, fffff800035c1382, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43781 )

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

BugCheck A, {20, 2, 1, fffff800034cd77c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+605 )

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

 

[bsodddd]

Hi and thanks for the reply, I did suspect the memory was the issue and I ran the inbuilt windows memory diagnostic twice with no errors, however I will run memtest and see if it reports anything different, I also ran driver verifier with no crashes but this was only for 2 hours maximum so if memtest reports no problems i will leave driver verifier running for the full 24 hours and report back. Once again thank you, your help is greatly appreciated.

 

[Arc]

Hi mate, make it sure that you are running memtest86+ as pointed in the tutorial. There are other programs with deceptively similar names which are not only inferior tools but also not very trustworthy.

 

[bsodddd]

Hi Arc, an update, I ran memtest86+, the one linked in your reply, I had 8 passes and 0 errors so it's not the memory, however when I booted my pc up after the tests had complete to activate driver verifier I had another bsod, I have been running the driver verifier with the recommended settings in the link you provided since about midnight last night, but still no signs of a bsod which is annoying, no doubt as soon as I turn it off I will get 3 bsod's

 

[bsodddd]

Well I've had driver verifier on for 24 hours now with the computer being constantly on with no signs of a bsod, I've been stressing the machine with multiple programs open and multiple tabs open streaming youtube videos in 1080p but still nothing, just wondering what you would advise? Maybe I should restart the driver verifier to include microsoft drivers also in case it is a faulty windows installation? I have ran the sfc /scannow command to check if the windows files were corrupted but that came back all clear also so I'm running out of ideas, I will keep the driver verifier running as is in case a bsod pops up in the mean time.

 

[Arc]

No need to keep DV enabled after 24 hours. Usually it cause BSODs too early.

But ... when there are so much RANDOM BSODs, and neither memtest86+ nor DV found any error, then the we have very little left to do ATM.

Run the computer normally. If it starts causing BSODs, boot into safe mode and run in safe mode for a couple of hours. Let us know it went.

 

[bsodddd]

Hi well I was using my computer as normal and had a crash, however this was just a complete freeze, everything including the mouse pointer froze and I had to do a hard reset, then when the windows logo started it just reset, it did this twice before it would successfully start....... I'm not sure whether a bsod was supposed to be displayed but it crashed before it displayed and dumped the memory or what but I've never had problems like this with a computer so I'm lost.

 

[Arc]

Just in case, do some other checks.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[bsodddd]

Hi, just an update, I did run the tests you asked of me, my machine needs 34 watts and I had a 500 watt PSU, I also passed the cpu stress test and the gpu test, both fine, however when I powered off my machine during the night, when I tried to power it on in the afternoon it would power on, all the fans, the hard disk and the disc drive were running, but there was no display, I tested if the monitor was to blame by waiting 20 mins and trying to enter my password and waiting for the windows boot sound to be played through my speakers but I couldn't even enable the CAPS lock key so this told me that the machine wasn't even getting to the bios screen. I cleared the cmos as a possible fix but it didn't work, I purchased a new PSU as I suspected the cheap one I got with the case was faulty somehow and that seemed to do the trick, I don't know whether that was the cause of the BSOD's or not but since I've installed the new PSU some things that never worked before are working now so I'm marking this one as solved now as I'm fairly certain the PSU must have been the cause of my BSOD's, Thanks for your help Archie.

 

[Arc]

The PSUs inbuilt in the cases are always crap. The good case makers (like CoolerMaster) mostly does not provide a PSU with a case. It is never recommended that you use the stock PSU came with the case.