New
#1
First BSOD on a custom build computer in 2 year - f4 error
So firstly, i love that there is a forum dedicated to the dreaded BSOD.
Setting the scene: Last night i put my computer on sleep mode for the first time ever whilst i went sleepies- normally i just perform a shut down. Bright lights were flashing in my room so i couldnt get to sleep, so lazy me turns on the computer from sleep mode and just holds the power button down to turn the computer off. Everytime the computer boots, just after the windows logo appears...BSOD everytime.
I did install a new data drive about 2 weeks ago, which could be the root of the problem????
After about 6 hours of research and 4 cups of coffee (I am pretty much a complete noob at this) i found that f4 errors are generally a hardware issue.
Things i have tried:
-System restore to earlier date....basic stuff
-Change sata cables around - even having the boot disk (call it drive1-SSD) in other sata drives and changing settings accordingly in bios (which i hope was the right thing to do) - I only had that boot disk connected. My data HD were disconnected.
-Installing w7 on another hard drive. Works fine. All files appear on the SSD when i reconnected it
-Can't run safe mode at all - BSOD aswell but vanishes in a blink of an eye.
-Ran memory diagnostics - all fine.
-Can't use memtest86 because none of my usb will allow the image to be unpacked for a bootable usb (if that made sense)
And just some thoughts....
I am wondering though if it would make a difference changing the RAM sticks around. I know this is an easy one to try, but i dont see it logical that swapping sticks in slots would make a difference.
I have also seen a lot of post about performing a crash dump log. Can this be performed through command prompts at all? Or any other way that doesnt require your computer to be somewhat working.
Thanks in advance for the insight you may bring.