New SSD causing issues

Have a nice day.

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"

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.

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 https://www.sevenforums.com/crashes-d...asus-mobo.html

EDIT: Finally got it done. Check the upload

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.

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

The repeating crashes are not included.

Code:

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:

Code:

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.

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.

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