New
#71
Good news.
What PSU did you get?
Thanks for the update and let us know if it's stable.
This thread will help others with similar issues.
Good news.
What PSU did you get?
Thanks for the update and let us know if it's stable.
This thread will help others with similar issues.
No problems so far, I ran the PSU test in OCCT just for giggles. Dave, perhaps you can tell me if it looks any better.
The voltage graphs are only slightly better that the previous ones, it's still possible the new PSU will help stability.
The bad news is the cause of the voltage fluctuations may be the motherboard.
Let us know the system status.
I'll keep you posted. So far, so good, no BSOD or odd behavior since install. I'll post if/when I get BSODs. thanks for looking at the graphs.
All was well from last Wednesday through this morning, 2x bsod. Dump attached. I guess it's the motherboard. Both were BAD_POOL_HEADER while using IE, not doing anything taxing, quite soon <5 minutes after start up
Last edited by badkarma11; 14 Jan 2013 at 09:42. Reason: additional info
Examples for Svchost.exe services are: "Automatic Updates", "Windows Firewall", "Plug and Play", "Fax Service", "Windows Themes" and many more.Code:STOP 0x00000019: BAD_POOL_HEADER Usual causes: Device driver, memory, external device drivers Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb ) BUGCHECK_STR: 0x19_3 PROCESS_NAME: svchost.exe PROCESS_NAME(dump #2): MsMpEng.exe LOCK_ADDRESS: fffff800032e1b80 -- (!locks fffff800032e1b80) WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. PNP_TRIAGE: Lock address : 0xfffff800032e1b80 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+cbb
MsMpEng.exe is a core process of Windows Defender.
Memory corruption is a likely cause.
This can also be caused by a third party driver.
As you mentioned, this type of crash can be caused by the motherboard.
Have you installed any new software or hardware recently?
Run memtest86+ again, all RAM cards installed and for 7 full passes, best to run overnight.
Let us know the results.
no new anything, I've memtested in every conceivable configuration. Must be mobo, probably fried something in the high heat environment it used to live in or it's just been marginal since day one. If I ever replace the mobo (won't be any time soon) I'll post back. Until then, the saga continues. I'll mark it solved and say the ultimate cause was mobo since we've done everything else. Thanks for looking at it, Dave.