- Aug 22, 2013
- 4
- 0
- 10,510
Specs
OS : Windows 7 Ultimate X64
CPU: Intel Core i5 3570K @ 3.40GHz
Motherboard : ASUSTeK COMPUTER INC. P8Z77-V (LGA1155)
Memory : VENGEANCE LP 8GB Dual-Channel DDR3
GPU: NVIDIA GeForce GTX 460 (Gigabyte)
HDD: 298GB Western Digital WDC WD3200AAJS-00L7A0 (SATA)
1863GB Western Digital WDC WD20EARX-00PASB0 ATA Device (SATA)
(Multiple external HDDs connected at any time)
I've built a custom computer almost a year ago and have been having problems with it eversince. At first random crashes and BSOD were bearable and i didn't make much of them. 5 months ago it finally became unbearable and i wasn't able to play %90 of my video games. They all crashed after 5 minutes, if the computer didn't reboot because of a BSOD first. There were a couple of times where these didn't happen at all and because of this inconsistency i was unable to reproduce this problem when i brought my pc to a computer engineer. Even if they saw what the problem was, no one could tell me what caused it. Needless to say, i have formatted my hard drives and did multiple clean installs since and before then, to no avail.
A month ago with one of my friends we thought we solved the problem after we disabled my motherboard's wi-fi go option and none of the stress tests came back with a BSOD (they didn't last 10 mins before). But after a week the same problem came back and i have been trying to deal with it eversince.
To be more brief:
-Video Games crash to desktop most times.
-Every 4 or 5 crash where i'm playing video games is replaced by a BSOD instead.
-It has given me BSODs a couple of times when i'm not playing a video game but it's very, very rare.
What i have tried:
-Complete clean installs on multiple different internal HDDs.
-Different versions of Windows 7 and even Windows 8.
-Cooling down the system to the point that i'm now using 7 fans.
-I have rolled my LAN and GPU drivers back and did clean installs on them.
I'm sorry if i've given too much information or if i have given too little, but this really has bothered me to the point that i've thought about selling each part individually and building a new custom PC.
I hope you come up with a solution that finally solves this irritating problem that could potentially ruin my life
Below are the whocrashed dump reports.
On Wed 21.08.2013 17:32:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-28938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x11A, 0x2, 0x0, 0xFFFFF80003C977B9)
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 that cannot be identified at this time.
On Wed 21.08.2013 17:32:03 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: 0xA (0x11A, 0x2, 0x0, 0xFFFFF80003C977B9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 that cannot be identified at this time.
On Wed 21.08.2013 12:42:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC5 (0xFFFFF81002E536B0, 0x2, 0x0, 0xFFFFF80002DF8A4E)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid 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. 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 that cannot be identified at this time.
Note: After reviewing the dump reports i've attached, i've realized that it only includes a couple of dump files, this i suspect is because i've used ccleaner earlier yesterday.
Most earlier dump files consisted of "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and "nvlddmkm.sys" and i realize that the ones i've attached do not. So, there you go.
OS : Windows 7 Ultimate X64
CPU: Intel Core i5 3570K @ 3.40GHz
Motherboard : ASUSTeK COMPUTER INC. P8Z77-V (LGA1155)
Memory : VENGEANCE LP 8GB Dual-Channel DDR3
GPU: NVIDIA GeForce GTX 460 (Gigabyte)
HDD: 298GB Western Digital WDC WD3200AAJS-00L7A0 (SATA)
1863GB Western Digital WDC WD20EARX-00PASB0 ATA Device (SATA)
(Multiple external HDDs connected at any time)
I've built a custom computer almost a year ago and have been having problems with it eversince. At first random crashes and BSOD were bearable and i didn't make much of them. 5 months ago it finally became unbearable and i wasn't able to play %90 of my video games. They all crashed after 5 minutes, if the computer didn't reboot because of a BSOD first. There were a couple of times where these didn't happen at all and because of this inconsistency i was unable to reproduce this problem when i brought my pc to a computer engineer. Even if they saw what the problem was, no one could tell me what caused it. Needless to say, i have formatted my hard drives and did multiple clean installs since and before then, to no avail.
A month ago with one of my friends we thought we solved the problem after we disabled my motherboard's wi-fi go option and none of the stress tests came back with a BSOD (they didn't last 10 mins before). But after a week the same problem came back and i have been trying to deal with it eversince.
To be more brief:
-Video Games crash to desktop most times.
-Every 4 or 5 crash where i'm playing video games is replaced by a BSOD instead.
-It has given me BSODs a couple of times when i'm not playing a video game but it's very, very rare.
What i have tried:
-Complete clean installs on multiple different internal HDDs.
-Different versions of Windows 7 and even Windows 8.
-Cooling down the system to the point that i'm now using 7 fans.
-I have rolled my LAN and GPU drivers back and did clean installs on them.
I'm sorry if i've given too much information or if i have given too little, but this really has bothered me to the point that i've thought about selling each part individually and building a new custom PC.
I hope you come up with a solution that finally solves this irritating problem that could potentially ruin my life
Below are the whocrashed dump reports.
On Wed 21.08.2013 17:32:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-28938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x11A, 0x2, 0x0, 0xFFFFF80003C977B9)
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 that cannot be identified at this time.
On Wed 21.08.2013 17:32:03 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: 0xA (0x11A, 0x2, 0x0, 0xFFFFF80003C977B9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 that cannot be identified at this time.
On Wed 21.08.2013 12:42:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC5 (0xFFFFF81002E536B0, 0x2, 0x0, 0xFFFFF80002DF8A4E)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid 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. 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 that cannot be identified at this time.
Note: After reviewing the dump reports i've attached, i've realized that it only includes a couple of dump files, this i suspect is because i've used ccleaner earlier yesterday.
Most earlier dump files consisted of "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and "nvlddmkm.sys" and i realize that the ones i've attached do not. So, there you go.
Facebook
Twitter
Instagram