BSOD several times per day... all different reasons. Need help!

I built a PC about a year ago. It ran pretty well until a few months ago. Now I'm getting a BSOD pretty much every time I try to use it. Once it BSODs, it seems it easily BSODs again right after and gets stuck in a sort of loop where it restarts and then BSOD within 5 minutes after a restart. I can't even begin to list all of the BSOD error messages I've gotten, but the most common seems to be MEMORY_MANAGEMENT (0x0000001A). After my last crash I got: IRQL_NOT_LESS_OR_EQUAL, but I don't remember getting that one before. Other than those, I've also gotten BAD_POOL_HEADER and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. I may have gotten others too, but I can't remember.

When I check my EventViewer log, all I see for critical errors are Kernel Power 41, which I think is just indicating that the PC shut down unexpectedly.

As far as Warnings in the EventViewer, I'm getting a TON of DeviceSetupManager errors. I'm also generally getting a TON of other errors. I mean like an error is being reported every minute or two.

My specs are:

ASRocks H97M Pro 4
CX750M PSU
Intel i5 4590 CPU
2 Rx480 GPUs (in crossfire)
PNY 8GB PC312800 DDR3DIMM Memeory (x2)
Seagate 1TB ATA Hard drive


Also, my DiskUsage under Task Manager is always 100% when the computer first starts and stays there for several minutes. It seems really slow (considering my specs) on start up. Once it's up and running, and the disk usage goes down, it's pretty snappy (except when it crashes).

Lastly, Google Chrome seems to trigger the MEMORY_MANAGEMENT error a lot. Not sure if there is a correlation, or if it just so happens that I use Chrome a lot and it's a coincidence.

kodiak1120 said:

While waiting for an answer, I started searching other threads about the MEMORY_MANAGEMENT error, and I saw reference to MemTest86+, so I downloaded it and created a boot USB stick and ran it. It's only 22% of the way completed and I have +370,000 errors. I think that means I have a RAM problem. I'm going to buy new RAM and run it again. Hopefully it's not a MB issue.

That is what I have gathered from the files you uploaded. That, plus so many errors from memtest86 would most definitely indicate a RAM issue. Bad RAM can cause a whole host of interesting errors to come up.