This device has problems in Device Manager:ĪODDriver4.1 ROOT\LEGACY_AODDRIVER4.1\0000 This device is not present, is not working properly, or does not have all its drivers installed. Low free space can cause BSOD's - but the actual amount depends on the files being used by the system. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty). Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.įYI - there are many Windows Update errors in the WER section of the MSINFO32 report.Ĭ: drive only has about 1.8% free space. Please visit Windows Update and get ALL available updates (it may take several trips to get them all). Most systems with SP1 have 350-400 or more. Only 289 Windows Update hotfixes installed.
As you can see, I'm behind in my work here also. I didn't get any messages so I assume everything went okay.Īre the programs I have running in the background relevant? I have run Windows Memory Diagnostic, and when I came back it was finished and had booted. I assumed that despite the settings being classed as "overclocked" on the motherboard, the RAM itself is not overclocked, so I would not have any issues. Overclocked motherboard side, set to the specific settings specified here I did this once before and this didn't happen though.ĪMD FX-8350 Eight Core Black Edition 4.0 GHzĢx4 GB G.Skill Ripjaws X 2133 MHz F3-17000CL11D-8GBXL I imported 10 or so songs as different tracks, and accidentally hit play and they all started to play on top of each other for one second before it crashed with "MEMORY_MANAGEMENT". I occasionally get a random "MEMORY_MANAGEMENT" stop error, usually not coinciding with anything that I am doing, with the exception of today, when I was using Audacity. This is probably an over-posted question, but I think my problem is likely specific to my particular machine setup.