Various and Constant BSOD's.

bAdbUd

bAdbUd

bAdbUd

Associate
Joined
4 Apr 2015
Posts
26
Various and Constant BSOD's.

All components are new as detailed below:

Intel Core i5-4690K 3.5GHz Quad-Core Processor
MSI Z97-GAMING 5 ATX LGA1150 Motherboard
Crucial 8GB (2 x 4GB) DDR3-1600 Memory
Crucial MX100 512GB 2.5" Solid State Drive
MSI GeForce GTX 960 2GB Video Card
Corsair SPEC-01 RED ATX Mid Tower Case
Corsair CX 430W 80+ Bronze Certified Semi-Modular ATX Power Supply
Samsung SH-224DB/BEBE DVD/CD Writer
Microsoft Windows 7 Home Premium SP1 (OEM) (64-bit)
Corsair Air Series Purple 2 pack 52.2 CFM 120mm Fan
Corsair Air Series Purple 2 pack 52.2 CFM 120mm Fan
AOC G2460PQU 144Hz 24.0" Monitor

Since day 1 I've had problems with BSOD's, My initial investigation's lead down the routes of un-installing Avast and then running memtest86/64. When I run memtest64 in windows it produces errors, I belive this is due to using all available memory and getting into a deadlock state. When I run memtest86 off a USB drive no errors are reported. I've left it running for 10 passes, no errors found. I believe this is the better memtest to run, unless advised differently.

However I bought an identical set of memory and have tried them and still I'm getting random BSODs.

I'm currently trying each of the four sticks in each of the four slots available, I'm still getting BSOD's In Slot Two and Four together and Slot 1 and 3 together. I'm now trying one stick in each slot.

UPDATE:
=======
No change trying each of 4 sticks in all 4 slots.

However the more I've investigated the less I think it's Memory, but it could be the motherboard.

I have re-installed my system 3 times, fully updated Win7 with all patch's, only used manufacturer drivers for the Motherboard.

I haven't Overclocked anything, everything is running with default settings.

Bios for the motherboard hasn't been updated as it's the current version 1.9.

I have run sfc.exe /scannow and no problems where reported.

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Users\Steve Arthur>sfc.exe /scannow
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

I'm now going to set "verifier" following these instructions:

Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next" (or Type "verifier /standard /all" (no quotes) if you want to verify all of them (this will slow your computer down))
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Click to expand...

As you'll be able to see a common failure is due to Kernel System Error and often related to Graphics cards.

However there are also files attributed to the LAN drivers and other drivers, so I don't now know what else to check.

Please advise how I can go about determining what is the root cause of my problem.

Minidump and DxDiag Files available from Dropbox

UPDATE:
=======
I've now Breadboarded and stripped the whole thing down to only crucial parts required to get Win7 to load and I'm still getting BSOD's. However I'm now getting the same BSOD for the last 9. IRQL_NOT_LESS_OR_EQUAL, same file; ntoskrnl.exe and same address; ntoskrnl.exe+74ec0.

I haven't connected USB 2/3 Cables or Sound cables. Only cables connected are power to motherboard and JFP1 System Panel connectors and the stock CPU fan cable.

I've examined the motherboard back and front and I haven't noticed anything that looks out of the ordinary.

I'm now going to take the CPU out clean it and reattach.
 
Last edited by a moderator:
Hi,

I've removed all the links as some or all of them are for competitors and I'm not checking every one.

If you wish use links for components please use the manufacturer's site or the OcUK shop site.

Thanks.
 
Sorry about that, I just used a part picker site to get all the components, I didn't even buy them from thouse other sites.

Again sorry.

Any help with my question will be greatly appreciated.
 
If its passing low level memory testing but kicking out when testing memory in Windows this might be due to the controller or surrounding circuitry being unstable - requiring extra system agent/vtt/imc or pch voltage to be stable - I've seen it before where for some reason it doesn't manifest in memtest86 but will in Windows. Though more usually that results in 0x124 or 0x9C BSODs.
 
Sound's plausible, are you suggesting it's a motherboard issue?

I really don't think it's Memory, 4 sticks bought in pair's at separate occasions from different scource. Unlikely ALL 4 are problematic.
 
Have you tried manually setting the memory voltage? You could try increasing it slightly.

On my very old system (in sig), I had to set my dram voltage to 1.85 I think, when its mean to run at 1.8v (IIRC). I used to get random BSODS with it being set to auto and 1.8v.
 
I've set Ram voltage to Auto, 1.35 and 1.5.

Now that I've breadboard, literally, as the mobo is on a wooden breadboard. And still not got any closer to knowing the cause I'm doing a full reinstall.

I could do a Linux install, if anyone has idea's about diagnosing in Linux, Ubuntu specifically. Then I could iron out possible driver issues.
 
Last edited:
OracIe said:
Just checking.

BIOS all default? Sounds like it's going to be motherboard or PSU.
Click to expand...

I'm leading to motherboard, I don't understand why the PSU could be at fault.

Please explain your reasoning

Everything is default, as I want a stable system before I tweek.
 
I've reinstalled, (4th time). This time I'm not installing any drivers at all. I'm running a few standalone burn tests and see if I still get a BSOD.

If I do get one, then it's not driver related, but hardware.

Suspects from a hardware point are:

1: Motherboard, (I'm leading to this).
2: PSU, I don't believe it's that, I think some may say that due to it being 430W. I'm pulling 390 W from the wall, so it's hardly down to wattage issues.
3: CPU is also a possible candidate.
4: Memory I've ruled out.
5: Drivers, I'm testing that now.
 
Quite often if the PSU is faulty it wont supply reliable current as the system draws on it, or intermittent current which can lead to BSOD.

I would say try the paperclip test on the PSU (you tube it) but it would appear its working to a degree.

It will be either PSU or motherboard, without getting a spare or sending them away to test by way of RMA, you wont reliably know.

The only other thing it could be is an incorrectly seated CPU cooler on the CPU itself, causing an overheat or you *may* have bent one of the pins on the motherboard which you would need to check by removing the CPU.
 
bAdbUd said:
I've reinstalled, (4th time). This time I'm not installing any drivers at all. I'm running a few standalone burn tests and see if I still get a BSOD.

If I do get one, then it's not driver related, but hardware.

Suspects from a hardware point are:

1: Motherboard, (I'm leading to this).
2: PSU, I don't believe it's that, I think some may say that due to it being 430W. I'm pulling 390 W from the wall, so it's hardly down to wattage issues.
3: CPU is also a possible candidate.
4: Memory I've ruled out.
5: Drivers, I'm testing that now.
Click to expand...

I don't recall details off the top of my head but there were some issues with some PSUs and compatibility with one of the more recent intel CPU architectures.

My money would still be on needing a touch more voltage somewhere - likely related to the "chipset" to get it stable.

EDIT: PSU wattages is a far more complicated story than just taking what your drawing versus the on paper capabilities - which is why I usually recommend quite a bit of an overhead when speccing PSUs - you can get issues like it can only delivery a certain amount of amperage on a rail, actual power delivery dropping with age, etc. and some simply struggle when you get close to their rated level with things like ripple, etc. becoming an issue - 390 watt could potentially be easily too much for a 430w PSU to handle (depending a bit on who actually makes the internals of the PSU - I believe the CX430 is Channel Well who I've not particularly high regard for).
 
Last edited:
OracIe said:
Quite often if the PSU is faulty it wont supply reliable current as the system draws on it, or intermittent current which can lead to BSOD.

I would say try the paperclip test on the PSU (you tube it) but it would appear its working to a degree.

It will be either PSU or motherboard, without getting a spare or sending them away to test by way of RMA, you wont reliably know.

The only other thing it could be is an incorrectly seated CPU cooler on the CPU itself, causing an overheat or you *may* have bent one of the pins on the motherboard which you would need to check by removing the CPU.
Click to expand...

Taken out CPU, cleaned, checked for bent pins, nothing out of the ordinary seen.

Heat hasn't been a problem, runs at 40/70 C with stock heatsink and 25/50 C with water cooler and still I'm getting BSOD's.
 
You must log in or register to reply here.
Back
Top Bottom