BSOD's - Please solve :-)

[xjustelevenx]

Here's a copy from "WhoCrashed"

________________________________________________

Crash dump directory: C:\Windows\minidump

Crash dumps are enabled on your computer.

1)

On Thu 13/10/2011 4:00:03 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101311-8283-01.dmp
uptime: 01:31:26
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B73028, 0xB6272000, 0x16000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.

2)

On Thu 13/10/2011 2:20:16 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-15880-01.dmp
uptime: 00:01:27
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x4E (0x99, 0x17122A, 0x0, 0x17132A)
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.

3)

On Thu 13/10/2011 2:14:56 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-8283-01.dmp
uptime: 00:12:26
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A0018A8000, 0x1, 0x0)
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.

4)

On Thu 13/10/2011 2:01:52 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-8767-01.dmp
uptime: 00:00:31
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFD20, 0x2, 0x0, 0xFFFFF800030A485A)
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.

5)

On Thu 13/10/2011 1:54:30 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-8704-02.dmp
uptime: 00:00:14
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xFC (0xFFFFF900C32F7050, 0xC2D00001C34B1863, 0xFFFFF88003FDB8D0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

6)

On Thu 13/10/2011 1:52:34 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-8704-01.dmp
uptime: 00:00:13
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033CC0E8, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.

7)

On Thu 13/10/2011 1:51:06 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-8221-01.dmp
uptime: 00:00:14
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8004B464C41, 0x0, 0xFFFFF800033AE9BA, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

8)

On Thu 13/10/2011 1:48:31 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\101211-9718-01.dmp
uptime: 00:00:06
This was probably caused by the following module: ntoskrnl.exe (nt+0x9FCEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF800030F2CEE, 0xFFFFF880045AF018, 0xFFFFF880045AE870)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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.

9)

On Fri 7/10/2011 11:58:48 PM GMT your computer crashed
crash dump file: C:\Windows\minidump\100711-8876-01.dmp
uptime: 3 days, 02:17:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFF1000F496CF8, 0x2, 0x0, 0xFFFFF8800126637D)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.

___________________________________________________________

Any ideas?

I mainly want to know what's wrong with the First BSOD - as WhoCrashed says it's hardware

-System-
(hopefully this helps?)

- Sentey Arvina

- ASUS M5A88-V EVO

- ZOTAC AMP! ZT-40102-10P GeForce GTX 480

- Rosewill Xtreme Series RX850-S-B 850W Continuous @40°C

- AMD Phenom II X6 1100T

- OCZ Agility 3

- CORSAIR Vengeance 8GB 1866


*edit : added numbers to distinguish.

 

[xjustelevenx]

Another BSOD today

------------------------------------


On Sat 15/10/2011 9:37:38 PM GMT your computer crashed
crash dump file: C:\Windows\minidump\101511-8658-01.dmp
uptime: 20:19:45
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007BA1028, 0xB42A2000, 0x2E000145)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.

--------------------------------------------

Maybe because of RAM OC'd at 2ghz?

 

[g-unit1111]

OC'ing your RAM is generally not a good idea to begin with. And it's mainly because the RAM heat sinks are not designed to take a lot of overheating. If you put in the wrong timing and voltage, you could fry the RAM or something else. If your motherboard's BIOS has a "load defaults" feature, try defaulting and see what that does to your system.

 

[xjustelevenx]

I read in a review that they are easily (Saftly) OC-able at 2ghz @ 1.65 - originally 1866@ 1.5 — Is there any program that will log temps for me? As I can't really see the temps in game lol :\

--- So then I can monitor temps more easily and see what exactly is overheating, could be because my board's max speed for ram is 2ghz and it's just too much for heatsinks.

 

[g-unit1111]

Not that I'm aware of. I mean the thing is I know RAM can be overclocked but I wouldn't push it as you could really test the limits of your motherboard.

 

[steelbeast]

Honestly, that looks like your HDD is failing. What HDD do you have and how old? ntoskernel and hal.dll are crashing your system which is vital to your OS, and these are the first signs of a failing HDD. I recommend running CHKDSK at boot time

You learn these things after servicing 100's of PCs lol.

 

[xjustelevenx]

My drive that's running windows is a Agility 3 with newest firmware - Other hdd is seagate baracuda LP — Though - I don't think the hdd can really cause BSODs - can it? **Because.. the hdd is just being used as storage - windows files.

 

[steelbeast]

My drive that's running windows is a Agility 3 with newest firmware - Other hdd is seagate baracuda LP — Though - I don't think the hdd can really cause BSODs - can it? **Because.. the hdd is just being used as storage - windows files.

That OCZ SSD is probably the culprit. It's most likely the controller that's failing because SandForce is fast, but their junk. I had 2 OCZ SSDs fail on me within a short time, causing BSODs and randomly "disappearing" from my system. I'll never buy them again.

 

[xjustelevenx]

Alrighty, so ram @ 2ghz is alright? And thanks, I'll keep a lookout - PS. Do you know what the warranty is for them - in-case it does fail?

 

[steelbeast]

Alrighty, so ram @ 2ghz is alright? And thanks, I'll keep a lookout - PS. Do you know what the warranty is for them - in-case it does fail?

If you did OC your RAM, put it back to stock settings and see if the BSODs go away. If not, your SSD should have a 3 year warranty, about 1-2 weeks for RMA. Good luck.

 

[xjustelevenx]

Best answer selected by xjustelevenx.

 

[xjustelevenx]

Thanks - no BSODs since yesterday - Only thing I've changed is switched from the beta nvidia drivers to newest (stable) driver.