mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2015-04-08, 18:31   #1
badbud65
 
Apr 2015

17 Posts
Exclamation Various and Constant BSOD's.

Various and Constant BSOD's.

Relevant Files here:
Minidump and DxDiag Files available from Dropbox

All components are new as detailed below:

CPU: Intel Core i5-4690K 3.5GHz Quad-Core Processor
Motherboard: MSI Z97-GAMING 5 ATX LGA1150 Motherboard
CPU Cooler: Cooler Master Nepton 140XL 122.5 CFM Liquid CPU Cooler
Memory: Crucial 8GB (2 x 4GB) DDR3-1600 Memory
Video Card: MSI GeForce GTX 960 2GB Video Card
Storage: Crucial MX100 512GB 2.5" Solid State DriveMSI GeForce GTX 960 2GB Video Card
Case: NZXT Phantom 530 (Red) ATX Full Tower Case
Power Supply: Corsair CX 430W 80+ Bronze Certified Semi-Modular ATX Power Supply
Optical Drive: Samsung SH-224DB/BEBE DVD/CD Writer
Operating System: Microsoft Windows 7 Home Premium SP1 (OEM) (64-bit)
Case Fan: Corsair Air Series Purple 2 pack 52.2 CFM 120mm Fan
Case Fan: Corsair Air Series Purple 2 pack 52.2 CFM 120mm Fan

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 believe 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'v tried 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've tried with each of 4 sticks in all 4 slots.

However the more I've investigated the less I think it's Memory, I as certain as you can be that it's not memory.

I have re-installed my system 4 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. Although the CPU is running at 3.7 GHz instead of the stock 3.5.

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 were reported.

I've set "verifier" and no driver issues reported

I've Breadboarded and stripped the whole thing down to only crucial parts required to get Win7 to load and I'm still getting BSOD's.

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.

CPU has been taken out cleaned, pins in the socket appear undamaged. I've set it back up with new Thermal Compound.

Temperatures haven't been a problem.

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

Prime Blend Test produced one error within 5 minutes, I stopped the test and rebooted and started it again, no error seen for the last 30 minutes.

Code:
[Wed Apr 08 18:31:49 2015]
Self-test 12K passed!
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
BSOD'S in this Order:

Code:
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION	
PAGE_FAULT_BEYOND_END_OF_ALLOCATION	
BAD_POOL_HEADER	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
IRQL_NOT_LESS_OR_EQUAL	
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED	
NTFS_FILE_SYSTEM	
BAD_POOL_HEADER	
SYSTEM_SERVICE_EXCEPTION	
SYSTEM_SERVICE_EXCEPTION	
BAD_POOL_HEADER	
MEMORY_MANAGEMENT	
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED	
IRQL_NOT_LESS_OR_EQUAL	
NTFS_FILE_SYSTEM
badbud65 is offline   Reply With Quote
Old 2015-04-08, 18:43   #2
paulunderwood
 
paulunderwood's Avatar
 
Sep 2002
Database er0rr

24·229 Posts
Default

Maybe you need a beefier PSU
paulunderwood is offline   Reply With Quote
Old 2015-04-08, 19:00   #3
badbud65
 
Apr 2015

1116 Posts
Default

PSU is well within limits, even with the GFX card installed, it isn't installed at the moment though.

So unless the PSU is actually faulty then it's not the PSU.

I'm trying to determine where the fault is, hardware or drivers.

PSU at this time is an unlikely candidate, unless you can provide a more specific reason why you say

Quote:
Originally Posted by paulunderwood View Post
Maybe you need a beefier PSU
That's not related to Wattage Bias.

Prime Failures and a BSOD

[Wed Apr 08 19:50:15 2015]
FATAL ERROR: Rounding was 4.460210523e+285, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 896K passed!
Self-test 32K passed!
FATAL ERROR: Rounding was 2.173430923e+189, expected less than 0.4
Hardware failure detected, consult stress.txt file.
badbud65 is offline   Reply With Quote
Old 2015-04-08, 19:25   #4
paulunderwood
 
paulunderwood's Avatar
 
Sep 2002
Database er0rr

24×229 Posts
Default

WITH WARNING, you might have to bump up you CPU voltage a little and retest.
paulunderwood is offline   Reply With Quote
Old 2015-04-08, 20:11   #5
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

3×5×499 Posts
Default

If small FFT torture works and blend fails, then it is likely a memory (or memory controller) problem. Otherwise, CPU voltage is a reasonable guess.
Prime95 is offline   Reply With Quote
Old 2015-04-08, 21:49   #6
TheMawn
 
TheMawn's Avatar
 
May 2013
East. Always East.

6BF16 Posts
Default

Quote:
Originally Posted by badbud65 View Post
FATAL ERROR: Rounding was 4.460210523e+285, expected less than 0.4
FATAL ERROR: Rounding was 2.173430923e+189, expected less than 0.4
Um..... 4.46 x 10285 is notably larger than 0.4.

Crank up the voltage some. Run Prime95 within your capacity to do so and stay under 80C as much as possible. That platform overclocks into the 1.2V - 1.3V range so you can go pretty high and then just bring it down to reasonable levels later. If you STILL fail with voltage that high, then you're almost assuredly looking at bad hardware.

In order, my guess is bad CPU, bad PSU, then bad Motherboard.
TheMawn is offline   Reply With Quote
Old 2015-04-08, 23:15   #7
Mark Rose
 
Mark Rose's Avatar
 
"/X\(‘-‘)/X\"
Jan 2013

3×977 Posts
Default

Memtest from USB is probably running Linux. It's quite possible that the two operating systems are configuring the hardware differently. I would try disabling the various extensions/options/hardware in the BIOS and see if the problem goes away.
Mark Rose is offline   Reply With Quote
Old 2015-04-09, 00:29   #8
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

3×5×499 Posts
Default

Quote:
Originally Posted by Mark Rose View Post
Memtest from USB
Unless you are running a multi-threaded memtest you are not coming remotely close to stressing the memory bandwidth of a Haswell chip. Prime95 blend test will max out your memory bandwidth. Last I looked, two years ago, multi-threaded memtest had bugs that made it unusable.
Prime95 is offline   Reply With Quote
Old 2015-04-09, 01:46   #9
TheMawn
 
TheMawn's Avatar
 
May 2013
East. Always East.

110101111112 Posts
Default

Quote:
Originally Posted by Prime95 View Post
Unless you are running a multi-threaded memtest you are not coming remotely close to stressing the memory bandwidth of a Haswell chip. Prime95 blend test will max out your memory bandwidth. Last I looked, two years ago, multi-threaded memtest had bugs that made it unusable.
I was on that website a while back to grab a copy of it for some testing. I didn't use the multi-threaded one but I recall seeing something about fixes.

Memtest86+ will find physical problems on the DIMMs not related to memory bandwidth by virtue of testing all but a few KB of the stick whereas anything running in Windows has to be assigned to the specific bad sector and then have that fault become relevant (hence the random Windows BSOD's vs. hours of stability in a stress test or a game or whatever).

If the memory controller is just not stable enough, then George is correct: Prime95 is a better tool. There's just the AVX scare.
TheMawn is offline   Reply With Quote
Old 2015-04-09, 03:36   #10
LaurV
Romulan Interpreter
 
LaurV's Avatar
 
Jun 2011
Thailand

24E016 Posts
Default

Memtest working from stick but not from disk smells fishy, and there is no hardware reason to be so. I know a couple of viruses who do that. Ever played with or installed something called "Protect search"? (don't!)
Any non-normal activity when you open a browser? (like more ads than usual, home page changed, default search engine changed?)

Last fiddled with by LaurV on 2015-04-09 at 03:37
LaurV is offline   Reply With Quote
Old 2015-04-09, 04:28   #11
Mark Rose
 
Mark Rose's Avatar
 
"/X\(‘-‘)/X\"
Jan 2013

3×977 Posts
Default

Quote:
Originally Posted by Prime95 View Post
Unless you are running a multi-threaded memtest you are not coming remotely close to stressing the memory bandwidth of a Haswell chip. Prime95 blend test will max out your memory bandwidth. Last I looked, two years ago, multi-threaded memtest had bugs that made it unusable.
Good to know!
Mark Rose is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Prime95 64-bit v27.9 Build 1 BSOD storm5510 Software 9 2013-12-19 04:21
BSOD drajce Information & Answers 10 2013-01-03 19:20
help please with a bsod with a gtx550ti ernieboy Hardware 7 2012-07-27 08:45
BSOD I Get Illegal Sumout ?? Very Confused? Timewarpone Hardware 29 2010-05-23 05:10
bsod help Unregistered Information & Answers 6 2009-09-24 07:05

All times are UTC. The time now is 05:19.

Sun May 9 05:19:27 UTC 2021 up 31 days, 19 secs, 0 users, load averages: 1.27, 1.41, 1.49

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.