Random BSOD

[Slartybart]

Mobo: M4A89GTD PRO/USB3
Specs
Downloads
CPU support list (can't tell sku from your specs)

Phenom IIX4 955 (HDX955FBK4DGI),3.2GHz,125W,rev.C2,SocketAM3,Quad-Core
Phenom IIX4 955 (HDX955FBK4DGM),3.2GHz,125W,rev.C3,SocketAM3,Quad-Core
Phenom IIX4 955 (HDZ955FBK4DGI),3.2GHz,125W,rev.C2,SocketAM3,Quad-Core
Phenom IIX4 955 (HDZ955FBK4DGM),3.2GHz,125W,rev.C3,SocketAM3,Quad-Core
​

Informational post only, not suggesting action to be taken.

 

[mp1cass0]

Thanks! Actually was there this morning, finishing up all downloads for drivers!

 

[Slartybart]

You're welcome. Wish I could be of more help, but other folks know more about these issues than I do. You definitely know more about this than I do, so I can post information stuff that might help resolve the issue =:>

There are a lot of updates there. Take all the time you need to make sure your system is up to date. Hopefully, the good folks here will be able to help you sort out this issue.

How long ago did you build the system, are components still covered under a return policy, if it comes to that?

Good luck
Bill

....and I'm out

 

[Layback Bear]

Some suggestions.
1. Remove all toys and gadgets from the computer except mouse and keyboard and keep them removed until the problem is fixed. Only have the hard drive with the operating system hooked up. We need to know that the basic computer is working properly before going any farther.
2. Remove all programs except MSE and keep them removed until the problem is fixed.
3. Keep all bios settings to default until problem is fixed.
4. Do memory test on all slots and report findings. My understanding is slots 1 and 3 are okay. Complete test on slots 2 and 4 and report findings. You must test all ram modules and all ram slots. The two ram sticks that worked in slots 1 and 3 test in slots 2 and 4. Then test the other 2 sticks in slots 1 and 2. We must know that all ram sticks and all ram slots pass.
5. Don't be doing a bunch of other things to the computer that haven't been asked. If you do other things these kind folk trying to help you will be going in circles along with you.
6. Report the findings of every test in detail.
7. Double check to make sure every connection is made and made properly to all hardware. Check again that ALL hardware is compatible with each other.
------------------------
These are basic steps to any new computer having problems.

 

[mp1cass0]

Some suggestions.
1. Remove all toys and gadgets from the computer except mouse and keyboard and keep them removed until the problem is fixed. Only have the hard drive with the operating system hooked up. We need to know that the basic computer is working properly before going any farther.

Stays that way. Will reinstall today only with updates installed.

2. Remove all programs except MSE and keep them removed until the problem is fixed.

Will do a fresh install again today, just to make sure.

3. Keep all bios settings to default until problem is fixed.

Again, that is the norm, other than fixing voltages/timings for RAM.

4. Do memory test on all slots and report findings. My understanding is slots 1 and 3 are okay. Complete test on slots 2 and 4 and report findings. You must test all ram modules and all ram slots. The two ram sticks that worked in slots 1 and 3 test in slots 2 and 4. Then test the other 2 sticks in slots 1 and 2. We must know that all ram sticks and all ram slots pass.

In the plans today...ended up doing a fresh install last night so never moved the modules.

5. Don't be doing a bunch of other things to the computer that haven't been asked. If you do other things these kind folk trying to help you will be going in circles along with you.

Understood and only do what is asked.

6. Report the findings of every test in detail.
7. Double check to make sure every connection is made and made properly to all hardware. Check again that ALL hardware is compatible with each other.

First thing I did when BSOD started.

------------------------
These are basic steps to any new computer having problems.

Thanks...replied individually to each statement.

 

[gregrocker]

The method Layback mentions above to isolate and test RAM sticks and slots is described fully in Jonathan's tutorial RAM - Test with Memtest86+.

Since you've described several reinstalls but also mentioned driver changeouts my focus will be on getting a baseline perfect Clean Reinstall - Factory OEM Windows 7 following the best practices for the OS, so you can finally eliminate software as possible cause.

For example, Win7 is driver-complete in the installer and quickly updated via optional Windows Updates, requiring no driver change-outs unless performance points to one or it is missing. This development for Win7 is so complete that in Win8 there is no user interaction with drivers at all.

So heed the driver steps closely, as well as the tools and methods which work best with Win7 based on countless thousands of installs we've helped with here. If a baseline perfect reinstall doesn't solve the problem then you'll know it's hardware.

 

[mp1cass0]

Clean install was done last night to rule out hardware issues. Only programs ran are the same ones used since computer 1st assembled July 2011, offering no problems until 2 months ago. Bad memory stick followed by a HD crash. Things have not been right since.

Installs have been done with a boot able disk, formatting the drive to make sure no remnants remain. However, I did install programs so will be doing a clean install with no additions, verifying if it is a hardware issue or compatibility problem. Once up, going to run memteat on slots 2&4 to eliminate any problems.

I appreciate all input/comments and will post what I have done/find.

 

[gregrocker]

Since you're going to install again in addition to following the steps in tutorial closely, I'd wipe the HD first with Diskpart Clean Command to clear the boot sector of possibly interfering code. DISKPART At PC Startup

This combination assures a perfect reinstall on a clean slate.

 

[mp1cass0]

Thanks! Re-downloading Windows 7 to make sure nothing corrupted and then with go through the process listed. Probably will not be finished with everything before tomorrow evening at the latest.

 

[Layback Bear]

That okay mp1cass0. Take your time so you don't miss any steps. All this is done step at a time. We will be here when your are ready for us.

 

[mp1cass0]

Thanks! Have not had to do such exhaustive testing before so a little anxious but rushing gets me nowhere!

With post when I know more!

 

[Dave76]

Your CPUZ file and the MSinfo32 file are saying you only have 3 CPU cores.
Go to Task Manager > Resource Monitor and check the CPU tab, make sure all four cores are recognized.

It also shows your RAM running at 800MHz (actual 1600MHz), this is a known problem for AMD CPUs, set the RAM to run at maximum 667MHz (1333MHz).
This has been known to stop AMD systems from constant BSoDs.
Even though your RAM passed memtest86+, this may still be causing problems.
Once the system is stable you can try and OC the RAM.
If it's stable at 1333MHz then you know the cause.

Also noticed the RAM has XMP settings, this is a feature for Intel system RAM, which may or may not run very well on an AMD system.
We might need to come back to this later.

If you want to change your BIOS from IDE to AHCI/RAID, it's best to do before you install the OS. There is a way to change it with the OS installed, best to leave this until the system is stable.

Your first crash dump is Driver Verifier enabled, and blames RAM which may be a result of the RAM frequency issue.
If you haven't already, disable Driver Verifier.
Driver Verifier - Enable and Disable
A PFN_LIST_CORRUPT (4e) is usually due to corrupt RAM, again the frequency issue.

From first dump files posted:

STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes:  Device driver, ?memory 
Probably caused by : [COLOR="Red"]memory_corruption [/COLOR]( nt!MiUnlinkPageFromLockedList+8d )
DEFAULT_BUCKET_ID:  [COLOR="red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x4E_2_VRF_nt!MiUnlinkPageFromLockedList+8d
--------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, [U]Memory[/U], 3rd party remote control,
This is a very common bugcheck.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  [COLOR="red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_nt!ExFreePoolWithTag+43
--------------------------------------------------------------------------------------------------------------------------------
Same as above, except:
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
--------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 
Usual causes:  Device driver, ?[U]Memory[/U]
Probably caused by : [COLOR="red"]memory_corruption[/COLOR] ( nt!MmFreeSpecialPool+374 )
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98018c90ee0, address trying to free
Arg2: fffff98018c90ff8, address where bits are corrupted
Arg3: 0000000000f30118, (reserved)
Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
DEFAULT_BUCKET_ID:  [COLOR="Red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
IMAGE_NAME:  [U]memory_corruption[/U]

Looks like a memory issue.

Second dump files:

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, [U]memory[/U], kernel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+20fc0

Most important is to check the CPU core issue, this may be indicating an issue with the CPU, bent pins or faulty CPU.
Next is change the RAM frequency to 1333MHz for testing.
Download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

 

[mp1cass0]

Go to Task Manager > Resource Monitor and check the CPU tab, make sure all four cores are recognized.

2nd core was turned off in BIOS. Resource monitor showing all 4 running.

It also shows your RAM running at 800MHz (actual 1600MHz), this is a known problem for AMD CPUs, set the RAM to run at maximum 667MHz (1333MHz).
This has been known to stop AMD systems from constant BSoDs.
Even though your RAM passed memtest86+, this may still be causing problems.
Once the system is stable you can try and OC the RAM.
If it's stable at 1333MHz then you know the cause.

Remembered reading about this when putting the system together and apparently forgot to change it. Thanks for pointing this out.

Also noticed the RAM has XMP settings, this is a feature for Intel system RAM, which may or may not run very well on an AMD system.
We might need to come back to this later.

Will look in BIOS and turn it off when in there.

If you want to change your BIOS from IDE to AHCI/RAID, it's best to do before you install the OS. There is a way to change it with the OS installed, best to leave this until the system is stable.

Changed it in the BIOS before installing Windows on original build but gave me problems so went back to IDE. Found out a few months later that my HD was on it's way out and never went back to change. Not really concerned one way or another as I have noticed no major benefit to having AHCI on a single drive.

Your first crash dump is Driver Verifier enabled, and blames RAM which may be a result of the RAM frequency issue.
If you haven't already, disable Driver Verifier.

Done.

Most important is to check the CPU core issue, this may be indicating an issue with the CPU, bent pins or faulty CPU.

Ran HotCPU tester PRO 2x's before coming on here looking for help. No issues were noted. CPU core "issue" has been fixed, as BIOS had 2nd core turned off.

Next is change the RAM frequency to 1333MHz for testing.

Done.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Only one I changed is the RAM - set at 1.5v. Do not see anything that says CPU or CPU integrated memory controller, with regards to voltages. Is it under another name?

Response in blue.

 

[mp1cass0]

Update - did a diskpart/cleanall, eliminated all partitions, installed Windows, installed all drivers via Windows, except my network drivers (from MB CD and checked for update once online). Installed Abobe Reader, Java, MSE, and Malwarebytes, all listed on "Clean Install - Factory OEM". According to Windows Update, all files have been installed.

Question - I have an Epson Artisan 837 printer that I use for work (I work from home). Installed via Windows update but then clicked on "update drivers" from Start menu link (downloaded from Epson). Should I use System Restore and go back to a time before that? to make sure nothing other than Windows "approved" drivers were installed? Or see how things go, keeping it in the back of my head?

 

[Slartybart]

I wouldn't worry about the printer driver.
Run your machine as normal and focus on the BSOD- report any new occurrences

 

[marsmimar]

I wouldn't worry about the printer driver.
Run your machine as normal and focus on the BSOD- report any new occurrences

^^^What Bill said.

 

[gregrocker]

Just guard both places in msconfig per the tutorial to make sure nothing Epson sneaks in, unless you need scan function to show up on your desktop when you initiate it on printer. In that case if it doesn't I would test enable each Epson listing in msconfig. If that doesn't suffice you may need to do a Custom install of latest Printer software package leaving out all the unneeded (shopping, update) choices.

 

[mp1cass0]

This is what my msconfig looks like for startup.

 

[gregrocker]

Very clean. My compliments.

You didn't say if your Epson requires a scan initiated on the printer to show up on PC desktop. If not you likely don't need that listing unless you lose some other functionality without it.

How about a screenie of Services tab after Hiding All MS Services? You're on a roll.

 

[mp1cass0]

Not at home at the moment but it was only 2. AMD external events utility and Adobe Acrobat updater. Went into Adobe Acrobat reader, turned off automatic updates, and disabled AMD through services.

I usually initiate scan from printer so will switch Epson to manual and see how if that works.