Solved Random BSOD after system maintenance

[Dave76]

The Western Digital Lifeguard tests are for the hard drive, not the SSD.
Are you using the Samsung SSD Magician tool?

I recommend to run memtest86+ again, for 7 full passes with all four cards installed.
If it passes or fails, then go to your steps 1&2.

If memtest86+ passes with all RAM cards installed and/or two RAM cards installed. No need to run the test with one card at a time, for now anyway.

Let us know the test results.

 

[badkarma11]

The Western Digital Lifeguard tests are for the hard drive, not the SSD.
Are you using the Samsung SSD Magician tool?

I recommend to run memtest86+ again, for 7 full passes with all four cards installed.
If it passes or fails, then go to your steps 1&2.

If memtest86+ passes with all RAM cards installed and/or two RAM cards installed. No need to run the test with one card at a time, for now anyway.

Let us know the test results.

I am using it SSD magician to optimize/benchmark from time to time. It was never clear to me if I was supposed to always have it running in the task bar so I haven't been.

OK, MemTest for 7 passes. Regardless of result, do 1 and 2, yes?

 

[badkarma11]

I downloaded the Western Digital Lifeguard, but after install it won't run. Tryed twice so I'm bailing on it. Memtest results to follow

 

[Dave76]

Does Western Digital Lifeguard startup?
If it starts up but won't run, that's not good news for your HDD.

Try SeaTools, it will run on any HDD.
Download and run Seatools on your HDD.
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.

Samsung SSD Magician tool manual

NOTE: Windows 7 supports TRIM natively, so this feature is less
necessary for Windows 7 Users. Those using Windows XP, which does
not support TRIM, should run this feature regularly to keep their SSD in
top shape. Of course, Windows 7 users can use Performance
Optimization as well if they wish to force Garbage Collection and TRIM to
run at a particular time rather than in the background.

Seems to be similar to the Intel ToolBox, might not be necessary but can't hurt using it.
I would run Performance Optimization once a week.
No need to have it running all the time, just open it when needed.

Even the best memory testing tool (memtest86+) won't always catch RAM errors, if there are indications that you have a RAM issue then you need to try troubleshooting steps anyway.

Regardless of result, do 1 and 2, yes?

Yes

Let us know the results.

 

[badkarma11]

I installed WD on my D drive (500GB drive where all my stuff that's not on the SSD is stored, been the D drive since I got the SSD, my old C drive is also 500GB but is empty). At the end of the installation it said 'Run WD Lifeguard?'. I left the box checked and clicked finish on the install. Threw an error immediately (I forget the text). I uninstalled it and tried again, same result. I'll try the Seatools thing. Thanks for the info on the SSD Magician, that's what I thought and I've been optimizing weekly and keeping at least 30GB available at all time (I don't install much to the SSD). memtest is running still, 12 hours and fininshing up pass #7 when I left for work. We'll see on that. I did reseat my RAM last night and swapped the matched pairs just for laughs. No BSOD after, I played BF3 until it crashed (just the program) and started Memtest after that. Will report back with results of the Seatools tonight (assuming it works) and then I'll start playing 'swap the memory'. Thanks for sticking with me

 

[badkarma11]

Update: I have run Memtest for 10+ passes, no errors. I installed the SeaTools and have done the short drive self test, the SMART check and the short generic on both non-SSD drives. All passed. Is the next recommended step the long generic? I can run that later (supposedly it takes a while). I'm not going to play 'swap the RAM' until/unless I complete the next recommended HDD check AND it BSODs again.

 

[Dave76]

Good news on the memtest86+ test.

You need to run the SeaTools Long Drive Self Test on both drives.
It will take longer than the short tests.

Let's look at the RAM settings.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs. Post one SPD tab for each brand of RAM.
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 NB voltages are.

We can adjust the RAM settings just to be sure it's not causing the problems.

 

[badkarma11]

Ran the long SeaTools test, no errors
CPU-Z images uploaded. I will edit with BIOS values shortly
EDIT:
This is what I get out of the BIOS...
CORE VID 1.2250v
CURRENT CORE 4
CURRENT CORE VID 1.248v
DRAM 1.52v
NB 1.09v
VTT FSB 1.20v
ICA 1.65v
Hopefully that's what you're looking for.

 

[badkarma11]

More dumps, 1 this AM, 1 just now. *sigh*

 

[Dave76]

Good news on the HDD tests.

Post a snip of the CPUZ SPD tab for the PNY RAM, in the top left corner select another slot from the drop box.

For now, bump the DRAM voltage to 1.550v and the NB voltage to 1.20v.

Your last crashes.

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
PROCESS_NAME:  bf3.exe
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+356c3
FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356c3
------------------------------------------------------------------------------
STOP 0x00000019: BAD_POOL_HEADER
Usual causes:  Device driver
PROCESS_NAME:  explorer.exe
FOLLOWUP_NAME:  Pool_corruption
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+118b

From System Event Log

Event[16587]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-09-18T08:06:24.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: GhengisSSD
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffa9b187fb018, 0x0000000000000000, 0xfffff800031dcc24, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091812-9874-01.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

This is a new crash, you haven't had before, it confirms a hardware issue.
If you're still using MSE, it's not likely causing any problems.
Device drivers have been checked.

Event[16961]:
  Log Name: System
  Source: Application Popup
  Date: 2012-09-18T18:36:03.256
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: GhengisSSD
  Description: 
Application popup:  : \SystemRoot\system32\DRIVERS\nvlddmkm.sys failed to load

Your nVidia driver again.

Event[16963]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2012-09-18T18:36:03.272
  Event ID: 219
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: GhengisSSD
  Description: 
The driver \Driver\ctaud2k failed to load for the device PCI\VEN_1102&DEV_0005&SUBSYS_00231102&REV_00\4&3c1f64e&0&00F0.

ctaud2k - Creative Audio Driver (WDM)
Check for an update for this driver.

Event[16969]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-09-18T18:36:06.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: GhengisSSD
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff88006fcfb88, 0xfffff88006fcf3e0, 0xfffff880012ea555). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091812-8970-01.

STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Two of these crashes.
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver

Event[19007]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-09-20T19:11:08.000
  Event ID: 2001
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: GhengisSSD
  Description: 
Microsoft Antimalware has encountered an error trying to update signatures.
 	New Signature Version: 
 	Previous Signature Version: 1.137.6.0
 	Update Source: Microsoft Update Server
 	Update Stage: Search
 	Source Path: http://www.microsoft.com
 	Signature Type: AntiVirus
 	Update Type: Full
 	User: NT AUTHORITY\SYSTEM
 	Current Engine Version: 
 	Previous Engine Version: 1.1.8800.0
 	Error code: 0x8024402c
 	Error description: An unexpected problem occurred while checking for updates. For information on installing or troubleshooting updates, see Help and Support.

Run a full scan with MSE and MBAM, SuperAntiSpyware, as before.

 

[badkarma11]

Voltages changed, snip posted, I'm looking for a newer CTAUD2K and I'll virus sweep again. Thanks Dave
EDIT: BSOD bad_pool_header right after I posted this. I had just started an MBAM scan.

 

[badkarma11]

Dave76,
This rig has a long and checkered history. I originally had another rig (home built) with a dual core CPU and an 8800 GTX video card, running Vista Ultimate, 4GB of RAM, same sound card, a couple of HDDs (a 320 and something else..). I wanted to upgrade this with a quad core CPU and a better video card as a relatively cheap way to keep it useful for another couple of years. I bought the processor and video card. CPU came first, I installed it, no problem. Video card came and GASP! it was so wide that it covered 2 PCI slots (needed 3 because at the time I had a wireless card plugged in too). So much for cheap and easy... OK, so I need a mobo that has more slots, or at least the video slot all by itself. I bought a new mobo, not realizing that it took DDR3 RAM (I had DDR2 in the other one). Put it together, realized my mistake and swore loudly. Bought the Crucial RAM online, it came, I plugged it in, wouldn't even boot. Turns out that particular mobo HAD to have double sided RAM. I went to 2 Staples stores to find 2 sticks of double sided RAM (the PNY). Plugged it in, the thing booted. OK. Ran it for a few weeks, had some issues so I decided to just build a new rig so I could recomission the old one for the kids. Bought a case, a power supply, the MSI mobo, a 500GB HDD and Windows 7 Ultimate. Built the new rig, put in all the RAM and then the fun began.
I have been building computers since the early '90s and started using Windows instead of DOS when Windows 95 came out. I had never, in all that time, encountered a BSOD on my home machine(s). Win95, Win98, XP, Vista, never a BSOD. Windows 7, I've been on and off in BSOD hell since. It took a couple of months to get the rig stable enough to reliably use (basically I'm a gamer). Finally settled down to a BSOD about once a month, which I could live with. Then, I installed the SSD (see beginning of thread) and it's been BSOD hell all over again. We've been 'round and 'round with all the troubleshooting listed here, and in other posts. I'm thinking one of a couple of things. 1. The mobo is marginal for this setup and the SSD was the 'last straw'. I might just bail on the SSD until I can build a new rig (at least upgrade the processor and mobo) perhaps that will shut the thing up. 2. Despite the MemTest results, I am suspicious of the PNY RAM and might try taking it out just to see. Whatever the problems have been, hardware is always lurking in the background, from a dump/error analysis point of view. Thoughts?

 

[Dave76]

Any small fault (intermittent is the worst) on the main components can be very difficult to track down.
The easiest way (after the usual testing) is to swap out components but, not always possible.
A small fault in two or more components can be exasperating at best.

Good RAM info on the SPD tabs, unusual to get two different RAM brands with the exact same SPD specs.
Crucial (Micron) is a RAM manufacturer, they probably sold this to PNY.

The low voltage RAM may not be stable in this motherboard.
For testing let's bump the DRAM voltage to 1.600v and the NB voltage to 1.300v.

I wouldn't think the SSD is causing any stress on your system, should actually lower the system power load.
It might be stressing the RAM due to the speed of the SSD.
Is the Crucial RAM you are using now single or double sided?
This is important due to RAM card chip size, double sided has more, smaller sized chips. The NB can only handle the smaller memory chips.
This may be a factor, just for testing (single or double) pull the Crucial RAM and let's see if it is more stable.
The PNY RAM cards should be in slots 1&3.
Then swap the PNY for the Crucial, if the Crucial is double sided.

Have you Clean installed Win7?
If yes, how many times and when was the last time.

A quick search shows a lot of RAM issues with this motherboard, seems to be a bit touchy with settings.
There are a couple of approaches to check this, bump DRAM and NB voltages and/or loosen the frequency and timings.
Is your DRAM timing Mode on auto (SPD settings enabled)?
Motherboard faults are the hardest to find, usually need to confirm every other component is functioning correctly, which can be 100% confirmed by testing your other components on another motherboard.

Your PSU is made by Delta Electronics and gives max 12v load of 540W.
PSU REVIEW DATABASE
How long have you had this?
They do degrade with time.
The above link is a good reference, I prefer PSU OEM Seasonic, they have an excellent reputation and track record.
Antec is also a well respected brand, as is Corsair but I still had a Corsair PSU fail in less than a year.
When a PSU fails it can be a slow drawn out process causing all kinds of errors/faults/crashes, in the worst case it can take other components out with it.

GPUs are another huge variable, the GTS 450 series does have a reputation of not being the most stable nVidia product.
Again, swapping to another GPU for testing, or putting your GPU in another system, is the easiest way to confirm.

It's a good thing we like computers, they can be a lot of fun and sometimes not.

 

[badkarma11]

Great response, Dave. Thank you.
I detest intermittant problems, computer, software or automotive. I'm a programmer by trade and I hate chasing bugs that I can't reproduce on demand.

I bumped the DRAM voltage to 1.60. The NB is now at 1.22 (the mobo will let me take it higher, but it says 'Not Recommended') If you think it's OK, I'll kick it higher.

The Crucial is not double sided. The DRAM timing is on Auto, currently. The PSU is the same age as everything else. I bought everything except one of the HDDs and the SSD at the same time. That was in October 2010 (more or less). I guess I'll play along until the next BSOD and then take out the Crucial and see. I don't have another computer with Win7 on it so I'd be swapping less capable components in (G
PU for example). Might or might not be a fair test. I'll burn that bridge when I get there I guess. Last clean install of windows was a couple of weeks ago after I got the SSD and cloned my C drive to it. I initially thought that was the problem, and a clean install did cure a couple of other non BSOD issues. I think I'll clone my SSD to the old C drive and have that as a back up troubleshooting step.

I will ride this into the ground, I hate to lose . Meanwhile, one of the other two computers in the house just ate it's C drive so I'll have to rebuild that out of spit and duct tape. It's an old Gateway (8 years at least) with it's original HDD as the C drive and a 240 as the D (not original, but still old). Ugh.
Thanks for riding along with me, if nothing else I'm learning stuff. Never too old for that (I'm 50). At least my 'puter let me play games for a while last night (1 BSOD).

 

[Dave76]

You can leave the NB at 1.220v.

Let me know when you take out the Crucial RAM, I think that will be a good test.
RAM issues can be intermittent, and we hate that.

Post the crash files if you get another one.

 

[badkarma11]

Quick update, only 3 BSOD all weekend (not bad) and BF3 crashes didn't result in BSODs like they ususally do. I had the case open all last week after I reseated everything and I buttoned it back up before I read your last post (I wanted to make sure that my cooling wasn't being lost by the open case). According to SpeedFan, cooling got better after I closed the case as I expected. Nothing more than 60C under load so that's good. I'm going to run it for a week and then post all the BSODs (unless it really gets out of hand). Previously when I've been in BSOD hell, I got the system to a point where it was liveable and the BSODs sort of petered out to once a month or so. the last voltage change seemed to make a difference. Anyway, I'll post more when there is more.

 

[Dave76]

Good update.

If your still getting crashes, pull the Crucial ram, for testing.
At least you'll know the source.
There are a couple more things we can do with the RAM to try and stabilize it.

Post the crash files when you can.

Let us know how it's going.

 

[badkarma11]

I've had 3 BSODs since my last post, all attributable to either known BF3 crash issues and a corrupted install of Steam. I'm not going to post them. The machine is stable otherwise. I'm going to call this one 'solved' because the only problems I have are sort of self inflicted. Thanks Arc and Dave76 for all of your help and guidance. See you on the forums

 

[Dave76]

Thanks for the update.

Let us know if you have any more questions.

 

[badkarma11]

Will do, thanks again!