Jump to content

Constant blue screens

Go to solution Solved by Bombastinator,

One thing to look at is what the blue screen errors are.  A mini dump could also be useful.  There are pinned posts at the top of the troubleshooting section with various sets of directions and lists of stats that are usually needed.  One thing that is basically always needed is a complete parts list.  This could possibly be a HDD issue for example.

 

 One common cause of crash after boot is memory problems.  Another lately is underpowered PSUs though you don’t seem to have the kind of equipment that commonly causes that.  Checking memory integrity is generally a step in such things.  May not turn up anything but it’s free if somewhat time consuming.  Memtest86 is old and slow but still works well. If a few passes come back clean it doesn’t completely rule out a memory problem but makes it far less likely.

Hey so a month ago I had changed my cpu cooler and then did a clean install of windows 11, after repeated crashes and numerous amounts of time spent researching what could be the issue I decided to do clean install back to windows 10, surprisingly these blue screens didn't go away, so then I thought maybe it's my GPU because most of the times the blue screen error would happen when in midst of a game or my gpu driver would just randomly disconnect, so I installed my old gpu and the blue screens did not stop. I honestly have no idea what to do or what could be the cause of these issues. What I've did:

1. Sfcscan 

2. Memory diagnostic (no issues were found)

3. Disk scan ( all healthy )

4. Manually made sure that every driver is up to date.

 

My pc specs:

Ryzen 7 2700x

RX 580 swapped with GTX 960

16gb of G. Skill 3200mhz 

 

I honestly don't know what to do and if anyone can give me any tips of how to find out what's the issue is would be lovely! Thanks

Link to comment
https://linustechtips.com/topic/1390089-constant-blue-screens/
Share on other sites

Link to post
Share on other sites

One thing to look at is what the blue screen errors are.  A mini dump could also be useful.  There are pinned posts at the top of the troubleshooting section with various sets of directions and lists of stats that are usually needed.  One thing that is basically always needed is a complete parts list.  This could possibly be a HDD issue for example.

 

 One common cause of crash after boot is memory problems.  Another lately is underpowered PSUs though you don’t seem to have the kind of equipment that commonly causes that.  Checking memory integrity is generally a step in such things.  May not turn up anything but it’s free if somewhat time consuming.  Memtest86 is old and slow but still works well. If a few passes come back clean it doesn’t completely rule out a memory problem but makes it far less likely.

Not a pro, not even very good.  I’m just old and have time currently.  Assuming I know a lot about computers can be a mistake.

 

Life is like a bowl of chocolates: there are all these little crinkly paper cups everywhere.

Link to comment
https://linustechtips.com/topic/1390089-constant-blue-screens/#findComment-15114298
Share on other sites

Link to post
Share on other sites

32 minutes ago, oop778 said:

Well one thing is that every time the blue screen error is different but most of the time it has to do with memory, I did run the windows memory diagnostic and it said there was no issues

There is an old and sometimes more subtle test which predates memtest86. Takes a variable and sometimes quite long time though.  It relies on the concept that with more than one memory stick it is likely that only one of them will be bad. As such it is not always useful.  You put in only a single stick of memory and run the thing.  If it errors out you run the other one.  If it DOESN’T error out you’ve found the problem, which is the other stick. If it does the memory is probably (but still less than 100%) ok, and the problem is likely elsewhere.  It’s been known to catch subtle stuff that memtest86 missed.  I don’t know what the current bundled memory test is.  Generally a few full runs of memtest86 is enough to make other problems worth examining first before going back to memory and messing with the single stick test.  A likelyhood thing. 

Not a pro, not even very good.  I’m just old and have time currently.  Assuming I know a lot about computers can be a mistake.

 

Life is like a bowl of chocolates: there are all these little crinkly paper cups everywhere.

Link to comment
https://linustechtips.com/topic/1390089-constant-blue-screens/#findComment-15114494
Share on other sites

Link to post
Share on other sites

20 hours ago, Bombastinator said:

There is an old and sometimes more subtle test which predates memtest86. Takes a variable and sometimes quite long time though.  It relies on the concept that with more than one memory stick it is likely that only one of them will be bad. As such it is not always useful.  You put in only a single stick of memory and run the thing.  If it errors out you run the other one.  If it DOESN’T error out you’ve found the problem, which is the other stick. If it does the memory is probably (but still less than 100%) ok, and the problem is likely elsewhere.  It’s been known to catch subtle stuff that memtest86 missed.  I don’t know what the current bundled memory test is.  Generally a few full runs of memtest86 is enough to make other problems worth examining first before going back to memory and messing with the single stick test.  A likelyhood thing. 

After 2 passes of memtest86 I have 79 errors does that mean my memory is ripped? 

Link to comment
https://linustechtips.com/topic/1390089-constant-blue-screens/#findComment-15115835
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

×