BSODs out the YingYang... Memtest86+ showing incorrect ram settings, says I have DDR640 ram with CAS 1-3-3-3

[thecynicalmonk]

Title says it all. I have Corsair Vengeance DDR3-1600 CAS 9-9-9-24 @1.5v(unfortunately, I'm regretting getting these sticks instead of G. Skill or the like) and it's been causing all sorts of problems... I've been getting BSODs every time I set it to 1600 from 1333 (My mobo defaults to 1333, I wish AMD would adopt something like XMP :/ ) Currently I have memtest running.... I'll probably let it run for 6 hours or so. Any thoughts? What else could I do to troubleshoot my BSODs? Once I can reboot it I'll post the crash dump from WhoCrashed.

Also, why is memtest not recognizing my ram speed and timings? CPU-Z does, as well as BIOS. Would this affect my memtest results?

Regards,
the ever-so Cynical Monk

 

[inzone]

You can try a couple of things to get the ram to work at 16oomhz.

1. When you set the ram speed to 1600mhz add a bit of voltage, it shouldn't take much maybe a notch or two.

2. You can try to relax the timings a bit, maybe try 9-10-9-27 or 10-11-10-30.

3.Try setting the ram to 1333mhz and the raise the BCLK till the ram is at 1600mhz, this will also affect the CPU so it would depend on whether or not your CPU is overclocked to start with and if you want it to be overclocked.

4. Overclock the CPU since the memory controller may only support 1333mhz the CPU would need to be overclocked in order for the memory controller to support the higher 1600mhz.

You don't have to do all of the above and maybe just one of them will work. So you could try the one that looks the easiest to you.

 

[thecynicalmonk]

Here's my crash dump...Hope it helps!

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 4/24/2013 7:34:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-31465-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006D24670, 0xFFFFF8001275B770, 0xFFFFFA800C3F4110)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/24/2013 7:34:18 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006D24670, 0xFFFFF8001275B770, 0xFFFFFA800C3F4110)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/17/2013 11:01:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041713-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8006C7E7F0, 0xFFFFF800B1A7B770, 0xFFFFFA8007D310A0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[thecynicalmonk]

You can try a couple of things to get the ram to work at 16oomhz.

1. When you set the ram speed to 1600mhz add a bit of voltage, it shouldn't take much maybe a notch or two.

2. You can try to relax the timings a bit, maybe try 9-10-9-27 or 10-11-10-30.

3.Try setting the ram to 1333mhz and the raise the BCLK till the ram is at 1600mhz, this will also affect the CPU so it would depend on whether or not your CPU is overclocked to start with and if you want it to be overclocked.

4. Overclock the CPU since the memory controller may only support 1333mhz the CPU would need to be overclocked in order for the memory controller to support the higher 1600mhz.

You don't have to do all of the above and maybe just one of them will work. So you could try the one that looks the easiest to you.

Thank you for the awesome help, inzone, but I finished my memtest scan... 3 bad sectors :-/
I RMA'd it about 2 hours ago as well as ordered me a Samsung 840 Series 120GB SSD I wish i could afford the Pro...but any SSD (within reason) is better than NO SSD!

(FYI people: Newegg has a 20% off sale running on select Samsung SSDs till midnight tonight! Here's the link. And the promo code is EMCXSVT249 ! Get it fast!)