Help identifying faulty component

[danboss88]

Hi guys. I built my PC just over a week ago.

AMD Athlon II X4 Quad Core 635 2.90GHz (Socket AM3) - Retail 1
Patriot Viper 4GB (2x2GB) PC3-10666 1333MHz Dual Channel (PVS34G1333ELK)
Asus M4A78LT-M LE AMD 760G (Socket AM3) DDR3 Motherboard 1
Corsair CX 400W ATX Power Supply (CMPSU-400CXUK) 1
Seagate Barracuda 7200.12 500GB SATA-II 16MB Cache - OEM (ST3500418AS) 1
Xigmatek Asgard Midi Tower Case - Black 1
Samsung SH-S223C/BEBE 22x DVDąRW SATA ReWriter (Black) - OEM 1

Here's exactly what has been happening:

I'll boot the PC up in the morning and after loading Windows 7, applications will stop working (Firefox, IE, CCleaner, etc.) and then I'll receive a BSOD. This will continue for many times but then the computer will work fine for 12 hours or more. Then as soon as I start the computer the next day, this cycle continues.

Here are the error messages just from today:

On Tue 03/08/2010 14:03:51 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x93169, 0x1, 0x93CC1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\080310-18298-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 14:01:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x9CC68, 0x1, 0x9CC70)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\080310-17706-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:57:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0xCC3F0, 0x2, 0x10380F)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\080310-24944-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:55:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0x1AB9, 0x1A8C00043572)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\080310-18205-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:53:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x8D1C6, 0x1, 0x8D1CE)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\080310-18252-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:51:02 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x2, 0x70F58, 0x12FFFF, 0x1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\080310-17862-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:45:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x7FEFD011001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\080310-20514-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:44:04 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006D211E8, 0xFFFFF88006D20A50, 0xFFFFF880012EC173)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\080310-20124-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 03/08/2010 13:42:19 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xFFFFF8800124D05F, 0x8000000003968121, 0xFFFFF88006E6CEB0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Dump file: C:\Windows\Minidump\080310-21340-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

So far I have:

Reinstalled Windows 7
Ran memtest for 12 hours - no errors reported.
Ran orthos/Prime95 for a few hours - no errors reported.
Contacted OCuk support - told to run these applications again.

Would highly appreciate your help. Very frustrating!

 

[JonJ678]

Most likely problem is with ram or with windows. That's pretty generic advice, they're by far the most likely parts to give problems. Next on the list is motherboard, and end of the list is cpu.

Download an iso for memtest and burn it to cd-r using a different computer to the one giving you problems, leave it running overnight. If you've already done this then fair enough, from your post I've no idea if you ran it within windows or not.

Prime 95 for a few hours doesn't mean very much, it can take far longer to throw up problems. I've only used it for testing overclocks though, not certain whether a stock speed system with dodgy ram would cause it to fail or not.

There's no mention of windows 7 in your basket; if you've thieved a copy then it greatly increases the chances that it's windows at fault. At the very least verify the download via checksums, burn it slowly then checksum the disk. If you're installing from a knackered dvd, things will never work well.

Good luck

 

[MiTz]

I was getting random bsod on my last system, i ran memtest for 24 hours and it showed no errors... I sent the memory back for replacement anyway and this solved the problem, so passing memtest doesn't mean there isn't a problem with the ram..

Good luck mate

 

[honosuseri]

Does sound memory related. Try removing one stick of ram and run the system on that. If it still acts up swap that stick for the other one you removed and run the system again on the one stick of ram. Hopefully it will be stable but although rare it is possible both sticks are faulty.

You can also check the memory timings in the bios maybe the system is working the RAM to hard.

Hope this helps

 

[danboss88]

Thanks guys. I have removed one stick and will wait until tomorrow to see if the error continues. I had a look at the BIOS and the RAM settings were all set to Auto. Not sure if I should play around with those.

By the way, if the stick I have removed is faulty, should I contact OCuk or the manufacturer (Patriot?) for a repair/refund?

 

[honosuseri]

Well sometimes the auto settings can be wrong silly as that sounds. It's more likely that the RAM is faulty, wait and see what's what. You can email them for an RMA code to return the faulty component if that's the problem

Good luck