BSOD

[Basie]

Getting a BSOD 0x34 Cache_Manager error. Tried swapping out my memory and that didn't work. I have a Adata SSD which this is happening on. I have a Windows 7 OS on another drive along with my Linux OS's. The Win 7 gets the same 0x34 error but my Linux distros boot up fine. Maybe it's my SSD drive but I can access all my Win 7 & 8 files from Linux.

 

[Ketchup]

So is the Windows OS booting to the desktop? When are you seeing this message? Usually you will see this message when you are running extremely low/out of memory. Possible causes would be a leaking driver/application or not having enough page file available.

 

[Basie]

No, Windows never boots. It does start and then I get the BSOD very quickly. I do have 8G of Ram and I swapped that out and no help. Weird that it boots up my Linux distros without a problem. Even tried using a Windows Recovery disk and it does start but quickly gets the same BSOD. I was getting that low memory warning and did change the setting to let the OS handle it. It went from 600MB to 3500MB. Using Safe Mode I experience the same problem.

 

[Ketchup]

A blue screen that quickly also reminds me of what one would see with a BIOS settings change. If nothing (such as AHCI mode) has been changed, you may want to take the approach of removing all unnecessary hardware (inside and outside) to see if that makes a difference.

At the very least, your problems are somewhat limited to the fact that Windows only is having the error.

 

[Mark R]

This BSOD is usually caused by a bad driver. If you can revert to a last known good configuration, that might be worth trying.

 

[JackMDS]

Maybe this can Help.

http://nirsoft.net/utils/blue_screen_view.html

 

[Basie]

I can't boot into any of my Windows OS's so the utility that you recommended is a non issue. I used it in the past though. Today, I took the Box apart and disconnected everything, cleaned the CPU and re-installed new Arctic silver and at least lowered the temp about 8 degrees. No Help. Still getting the same BSOD as soon as Windows starts to load. But, no problem with my Linux OS's. Even using Windows Recovery DvD's it does the same thing. Wondering if it could be a Motherboard memory controller? Though why it boots Linux with no problem is puzzling.

 

[Ketchup]

If you want to view your blue screens, you can pull the minidumps from the Windows/Minidump folder and put them in the same directory on another windows computer (you will probably need to create the folder, as Windows only makes one on an as-needed basis). From there apps Jack mentioned can tell you a better idea of what the problem is.

In your case though, I don' see a future Without a re-install. If you can't boot into safe Windows or regular mode at all, there aren't a lot of options left.