BSOD after installing new Kingston SSDNOW V300

Britton30 said:

Your CPU is nearly 7 years old. Intel Core 2 Quad Q6600 HH80562PH0568M (BX80562Q6600)
This is a bit before Vista was released. Timeline of Microsoft Windows - Wikipedia, the free encyclopedia which did support AHCI.

I'm not positive but the SSD should, I say should, work in SATA mode once you set the BIOS correctly.

I have the same CPU.

If his motherboard is anything like mine, its a standard Overclock. My CPU at home is a 2.66Ghz Quad Core LGA775 socket. My motherboard, much like my previous ASUS RoG board, it overclocks it to 2.83Ghz. Now, this could have some adverse effect with it. Other than what I stated previously, I haven't worked with any SSD besides my own, which was like a massive cake awalk.

Good to know, good luck and enjoy the SSD.

x BlueRobot said:

Code:

BugCheck 124, {0, fffffa8003e368f8, 0, 0}
 
Probably caused by : GenuineIntel

Code:

1: kd> !errrec fffffa8003e368f8
===============================================================================
Common Platform Error Record @ fffffa8003e368f8
-------------------------------------------------------------------------------
Record Id     : 01cebd8121e3ef65
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/30/2013 2:02:39 (UTC)
Flags         : 0x00000002 PreviousError
 
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8003e36978
Section       @ fffffa8003e36a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
 
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fb
Processor ID  : 0x0000000000000000
 
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8003e369c0
Section       @ fffffa8003e36b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
 
Local APIC Id : 0x0000000000000000
CPU Id        : fb 06 00 00 00 08 04 00 - bd e3 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
 
Proc. Info 0  @ fffffa8003e36b10
 
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8003e36a08
Section       @ fffffa8003e36b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
 
Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

The error seems to have been caused by something attempting to access the data within the Level 0 cache, whilst the processor was having generic non-timeout related error.

I've also checked the CPU documentation for the mnemonics for the above error, and error sourced from the processor (SRC) and something did in fact access the Level 0 Cache (M = Memory Access).

Are you performing any overclocking?

The MMU within the CPU may not have been physically able to translate a address, because it's either physically broken or the driver is using a incorrect pointer; or that the address wasn't valid or existent.

Run the Small FFT's, Large FFT's and Blend Test for a few hours each; do not let the temperature exceed 80*C.

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

Actually Harry I did notice a lot of hardware related issues in some of those files is this what you are referring to if so it is handy to know that.

Johnnycash said:

ICit2lol said:

Well that is a pain after all that keep us updated on howthe install goes anyway. It could possibly be you have a bad SSD too. If itstill keeps happening then maybe you ought to get a replacement drive. It won'tbe the first time and certainly not the last mate.

Now I just had a look at the Kingston and it has a SandForce controller I know they have had a fair share of problems with it (controller) in the past so just keep it in mind. I know the others will be able to tell you if the problems have now been sorted out but personally I stick to the Samsungs now.

You will surely need up to date mobo & CPU to fully enjoy the SSD speeds. Advice would be to stop abusing brands like sandforce even though the problems being faced are very much inherent & not at all relevent to sandforce. Grow up people!

Well Johnny if you READ my post I said that the SandForce controllers have had problems in the past I was not abusing them please do not go insinuating that I was myself abusing them. In fact the SanDisk Extreme in my laptop has the said brand of controller in it and I have not had any problems.

I agree with ICit2lol, Sandforce controllers in almost any brand SSD have seen a fair amount of threads here dealing with poor performance, dead, data corruption...
The one exception seems to be Intel's specially modded Sandforce controllers.for its own SSDs. No one here is abusing any bran mate, Sandforce did it themselves, we report the facts.

Well the Kingston HyperX was able to last a lot longer before finally BSODing...
I should also mention that I used Chrome for browsing just fine for 5 days and started using Firefox for about 1.5 days before getting a BSOD.
here's the error message and also attached new diagnostic files:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800405D028
BCP3: 00000000F2000040
BCP4: 0000000000000800
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\100613-13182-01.dmp
C:\Users\marcus\AppData\Local\Temp\WER-17019-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt