BSOD while folding on new rig help please?

Hello everybody,

Just built a new rig Its in my signature. I have really no experience with the bsod, so heres whats going on.

I built my new computer and started messing with overclocking trying to learn, and could never get it stable, so I set my bios back to default then picked the performance option in the Asus P8Z68 Deluxe UEFI and that set speed to 4.4ghz which I figured should be stable or else I didn't think Asus would put that option there.

So everything was fine, I was folding for at least 5 days straight no problems, then I started getting bsod's, it will take at least 3-4 hours of folding before I get one.

I ran Whocrashed and this is what I got. It wouldn't let me attach .RAR file for my minidump so I have it hosted here if that will be helpful:

http://limelinx.com/files/7c435fea34e75898d6577d71f3427798

Thanks every body any help will be greatly appreciated!


windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17080270848 total
VM: 2147352576, free: 1966448640

---

Crash Dump Analysis

---

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 2/26/2012 12:22:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022612-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E66E7D, 0xFFFFF8800A6D9410, 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 2/26/2012 5:29:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-16660-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41284, 0xFFFFF7044001B001, 0x14868, 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 Sun 2/26/2012 2:33:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-17128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000780FC0, 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 2/25/2012 7:01:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022512-21028-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880086FD5D8, 0xFFFFF880086FCE30, 0xFFFFF880012CE527)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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.

Thanks, I've read the first tutorial you posted. I haven't seen the second one, I'm going to read it tho.

So my problem continues, I don't even need to have a load on the CPU to trigger a blue screen, So I been doing a Memtest86+ for 4 hours. I got over 1 million errors, does that mean I have a bad chip? how do I locate what dimm is bad? Or could this mean something else?

I reset the bios back to stock defaults.
Edited by Chrisnbig - 2/27/12 at 3:30am

Yup, Thats exactly what I had to do. It Was a faulty stick.. Going to return it to Micro Center, I just hope they give me 1 new stick instead of replacing all four, since I bought them in a 4 pack. Dont need the trouble of testing 4 new sticks. Thanks everybody for the help.

Hey eveerybody,

Its been a month with the new ram chips, and another one went bad. Exactly 1 month after replacement.

My PC has been folding continuously for that month. I'm thinking these ram chips cant handle it? I'll take them back to Micro Center, anyone know of some better chips that can handle what I'm trying to do?