So this is roughly a two month old computer. It was working fine for the first month or so, and then I began getting many BSODs.
I will warn you now, this is probably a wall of text, and I'm sorry for that...
The first error code was 0x0000001A, a memory management error. It sometimes happened when I booted up, but after 2-3 happenings, it never came back.
After a good run of no blue screens, I got the next error, which was a 0x000000F4 error code. I can't remember the text error, just the code. Now this one really fucked me over, as I ended up having to re-install Windows on a clean install. After doing all that, another blue screen started plaguing me.
This one was a 0x00000050 blue screen, which was a page_fault_in_non_paged_area. What the fuck is that? Anyways the first time it happened was directly after re-installing Windows, when I tried to boot up steam. It happened again right when I logged on today.
This has brought me to wonder, what is wrong with this computer? After those first memory management errors, I ran multiple memtests and nothing came up. Checked the hard drive's health and did a chkdsk, nothing. I doubt the CPU has anything to do with it, along with the GPU. This narrows it down to possibly the MOBO, but I highly doubt it as other hardware hasn't really been failing. Again, I doubt the PSU is the problem either. It may be Windows just fucking up, but that seems weird as even after a completely clean install, I got another BSOD.
Here is a pic of the specs
[IMG]http://i.imgur.com/TnIpT.png[/IMG]
The 2500k is actually @ 4.5 ghz, speccy doesn't pick that up.
Any help is greatly appreciated, as I have no clue what is up.
Downclock your CPU to its original value and see if that helps.
[QUOTE=taipan;33058137]Downclock your CPU to its original value and see if that helps.[/QUOTE]
I'll give it a go, but I doubt this is really the issue as 2/3 of the blue screens occurred before it was OC'd, I only got the cooler last week or so.
Download memtest and run that for 24 hours.
Alright, I'll probably set it up tonight and let it run.
Will post results.
Turns out it seems to be my RAM. Guess I'm going to have to RMA it...
Sorry, you need to Log In to post a reply to this thread.
