Very frequent bsods with F3-10600CL9D-8GBNT

[lawlz]

Hi,

I have 8 gigs of F3-10600CL9D-8GBNT RAM. I don't know all that much about computers, at least by the standards of this forum, so here's the full description:

G.SKILL Value Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600) Desktop Memory Model F3-10600CL9D-8GBNT


I'm running it on this motherboard:

ASRock H61M/U3S3 LGA 1155 Intel H61 HDMI SATA 6Gb/s USB 3.0 Micro ATX Intel Motherboard


with this CPU

Intel Core i3-2100 3.1GHz Dual-Core 65W LGA1155


and this video card

EVGA 01G-P3-1556-KR GeForce GTX 550 Ti (Fermi) FPB 1GB 192-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card



I get frequent bsods. I've appended the WhoCrashed logs to this message, below.

I've just tried changing the voltage from "auto" to 1.605 or something like that. It had been set at around 1.575, I think.

Do you have any ideas? I'm not trying to overlock this computer or anything. I just want to get it working at spec. It mostly works okay, but it crashes pretty frequently. No obvious pattern; sometimes while watching YouTube, sometimes while playing LOL.

[lawlz]

crash logs 1

---
crash logs
---

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8571781120 total
VM: 2147352576, free: 1948942336



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 7/24/2011 4:11:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072311-21606-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x411, 0xFFFFF680000068A8, 0x5C00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 4:11:55 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: 0x1A (0x411, 0xFFFFF680000068A8, 0x5C00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 7/22/2011 6:53:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-21886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x99, 0x16BE17, 0x3, 0x182278)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/18/2011 2:39:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-24180-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003140100, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/17/2011 1:43:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x3, 0xFFFFF88002187550, 0xFFFFF88002182150, 0xFFFFF88002187550)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 7/14/2011 1:38:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071411-23727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41284, 0xFFFFF7063FBE6001, 0x196133, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 7/14/2011 10:53:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071411-23758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41284, 0xFFFFF8A009F44001, 0x9971, 0xFFFFF781C0000000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/10/2011 3:33:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-33399-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x411, 0xFFFFF683FF7F7E00, 0x4C00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/10/2011 2:36:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-29530-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A007E03620, 0xFFFFF8A007E03620, 0xFFFFF8A007E02620)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[lawlz]

crash logs 2

On Sat 7/2/2011 9:00:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-34647-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003140100, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/2/2011 6:33:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-27159-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C7A904)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sat 7/2/2011 7:15:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-20202-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x849E)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x4A8E, 0x4A9000008D1C)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 6/27/2011 12:21:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062611-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000291AB2C, 0xFFFFF88003765E50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Sun 6/26/2011 11:12:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062611-24086-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003140130, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Tradesman]

Do you have the latest BIOS? Have you tried running memtest on each stick individually to make sure both sticks are good

[lawlz]

Hi -

I did update the BIOS. It's still doing it. Here are some new reports:





windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8571781120 total
VM: 2147352576, free: 1948221440



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 8/6/2011 10:19:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-29515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x49E, 0x4A000000D3C)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 8/6/2011 10:19:14 PM 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: 0x1A (0x5003, 0xFFFFF70001080000, 0x49E, 0x4A000000D3C)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/3/2011 3:05:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-47205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003140130, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Tradesman]

Have you run memtest on each stick individually? Also can you post your DRAM settings as well as your system voltages

[lawlz]

Have you run memtest on each stick individually? Also can you post your DRAM settings as well as your system voltages

Thanks for the reply!

I googled around, but can't figure out how to get that info. Any suggestions?

[Tradesman]

Start with Memtest, can get it here and instructions on how to run it

http://www.memtest.org/

[lawlz]

Have you run memtest on each stick individually? Also can you post your DRAM settings as well as your system voltages

Got my settings:


VOLTAGE
Power Saving || Disabled
CPU Core Voltage Offset || +0mV
IGPU Voltage Offset || +0mV
DRAM Voltage || 1.575V
PCH Voltage || 1.059V
CPU PLL Voltage || 1.794V
VTT Voltage || 1.057V
VCCSA Voltage || 0.925V



DRAM TIMING CONTROL
DRAM Freq || DDR3-1066
CAS# Latency (tCL) || 7
RAS# to CAS# Delay (tRCD) || 7
Row Precharge Time (tRP) || 7
RAS# Activation (Action? Active?) Time (tRAS) || 20
Command Rate (CR) || IN // ... I have what looks like 1N or IN written dwon. Could be 1 V.
Write Recovery Time (tWR) || 8
Refresh Cycle Time (tRFC) || 86
RAS to RAS Delay (tRRD) || 4
Write to Read Delay (tWTR) || 4
Read to Precharge (tRTP) || 4
Four Activate Window (tFAW) || 16

Memory Power Down Mode || "Auto"
same for:
ODT WR (CHA)
ODT NOM (CHA)
ODT WR (CHB)
ODT NOM (CHB)

[lawlz]

http://www.newegg.com/Product/Produc...D=3067296&SID=


... am I just really stupid and I just need to change

DRAM Frequency --> DDR3 1333
and then change some of these timings to 9? Not sure which ones, though ... maybe tCL, tRCD, tRP?

... though I'm actually not sure exactly what numbers these reference. e.g., it says voltage 1.5V ... does that mean I should bring it down from 1.575, or is it better to be a bit high?

I'm getting hopeful that this situation is fixable.

[Tradesman]

Yes speed to 1333, base timings 9-9-9-24, DRAM voltage 1.5 and CR (Command Rate or Command Timing) to 2T or 2N depending if the mobo uses the T or the N designator

[lawlz]

Yes speed to 1333, base timings 9-9-9-24, DRAM voltage 1.5 and CR (Command Rate or Command Timing) to 2T or 2N depending if the mobo uses the T or the N designator

http://www.newegg.com/Product/Produc...82E16813157236

Is that T or N, do you think?

Also: thank you so much. I hope this works.

EDIT: It didn't even give a T option, so I did N

[Tradesman]

Yep, it used to always be T w/ Intel system and N with AMD as designators, now it's almost interchangeable - it will be one or the other - Let us know how it goes