BSOD Need Help To End This Madness

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
M

Mystery Man

Distinguished
Apr 5, 2011
38
0
18,530
Ok, so I have no idea what is triggering this BSOD issue for me, but it keeps happening over and over and over again. Sometimes 5 hours after using my computer, sometimes 5 minutes. It is very random.

I just downloaded this program I saw on PC World.com called BlueScreenView. Here is what it said.


082912-33290-01.dmp 8/29/2012 9:28:29 PM
IRQL_NOT_LESS_OR_EQUAL
0x0000000a
00000000`00000046
00000000`00000002
00000000`00000001
fffff800`02ec1f88
ntoskrnl.exe
ntoskrnl.exe+70040
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7600.17017 (win7_gdr.120503-2030)
x64
ntoskrnl.exe+70040
C:\Windows\Minidump\082912-33290-01.dmp
4
15
7600
286,128
 
Sort by date Sort by votes
what's in the .dmp file? Without knowing what's in there, here's what comes to mind first...

I would shut down the computer and disconnect the power, then press the power button to dissipate the remaining power in the caps. Then i would open up the case and see if there's dust, if so, clean it. After cleaning the dust from everywhere remove the memory and put it right back. Also check all the power and data connections to your drives. If the computer is a couple years old I would replace the TIM on the processor with some new Arctic5 or something. Also reseat the video card if you have one. You should also make sure all the reataining screws on the motherboard are secure.
 
Upvote 0 Downvote

How would I check the .dmp files?
 
Upvote 0 Downvote
99 times out of a 100 this is caused by malfunctioning RAM. Try cleaning the contacts of the RAM carefully with a pencil eraser and re-seating it, and if you can borrow/have another stick of RAM around, try changing it and see what happens.

(Rarely, if you get some virus infections also it can result in this. I would do a full scan too if possible).


 
Upvote 0 Downvote

I did just uninstalled Norton and have not experienced a crash just yet.
 
Upvote 0 Downvote


Ah, so you uninstalled the Norton malware :)


I have had many, many computers land on my work bench (dining room table) and fixed such problems simply by uninstalling AV software which is primarily focused on make sure you upgrade at the end of the license period than on protecting the machine from viruses.
 
Upvote 0 Downvote
Generally, IRQL errors are due to bad RAM. However, in this case, that is not very likely.

The reason is the first parameter is the memory address that actually crashed. That address was 00000000`00000046. Typically, motherboards use memory addresses below the old 760k limit for addressing HW, so its looking like a HW problem rather then RAM, at least at first glance. Wouldn't hurt to run a memory test with memtest86 though.

If the memtest comes up clean (and I suspect it will), try a different GPU driver.
 
Upvote 0 Downvote
Had more or less the same problem occur on my boss's PC. He was running windows XP and an anti-virus update came out and basically trashed the whole thing, couldn't boot to safe mode or even do a repair install, we had to do a full re-install. Previous to this experience, I had heard about a Symantec update going out and any users below a certain version of windows XP all ended up with blue screens (this apparently affected MANY more PC's than the second experience that affected my boss, it was pretty big news). I would chalk it up to the Anti-Virus, especially if anything on it got updated recently. You may just be stuck re-installing windows, otherwise I did see some guides online to replacing the drivers through the recovery console (however this proved to be quite difficult for us, and we had to do a full install anyways).
 
Upvote 0 Downvote
Ok, so I ran Memtest multiple times and it found nothing. The BSOD keeps popping up though. I did get the 'Windows has recovered from an unexpected shutdown' message when I booted back up to the desktop.

Here is what the problem details showed (I am just copying it):


Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002E6B117
BCP3: 0000000000000000
BCP4: 000000007EFA0000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\090612-42073-01.dmp
C:\Users\John\AppData\Local\Temp\WER-59358-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Upvote 0 Downvote
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4270796800 total
VM: 2147352576, free: 1938980864



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 9/6/2012 7:29:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090612-42073-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E6B117, 0x0, 0x7EFA0000)
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.


On Thu 9/6/2012 7:29:50 AM 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E6B117, 0x0, 0x7EFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.


On Thu 9/6/2012 7:25:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090612-48079-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000317CFEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Thu 9/6/2012 6:54:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090612-43571-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xDC, 0x2, 0x1, 0xFFFFF80002EA9995)
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.


On Wed 9/5/2012 7:07:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-28407-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031B7FEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Wed 9/5/2012 5:41:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-40217-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003172FEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Wed 9/5/2012 2:10:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-36317-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x1000000DD, 0x2, 0x1, 0xFFFFF80002E60995)
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.


On Tue 9/4/2012 11:23:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-31356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E58117, 0x0, 0x7EFA0000)
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.


On Tue 9/4/2012 11:05:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-31902-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E62117, 0x0, 0x7EFA0000)
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.


On Tue 9/4/2012 6:09:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-33555-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003180FEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Tue 9/4/2012 4:49:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-32510-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031BAFEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Tue 9/4/2012 12:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-32697-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002EA3117, 0x0, 0x7EFA0000)
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.


On Mon 9/3/2012 3:52:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-27144-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1AE3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031C3FEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard Driver
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 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.


On Mon 9/3/2012 3:48:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-27331-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xDC, 0x2, 0x1, 0xFFFFF80002E5F995)
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.


On Mon 9/3/2012 3:46:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-30716-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E53117, 0x0, 0x7EFA0000)
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.


 
Upvote 0 Downvote

Where do I check to see if I am using 11.5 or 11.2, possibly?
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom