Jump to content

Random frequent BSOD

MrKev
By MrKev
in Troubleshooting
 Share
Posted

I've been experiencing a few blue screens over the last few weeks/months but recently it's been a lot more frequent and I figured I'd try and sort it out now.

 

The most common error messages I'm getting are:

SYSTEM_SERVICE_EXCEPTION

MEMORY_MANAGEMENT
 
There have been a few other ones however I can't recall them.
 
I've uploaded dump files to Dropbox which have been saved over the last few weeks. Hopefully someone can take a look and help me out!
 
 
 
PC Specs:
Corsair 600W (CMPSU-600CX) PSU
8GB (2x4GB) Corsair DDR3 Vengeance Arctic White, 1600MHz
Gigabyte GA-Z77-D3H
Intel i5 3570K 3.4GHz
NVIDIA GeForce GTX 560 (1GB)
Western Digital Caviar Blue 500GB SATAIII 6Gb/s 16MB Cache
 
Thanks.
Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Test your memory. Remove one of the DIMMs and run the machine. If it blue screens again, switch to the other DIMM and try again.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

What was the last time you did a clean install

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Sounds like either bad memory, or memory that's been overclocked too far.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I have gotten that Code with a combination of not enough voltage and a virus so try to connect the psu cable directly to your wall and check if you can do a clean install

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

What was the last time you did a clean install

 

Quite a while ago.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Quite a while ago.

You should probably do that then, it will fix all the BSOD problems.

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

You should probably do that then, it will fix all the BSOD problems.

That's a fairly large assumption to make, especially considering the OP has not mentioned any hardware changes in the last few weeks. We have no information as to whether or not he/she has. You don't even know for sure(or if at all) the BSODs are caused by a bad OS install.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

That's a fairly large assumption to make, especially considering the OP has not mentioned any hardware changes in the last few weeks. We have no information as to whether or not he/she has. You don't even know for sure(or if at all) the BSODs are caused by a bad OS install.

 

Just to clarify, I haven't changed the hardware at all since I've had the PC.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

That's a fairly large assumption to make, especially considering the OP has not mentioned any hardware changes in the last few weeks. We have no information as to whether or not he/she has. You don't even know for sure(or if at all) the BSOD is caused by a bad OS install.

The thing is those errors are from issues from OS corruption. So it is possible his drive is dying, he can use crystaldiskinfo check the amount of errors.

http://crystalmark.info/download/index-e.html

If there are lots of relocated sectors and errors, then he should replace the drive and do a clean install.

If the drive is fine, then he should do a clean install.

 

Either way he is going to be doing a clean install.

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

The thing is those errors are from issues from OS corruption. So it is possible his drive is dying, he can use crystaldiskinfo check the amount of errors.

http://crystalmark.info/download/index-e.html

If there are lots of relocated sectors and errors, then he should replace the drive and do a clean install.

If the drive is fine, then he should do a clean install.

Either way he is going to be doing a clean install.

BSOD stop codes are fairly generic. I had a CPU overclock that was unstable. The BSOD blamed the NVIDIA kernel driver. The drivers had absolutely nothing to do with it. Pulled back my overclock and everything was fine.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

BSOD stop codes are fairly generic. I had a CPU overclock that was unstable. The BSOD blamed the NVIDIA kernel driver. The drivers had absolutely nothing to do with it. Pulled back my overclock and everything was fine.

Are you sure it said driver?

For overclock crashes it should say kernel power

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Are you sure it said driver?

For overclock crashes it should say kernel power

I looked up the stop code. It was referring to the NVIDIA kernel driver.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I looked up the stop code. It was referring to the NVIDIA kernel driver.

Were you BLCK overclocking?

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Were you BLCK overclocking?

No. Only multiplier.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Test your memory. Remove one of the DIMMs and run the machine. If it blue screens again, switch to the other DIMM and try again.

 

Since it blue screens at random times, should I just run the PC with one DIMM as normal and see how it goes for, say, a day?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Since it blue screens at random times, should I just run the PC with one DIMM as normal and see how it goes for, say, a day?

Yes.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

The thing is those errors are from issues from OS corruption. So it is possible his drive is dying, he can use crystaldiskinfo check the amount of errors.

http://crystalmark.info/download/index-e.html

If there are lots of relocated sectors and errors, then he should replace the drive and do a clean install.

If the drive is fine, then he should do a clean install.

 

Either way he is going to be doing a clean install.

 

So I installed crystaldiskinfo but I'm not too sure what I'm looking at/meant to be looking at? Here's a screenshot:

 

post-950-0-63023300-1417214806.png

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

So I installed crystaldiskinfo but I'm not too sure what I'm looking at/meant to be looking at? Here's a screenshot:

 

attachicon.gifScreenshot_1.png

Drive looks fine. Blue icons mean "good" according to the program. Alternatively, you can schedule a disk check as well. This allows Windows to check the hard drive for bad sectors. This requires a system restart and takes a considerable amount of time.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Drive looks fine. Blue icons mean "good" according to the program. Alternatively, you can schedule a disk check as well. This allows Windows to check the hard drive for bad sectors. This requires a system restart and takes a considerable amount of time.

 

Thanks. I ran the disk check and it came back with no errors (on Windows 8 it doesn't require a restart and took a few mins). Right now I'm just using my PC with one DIMM and I'll see how it goes through today/tomorrow.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Quick update:

 

I used one DIMM for almost a week with no issues. Since yesterday I switched to the other DIMM and today I've experienced one BSOD so far with the "MEMORY_MANAGEMENT" error.

 

 

Dump file, if it's of any use

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Another update:

So I just turned on my PC, and after about 10 seconds it just turned back off. This happened twice and the third time it booted however another "MEMORY_MANAGEMENT" BSOD occurred.

I guess this means there's definitely an issue with the DIMM?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I would say so.

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

I would say so.

 

Is there anything I can do, or is my only option to purchase new memory?

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×