4 BSOD's in less than 30 minutes

[failedtolisten]

I know some will ask me if my drivers are up to date. As far as I know, they all are. I know others may ask me if I've overclocked or made it recent hardware changes. I have not. This build is almost brand new as I built it right before November 2017. The ONLY hardware change(if this can even be considered)is my monitors. I have an old Dell that has just a display port and DVI. I don't know what I did with my DVI cable, so I took the DisplayPort cable from my 144hz Asus monitor and used it on the old 60hz Dell. I was using the HDMI on 144hz Asus, but at the time of this posting, I've unhooked the old Dell and once again using the DisplayPort cable on my Asus. I was having to play at 60hz on the Asus until the new DisplayPort cable arrives. I have no idea if this could have caused an issue or not. Maybe NVIDIA drivers didn't like that during driver installation I had one monitor at 144hz and then suddenly had settle for 60 with a completely different cable.

Specs:

Fractal Design Define R5 Black Window Silent ATX Midtower
ASUS ROG Crosshair VI Hero
Ryzen 1700x
MSI GTX 980 TI
Corsair Vengeance DDR4 16GB@3000mhz
EVGA SuperNOVA 850W 80+ PLATINUM
1x 1TB Crucial MX300 SSD
2x 850 Samsung EVO 500GB SDD

One BSOD stop code said Attempted to Write Read Only Memory, another said IRQL not less or equal, another simply said Memory Management, and the first one I received said Driver Overan Stack Buffer. ALL of this happened in less than 30 minutes. At one point, I opened up Chrome, tried to click on a tab, and I got one of those BSODs. Nothing seems to be happening now, but I'm gonna try and play some PUBG. The first time it happened I was playing PUBG, so I guess we'll see what happens.

 

[Paul NZ]

May I also ask why a couple people have suggested to unplug the other two SSD's while setting up fresh install of Windows?

Because when you install windows on whatever hdd / ssd the files can end up on the wrong ssd.

Esp the boot files. And one way to find out if this has happened.

If you unplug the other hdds (if you leave them connected when you install windows). After windows has been installed on whatever hdd.

The hdd you did install windows on may not boot. Because part of the boot file is on one of the other hdds.

 

[failedtolisten]

May I also ask why a couple people have suggested to unplug the other two SSD's while setting up fresh install of Windows?

Because when you install windows on whatever hdd / ssd the files can end up on the wrong ssd.

If more than 1 hdd is connected

Which is why you should unplug them when you install windows. Reconnect them after windows has been installed

It's weird that while it's installing it would install files to drives/SSD's you didn't select. Thanks for the information, though. I wasn't aware of that.

 

[failedtolisten]

As for the ISO file, I'm not sure I ever had one? Is there a direct link to the Windows ISO?

 

[Paul NZ]

You used the mediacreation tool before . You get the ISO with that but select for another computer. So it downloads it

Then use Rufus so it extracts it to a flash drive (do the above)

 

[Paul NZ]

I think those 2 options are network boot options. Are you using RAID or something why you're using 2 850's?

If you've still got the ISO use Rufus instead. Sometimes the tool can screw things up

And what ssd did you install windows on?? The MX300?

Any reason it would randomly put those two network boot options there instead of my other two SSD's? Not running raid. I use one SSD for Windows, one for all my gameplay videos, MX300 for nothing but games.

If nothing is on those 2 ssd's that maybe the reason why they dont appear in the boot menu.

And if they did appear under the boot menu, if there's nothing on them, they wont boot anyway

 

[Paul NZ]

Does the ssd you did install windows on appear in the bootmenu as UEFI: Name of ssd?

 

[failedtolisten]

I think those 2 options are network boot options. Are you using RAID or something why you're using 2 850's?

If you've still got the ISO use Rufus instead. Sometimes the tool can screw things up

And what ssd did you install windows on?? The MX300?

Any reason it would randomly put those two network boot options there instead of my other two SSD's? Not running raid. I use one SSD for Windows, one for all my gameplay videos, MX300 for nothing but games.

If nothing is on those 2 ssd's that maybe the reason why they dont appear in the boot menu.

And if they did appear under the boot menu, if there's nothing on them, they wont boot anyway

There is some gameplay on one and the other is full of about...idk...30 Steam games.

 

[Paul NZ]

Ok so windows is on the MX300 which appears in the bootmenu as UEFI: Name of ssd?

That'll be why the 2 850's dont appear in the boot menu. They're not bootable

 

[failedtolisten]

Ok so windows is on the MX300 which appears in the bootmenu as UEFI: Name of ssd?

That'll be why the 2 850's dont appear in the boot menu. They're not bootable

No, again, one of the 500GB's have Windows, the other some gameplay, and the MX300 has my Steam games. Sorry if I may have said something else.

Also, no, the SSD with Windows on it says P1: Samsung EVO 500GB...nothing with UEFI

 

[Paul NZ]

Ok well, I would unplug the other 2 hdd's

Then do the above. Get the ISO again get rufus put a flash drive in select GPT in Rufus add ISO. Wait for it to finish

Reboot go into the BIOS make sure AHCI secureboot and UEFI are enabled first. If you're installing 64 bit.

Save settings then reinstall windows on one of the 500 GB ssds. Delete all partitions first

Then it may change to UEFI: Name of SSD. After Windows has been reinstalled, reconnect the other ssd's

 

[failedtolisten]

Ok well, I would unplug the other 2 hdd's

Then do the above. Get the ISO again get rufus put a flash drive in select GPT in Rufus add ISO. Wait for it to finish

Reboot go into the BIOS make sure AHCI secureboot and UEFI are enabled first. If you're installing 64 bit.

Save settings then reinstall windows on one of the 500 GB ssds. Delete all partitions first

Then it may change to UEFI: Name of SSD. After Windows has been reinstalled, reconnect the other ssd's

Ok, I did exactly as you stated. I'm currently on another fresh install of Windows following your directions. Only been about an hour or so, but no BSOD so far. I will keep this thread updated if anything else happens.

 

[Paul NZ]

Sweet !

 

[failedtolisten]

Something told me that it couldn't last. I just received another crash about 30 minutes ago.

Here are the dump files:

https://drive.google.com/file/d/17IdwyCJ0acn-5xLXEam-FPGLpoxFZ9sN/view?usp=sharing

https://drive.google.com/file/d/1glXUtE6G-oZcmbwHKZOoqWno2FMTL-e6/view?usp=sharing

I'm so worried now. I feel like with two fresh installs of Windows, both of which have given me at least one crash(the current has given me two), that this is hardware related. I've tested RAM. I've tested the SSD's. The error codes all say something different. I don't know what's wrong.

 

[Paul NZ]

Is the latest firmware on the Samusung ssd's?? And WHEN does it crash now. What were you doing?

And is the firmware on the MX300 up to date?? It looks like the MX300 has also got issues. It can freeze your system

 

[failedtolisten]

Is the latest firmware on the Samusung ssd's?? And WHEN does it crash now. What were you doing?

And is the firmware on the MX300 up to date?? It looks like the MX300 has also got issues. It can freeze your system

I was actually doing nothing. I was napping when the first crash occurred. The PC was on with Chrome open and about three tabs open.

I can check if those are up to date. It wouldn't hurt. That being said, when I built this PC a couple months back, I moved my GPU and those same SSD's from my Intel machine. I probably wasn't running the latest firmware with them over on that build and was not receiving these issues.

 

[Paul NZ]

Umm I would check the sata cables these ssd's are connected to.

Make sure the ssd end is in properly. On the other pc here, I had to force the cable on before I connected it to the side of the case. Because when I connected it to the side of the side and connected the cable, it wouldnt connect properly

 

[failedtolisten]

Umm I would check the sata cables these ssd's are connected to.

Make sure the ssd end is in properly. On the other pc here, I had to force the cable on before I connected it to the side of the case. Because when I connected it to the side of the side and connected the cable, it wouldnt connect properly

I can check them. That being said, the two Samsung SSD's ended up having the latest firmware. When I went to update the MX300, the software said it needed to reboot. I agreed. As Windows began to shut everything down, I got another BSOD. However, the firmware in the MX300 was updated during reboot anyway.

Also, here is the .dmp for that BSOD

https://drive.google.com/file/d/1mI-wsCm_CDSUThaFoanJclKShPyZj7a8/view?usp=sharing

 

[Paul NZ]

What did the BSOD say when it tried to shut down??

Strange that it crashed when it shut down

 

[failedtolisten]

And another BSOD minutes after I sent last reply on here

https://drive.google.com/open?id=1mI-wsCm_CDSUThaFoanJclKShPyZj7a8

Another MEMORY MANAGEMENT error code

 

[failedtolisten]

What did the BSOD say when it tried to shut down??

Strange that it crashed when it shut down

Yes. That also said Memory Management. Like the one I just got

 

[Paul NZ]

Looks like chrome caused the last crash which was 0x1a - memory management

Disable hardware acceleration in Chrome.

I dont know why people use Chrome, it's the buggiest browser around.

 

[failedtolisten]

Looks like chrome caused the last crash which was 0x1a - memory management

Disable hardware acceleration in Chrome.

I dont know why people use Chrome, it's the buggiest browser around.

I can try that. Just to verify, are you saying Chrome is the source of all this? Seems kind of random and out of nowhere for it to be Chrome. What browser would you suggest?

 

[Paul NZ]

Anything but Chrome lol. Well, it was the cause of the last crash

Dont know if it's the cause of ALL the crashes.

But I wouldn't be surprised if it is. If it was running at the same time, all of the crashes occurred

I've been using firefox. Nothing wrong with it so far. No crashes whatsoever

https://www.mozilla.org/en-US/firefox/all/

 

[failedtolisten]

Anything but Chrome lol. Well, it was the cause of the last crash

Dont know if it's the cause of ALL the crashes.

But I wouldn't be surprised if it is. If it was running at the same time all of the crashes occurred

I've been using firefox. Nothing wrong it so far. No crashes whatsoever

https://www.mozilla.org/en-US/firefox/all/

I can promise you, Chrome was not running when the very first crash happened a couple nights ago while playing PUBG. I never leave anything open but the game.

 

[Paul NZ]

Umm one thing. When you built this, did you install the standoffs if the case didnt come with them pre-installed?

If you didnt the mobo will short on the case