Disclaimer: Mac user my whole life, had a custom built PC sent my way from iBuyPower, and have been having issues for the last year. I'm in desperate need of help (I use this PC for work) and sending it in isn't really an option because it would take a month+. Talking with their tech people has resulted in little help.
So about a month ago I couldn't get my computer to boot up due to frequent blue screens. I eventually just reset my entire Windows (files gone and all) and just reinstalled it.
For a couple of weeks, it worked like a charm. Then, yesterday, I got a blue screen "IRQL_NOT_LESS_OR_EQUAL". I've done plenty of hardware tests with not a single error, and have pretty much determined that it's a driver issue. But I can't figure out which driver is causing the problem? I ran a verifier test for a few hours and that popped up with nothing. Also ran a 3 hour Mem86 test, with no errors.
I'm getting a frequent error (16389) that says "A new BITS job could not be created...", and I'm not sure if that has anything to do with it. I'll also occasionally get an error when booting up or closing down (7000) that says "The AODDriver4.2.0 service failed to start due to the following error: the system cannot find the path specified".
I did mess with the CPU a bit and overclocked it, but I'm not sure that's my problem. I reset the BIOS to defaults, and that didn't really fix anything.
Any and all help would be HUGELY appreciated. I can provide any extra info necessary. I can't afford to have my computer crash out on me again, especially if I'm not sure that a reset would fix it.
Update: Just installed some new RAM. So far, so good.
Update #2: Memory dumps...
On Sat 7/4/2015 9:04:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
uptime: 01:11:19
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFBA80021AE000, 0x2, 0x0, 0xFFFFF803B12A5B5D)
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 Sat 7/4/2015 10:14:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-14015-01.dmp
uptime: 01:15:33
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8267CD0E60, 0x2, 0x0, 0xFFFFF8032493E09D)
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 Sat 7/4/2015 7:56:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-19000-01.dmp
uptime: 00:01:19
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA82661A8CF0, 0x2, 0x0, 0xFFFFF801B62CC09D)
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 Sat 7/4/2015 5:02:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-20156-01.dmp
uptime: 00:11:12
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA819A398D10, 0x2, 0x0, 0xFFFFF801C0ED809D)
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 Thu 7/2/2015 4:24:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070215-17812-01.dmp
uptime: 08:16:11
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x4F)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 that cannot be identified at this time.
On Wed 7/1/2015 7:11:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070115-16484-01.dmp
uptime: 01:40:20
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA819D80E810, 0x2, 0x0, 0xFFFFF802A394309D)
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.
So about a month ago I couldn't get my computer to boot up due to frequent blue screens. I eventually just reset my entire Windows (files gone and all) and just reinstalled it.
For a couple of weeks, it worked like a charm. Then, yesterday, I got a blue screen "IRQL_NOT_LESS_OR_EQUAL". I've done plenty of hardware tests with not a single error, and have pretty much determined that it's a driver issue. But I can't figure out which driver is causing the problem? I ran a verifier test for a few hours and that popped up with nothing. Also ran a 3 hour Mem86 test, with no errors.
I'm getting a frequent error (16389) that says "A new BITS job could not be created...", and I'm not sure if that has anything to do with it. I'll also occasionally get an error when booting up or closing down (7000) that says "The AODDriver4.2.0 service failed to start due to the following error: the system cannot find the path specified".
I did mess with the CPU a bit and overclocked it, but I'm not sure that's my problem. I reset the BIOS to defaults, and that didn't really fix anything.
Any and all help would be HUGELY appreciated. I can provide any extra info necessary. I can't afford to have my computer crash out on me again, especially if I'm not sure that a reset would fix it.
Update: Just installed some new RAM. So far, so good.
Update #2: Memory dumps...
On Sat 7/4/2015 9:04:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
uptime: 01:11:19
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFBA80021AE000, 0x2, 0x0, 0xFFFFF803B12A5B5D)
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 Sat 7/4/2015 10:14:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-14015-01.dmp
uptime: 01:15:33
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8267CD0E60, 0x2, 0x0, 0xFFFFF8032493E09D)
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 Sat 7/4/2015 7:56:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-19000-01.dmp
uptime: 00:01:19
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA82661A8CF0, 0x2, 0x0, 0xFFFFF801B62CC09D)
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 Sat 7/4/2015 5:02:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070415-20156-01.dmp
uptime: 00:11:12
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA819A398D10, 0x2, 0x0, 0xFFFFF801C0ED809D)
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 Thu 7/2/2015 4:24:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070215-17812-01.dmp
uptime: 08:16:11
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x4F)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 that cannot be identified at this time.
On Wed 7/1/2015 7:11:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070115-16484-01.dmp
uptime: 01:40:20
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA819D80E810, 0x2, 0x0, 0xFFFFF802A394309D)
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.
Facebook
Twitter
Instagram