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 downloaded the Western Digital Lifeguard, but after install it won't run. Tryed twice so I'm bailing on it. Memtest results to follow
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
Seems to be similar to the Intel ToolBox, might not be necessary but can't hurt using it.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.
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.
YesRegardless of result, do 1 and 2, yes?
Let us know the results.
Last edited by Dave76; 18 Sep 2012 at 23:48.
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 :)
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.
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.
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.
Last edited by badkarma11; 20 Sep 2012 at 18:45. Reason: additional information
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.
From System Event LogCode: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
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREACode: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.
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.
Your nVidia driver again.Code: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
ctaud2k - Creative Audio Driver (WDM)Code: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.
Check for an update for this driver.
STOP 0x00000024: NTFS_FILE_SYSTEMCode: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.
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
Run a full scan with MSE and MBAM, SuperAntiSpyware, as before.Code: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.
Last edited by Dave76; 21 Sep 2012 at 05:45.
Quote