Solved New SSD causing issues

[iamcami]

Hello,

I have recently installed a solid state hard drive into my laptop and since doing so I have experienced numerous system crashes. When this happens an error screen appears, but there is not enough time to read the content before it restarts and boot options kick in (ie safe mode etc). The crash seemed to occur when I was browsing the net and has become more frequent and now has crashed minutes after start up. It seemed to be prompted by any simple action like closing dialogue boxes, whereas initially it occurred only infrequently. I am confident that the root cause has to do with the Kingston SSD as my old hard drive works ok (so far). Please help

Here's the event logs etc from windows.

Kernel 41 1 - Pastebin.com

Detailed - Pastebin.com

one more - Pastebin.com

or

http://dl.dropbox.com/u/64451561/blah.txt

http://dl.dropbox.com/u/64451561/blah3.xml

http://dl.dropbox.com/u/52986617/another.txt

When I first installed the HDD and Windows, I ran the Windows experience thing and it rated the HDD at 7.8 out of 7.9 which made me think I had no reason to mess around with settings etc.

Once I noticed these issues I did some research and saw that I should have updated the SSD's firmware which I attempted to do and think I did successfully but it had no effect.

Hope you can help me.

 

[HammerHead]

Crystal Disk

Down load Crystal Disk and run it. It will show you the condition of the disk.

CrystalDiskInfo - Software - Crystal Dew World

 

[windude99]

You need to disable the automatic restart function when your system crashes. To do this, go to start and type in (without quotes) " view advanced system settings " and press enter. Go down to the section titled: Startup and Recovery" and click on settings. Then, find the section titled System failure and uncheck the checkbox titled "Automatically restart." Now, you can tell us what the bluescreen says (error number and message)

 

[iamcami]

Forgot to mention it's brand new. About 1 week old.

http://dl.dropbox.com/u/52986617/ssd.JPG

EDIT: OK will do that. I'd taken it out and put it in an enclosure to regain use of the laptop.

EDIT: OK Here is the blue screen.
http://dl.dropbox.com/u/52986617/IMAG0127.jpg

 

[iamcami]

bump

 

[Total]

bump

have you tried memtest ? Memtest86+ - Advanced Memory Diagnostic Tool

 

[karlsnooks]

iamcami,

First forget ever bumping in this forum. Leaves a bad taste in the mouth of us regulars.

We all have very active lives. This a no-pay avocation. When we can, we get to the posts.

Now, your problem has zero to do with the fact that you are now using a SSD.

Presently, we must fire a few shots at your problem and hope that we hit the target soon.

A system must be 100% clean of malware before anything is attempted.

With that said: follow this procedure perfectly. When finished, attach the log files to your next post. I'm going to jump ahead and show you how to Post/attach a file here in SevenForums:

Post a File or Screenshot in Seven Forums

================================================
now the procedure:

HOW TO USE WINDOWS DEFENDER OFFLINE ON A USB STICK
Windows Defender Offline
· is a free standalone, bootable malware and virus remover from Microsoft.
· performs an offline scan of an infected PC to remove viruses, rootkits and other advanced malware.

Download Windows Defender Offline (about 764 kB)

You will have the choice of downloading the 32bit version (x86) or the 64 bit version (x64).
The link will help you determine whether you are running a 32 bit version or 64 bit version of Windows

NOTE!! You can download and prepare a 32 bit version using a 64 bit version of Windows
NOTE!! You can download and prepare a 64 bit version using a 32bit version of Windows.

You run the 32 bit version on a 32 bit version of Windows.
You run the 64 bit version on a 64 bit version of Windows.

The 32 bit download file name is: mssstool32.exe
The 64 bit download file name is: mssstool64.exe

For the curious, this program was originally name Microsoft Standalone System Sweeper.


INSTALLATION:
You will need an Internet Connection.
Insert 512 mB (Microsoft’s 256 mB is no longer accurate) or larger USB stick into a usb port.
Run the downloaded program--mssstool64.exe or mssstool32.exe
NEXT button
Choose the option On a USB flash drive that is not password protected
NEXT button
NEXT button
.
The install program will format the usb stick using the NTFS format.
The install program will download about 210 mB.
The install program will name the USB stick WDO_Media32 or WDO_Media64
The WDO_Media32 usb stick will have used space of 255 mB (268,140,544 bytes)
The WDO_Media64 usb stick will have used space of 282 mB (296,165,376 bytes)
You can expect the number of mB to increase as more malware appears.

UPDATE Windows Defender Offline USB stick:
· reinsert the usb stick
· run the installation program, mssstool64.exe or mssstool32.exe, again.
· the update will download about 66 mB (mssstool32.exe) and 68 mB (mssstool64.exe).

Since the malware database is sometimes updated several times in a day, always update before running.

PERFORM AN OFFLINE SCAN
Bootup your computer from the USB stick
Windows Defender Offline will automatically perform a quick scan.
After the quick scan finishes, Choose Full Scan
Select all of your drives

The initial, full scan can easily take several hours, but
Remember, your computer is being very thoroughly checked for all types of malware.


RESULTS OF THE SCAN
The results will be in 4 log files on your computer's disk in:
\Windows\Microsoft Antimalware\Support
Upload the four log files please.
=============================================

 

[iamcami]

Sorry, I only bumped it as I'd edited the previous post a few times, so was trying to let people know I'd gotten the information asked of me. Is double posting OK?

The laptop works with my old slow 5400rpm drive no problem. I hadn't erased it, so have now gone back to using it primarily.

Rather than run a bunch of scans, should I just go ahead and do a fresh windows install on the SSD?

And the RAM should be fine if I never have this problem unless I'm using the SSD? It's process of elimination right? ill try it anyway

Using the old HDD again. It's not shown me that blue screen in the past and it's not yet. Since I switched back earlier today.

 

[karlsnooks]

Follow the advice I gave.

There is never an excuse for bumping or double-posting.

 

[iamcami]

Sorry. Some sites allow it. That's why I didn't think it was a big deal. I'll check the rules.

Should I follow those steps with the SSD in the USB enclosure or in the laptop connected via SATA? The latter will probably be harder.

 

[karlsnooks]

Have a nice day.

 

[iamcami]

After reading through the steps to the end, I see that I will be booting off a USB stick. So having the SSD connected directly shouldn't be a problem.

Sorry I misunderstood.

EDIT: Did the Defender scan. It did a quick scan automatically and then I ran a full scan. Found nothing. Wouldn't expect it to as I only installed windows the other day.

Just after I copied the logs, within a few minutes, it did the error screen again. Gonna run mem test if I get the chance.

EDIT: Did memtest. It passed. Added pic. LOL It's upside down. But Iv got to sleep. It says "passed with no errors"

 

[Dave76]

What is the exact model of the Kingston SSD?
What firmware version did you upgrade to?
Just looked at your CrystalDisk info, it appears you have the updated firmware installed.
When did you install the firmware?

Did you install this firmware update?
SVP200S3 - Solid-State Drive SSDNow SVP200S3 Firmware Update

We have discovered a technical issue with our SVP200S3 SSD which could result in temporary drive disappearance during certain sleep modes or a rarely, randomly occurring BSOD. If you are experiencing these issues, Kingston strongly recommends that a firmware update be applied to your SVP200S3 drive.

If you are still having the crashes after the firmware update then upload the following files.
There is a known issue with SSDs that have the SandForce Processor, which yours has, the latest firmware update should fix it.

The known issue are exactly what you are having now, BSoD F4, crashes.
It is the equivalent of your SSD being disconnected while you are using it, Windows doesn't like that and will show you a blue screen.

Check that the SSD is firmly attached in your laptop.

We need more information, can you attach the files to your next post?
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

 

[iamcami]

Thanks that's a big coincidence. I will double check I'm on the latest FW. Updating the FW was one of the first things I did. Although I think the SSD was already on the latest firmware. But I'll try again, and looking at the instructions I didn't "run as admin"

Kingston 120GB V+200 SSD

I'll also follow the BSOD posting instructions if the FW update doesn't fix it this time.

EDIT: Hm well so far so good. Not convinced yet. I was pretty sure I did the FW update previously and I suspected it was already on the latest. But it hasnt crashed yet.

EDIT: at least another hour of usage here... could running the FW update as admin really have made the difference? seems to be better now and that's all I changed. even though the FW version didn't seem to change when I ran the update.

EDIT: Spoke too soon. It's still doing it.
Trying to run the BSOD report thing but it keeps crashing

EDIT: Still trying to run the BSOD dump results thing but for some reason it won't run that long with out crashing.
gonna remove daemon tools and the mentioned driver here http://www.sevenforums.com/crashes-...sod-after-changing-new-ssd-new-asus-mobo.html

EDIT: Finally got it done. Check the upload

 

[karlsnooks]

iamcami,
You need to follow the procedure in our BSOD forum for analysis of your dumps and for instructions on the info needed to analyze your BSODs.

 

[iamcami]

I will do so if I go that route.

I'm not trying to have a go at you karlsnooks, but you pointed out the rules regarding bumping/double posting.

I'd like to now point out this rule to you.
2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.

In regards to your post here in this thread. "Have a nice day." In response to my question.

And your post here http://www.sevenforums.com/general-...dows-explorer-not-responding.html#post1954001 "I wish you a good and pleasant day!" In response to that users question.

These comments in response to users questions aren't helpful at all.

I appreciate you taking time to help people here anyway. Just wanted to point that out.

 

[Dave76]

You have had 11 crashes today, 11 yesterday and 11 prior to that.

The repeating crashes are not included.

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been terminated.
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
------------------------------------------------------------------------------------------------------------------------------------------------
CRITICAL_OBJECT_TERMINATION (f4)
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe
------------------------------------------------------------------------------------------------------------------------------------------------
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by a bad block in the paging file or disk controller error.
DISK_HARDWARE_ERROR: There was error with disk hardware
PROCESS_NAME:  System
FOLLOWUP_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
------------------------------------------------------------------------------------------------------------------------------------------------
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by a bad block in the paging file or disk controller error.
DISK_HARDWARE_ERROR: There was error with disk hardware
PROCESS_NAME:  System
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+3717a
------------------------------------------------------------------------------------------------------------------------------------------------
These indicate possible problem drivers, they may be the result of the actual cause.
Unloaded modules:
fffff880`08385000 fffff880`08393000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`08393000 fffff880`0839f000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0839f000 fffff880`083aa000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
fffff880`083aa000 fffff880`083bd000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`01630000 fffff880`0163e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0163e000 fffff880`0164a000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0164a000 fffff880`01655000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
fffff880`01655000 fffff880`01668000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

This still looks like the known SandForce SSD issue, either the firmware update didn't fix it for you or there is another issue adding to the problem.
Since memory corruption is mentioned several time you should run memtest86+ again. Running it for 1 pass is not enough to rule out the RAM, run it for a minimum of 7 full passes. Best to run overnight.
This test runs without the OS and should exclude the SSD, testing only the RAM.

Have you upgraded your RAM?
Can you 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

Have you been checking your temperatures?
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.


Just to confirm, do you have any issues with the SSD removed and the HDD installed?
If no, this obviously points to the SSD.

The Unloaded modules include the AHCI/IDE drivers, which may be caused by the SSD issue, can you post the driver versions listed in your Device Manager?

Other possible driver conflicts:
Remove CPUZ 1.35 and install CPUZ 1.60.1

What power management setting are you using?
Control Panel> Power Options.
Could possibly be an issue returning from Sleep or Hibernation.
To test this, disable them and see if the crashes persist. This would still indicate a SSD issue.

Event logs Apps:

Event[3]:
  Log Name: Application
  Source: Microsoft-Windows-WMI
  Date: 2012-06-06T21:30:42.000
  Event ID: 10
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Richard-PC
  Description: 
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

May be caused by the SSD issue, check CPU temps to be sure.

EDIT:
Thanks to Golden for this suggestion.
Try doing a power cycle of the SSD.
Highly recommend this procedure.

 

[iamcami]

Thanks so much for all those suggestions! I really appreciate it.

I will work my way through those ASAP.

To answer what I can off the top of my head,

I've not upgraded the RAM. It came (direct from HP) with 3GB, a 2GB stick and a 1GB stick (different makes/brands)
It's a 'Hp g62 - 105 sa', I'll get you those screen caps from CPU-Z.

To confirm, the issue disappears when using the regular HDD and reappears when using the SSD. I've switched between them a few times now.

It could be temperature related. I've not been checking that, but will try. I did have some periods where it would run OK for an hour or two which seemed to happen after it had been off for a while so probably a lot cooler.

I've been using the "balanced" power option. Although I did disable the "turn off Harddrives" setting.

I recently updated the Intel Matrix storage controller drivers from HP as I don't think I'd done it since the Win7 install as I had no yellow exclamation (warnings) in the device manager. So didn't worry too much about drivers. But out of desperation I tried it. It seemed to run OK for a few hours after that aside from a "Windows temporarily unable to read hard disk" message in the windows action center.

I'll post the CPU-z snips and then run memtest for a minimum of 7 passes tomorrow. Cheers.

 

[Dave76]

Good feedback.

The "balanced" power option and disable "turn off Harddrives" setting are best under your situation. Have seen these type of errors when systems return from sleep/hibernation, those settings should rule that issue out.

I think the RAM test will be a formality, but it needs to be done before we can be sure.

 

[iamcami]

I'm pretty sure the BSOD is a thing of the past. Ever since I updated the Intel drivers I mentioned in previous post, removed Daemon Tools and disable the turn off HDD power setting.

There are still some strange happenings though. Like alerts coming up saying certain services haven't started (windows update and security center). And one time it wouldn't boot all the way. Killed it and it booted OK. Just strange behavior.

Should I still go ahead and follow those steps Dave76 mentioned?

I will continue with these steps because while the BSOD seems to have stopped there is still some funny business going on.

Attached the CPU-Z stuff. And memtest ran for 7 passes