BSOD Memory_Managment

[Ramble012]

I had been having problems previously with this same system getting multiple BSOD everyday with varying messages on them. I was told after it was looked at that I had corruption in my registry and the easiest solution was to just re-install Windows. I went ahead and did that and even after a fresh install i'm still getting BSOD. I tried several re-installs and have been getting the same issues every time.

There doesn't seem to be any kind of pattern to it doing it, just happens here and there. It doesn't seem to be the same frequency it used to but it's still happening. The only message i've seen thus far is "Memory_Management". During this last re-install, all I did was install Windows 7 Ultimate x64, loaded the necessary, updated drivers for my graphics card and motherboard and just left it, still got the blue screen.

Any help would be greatly appreciated.

 

[koolkat77]

Your msinfo32 file is corrupted

Please upload your msinfo32.nfo file. To get this:

• Click on the Start rb:
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

 

[Ramble012]

Ok, here it is.

Thank you.

 

[koolkat77]

Still corrupted

 

[Ramble012]

Do you have any insight on what is going on? I'm looking for anything at this point, it's just driving me crazy. I'm doing a fresh install, installing updated drivers and it just keeps happening. I've tried using different install disks, I switched out the cd drive just in case. I just don't get what's going on.

 

[koolkat77]

Seeing your bug check:

STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel

You can start with checking your ram, BSOD Index
Run memtest86+ on each stick for 8 passes preferably overnight http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Tell me:

1. What antivirus are you using?
2. Are you overclocking any hardware?
3. Do you have programs like alchohol/daemon tools installed on your comp?

Let us know

 

[Ramble012]

I don't have any anti-virus on here since the last install but I was running that free one called "Avira" I think was the name. I was running that before the first set of blue screens started happening.

I was overclocking my processor and my RAM but I'm not anymore since the last install. I reset my BIOS back to defaults so everything is running default right now.

I don't have any crazy programs on here since the last install. The only thing I put on here was I think yahoo messenger and google chrome for web browsing. I haven't gone onto any crazy websites or porn (harhar) I know it's just my word on it but I've specifically not done anything crazy on the PC so as to eliminate the possibility of what I might have been doing previously.

I'm going to get started on the Memtest here shortly. Thank you for your help!

 

[koolkat77]

Lol okay.

Overclocking is not always safe..recheck & restore your clocks back to default.
Uninstall Avira and keep Microsoft Security Essentials - Free Antivirus for Windows instead..It's free and known to be the most compatible antivirus with windows 7.

Will be waiting for the memtest results.

 

[centaur78]

Your system is running hot....

The temps prior to a reboot was caused by high temp 379K or 105.85deg C...

Suggest you clean your CPU fans and Graphic fans...

We will wait for the memtest results as well.

 

[Ramble012]

Update:

I initially ran the memtest with both sticks of ram in and was immediately getting errors so I took one stick out and placed the other stick in slot 1 per the mobo's manual. Let stick 1 run 7 pass through's and no issues. Put in stick 2 to slot 1 and ran memtest and it immediately started having errors. So I believe I found the culprit.

That's odd about the temperature... I just cleaned all of the fans last week and the case is a HAF 922 and I have three 200mm fans along with the 120mm rear fan on it and everything appeared to be fine the last time I had checked the temp.

 

[centaur78]

Well that's the critical temperature that happened a few seconds before the reboot..... it not the kind of temp you see during normal operation unless there are other problems...

 

[Ramble012]

Being that I have already cleaned off all of my fans and graphics card and i'm running a rather large heat sink with its own fan (Hyper 212 Evo) and all of the fans appear to be functioning properly do you have any idea on what could have caused something like that? Would the faulty RAM stick be capable of doing something like that to the system?

 

[centaur78]

This kind of temps usually occurs when the processor is locked up or when it get into a never ending loop thereby increasing the temp above the critical temp designed for the MB .... and yes this lockup can be caused by a faulty RAM stick,....

 

[Ramble012]

Ok that makes me feel a little better lol. I'm pretty confident from what I've seen that the main issue is one faulty RAM stick and that's probably what was snowballing other issues with the PC. The PC is practically brand new, only built it a few months ago so if this is the only issue then I got out of it pretty clean.

Thank you for your responses and help!

 

[Dave76]

You should be monitoring your CPU core temps, if it continually overheats it can damage the CPU.

Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Check that your CPU cooler is firmly attached, you shouldn't be able to turn it.
Be careful, if it's too tight it can cause overheating.

Can you fill in your system specs, add them into the 'My System Specs' in the lower left corner of any of your posts.
This info will help with BSoD analysis and hardware troubleshooting.

Use Speccy Free System information Utility to get the information.

Your CPU core temps maximum should be about 75°C, depending on which Intel CPU you have.