Random BSOD, error 0x0000000A

[ToxicFyre]

Hello, I've had a BSOD while downloading a game and playing Dwarf Fortress, which are not CPU or GPU intensive activities. This crash happened on the 05th of December 2012 at around 11 o'clock.

Before these BSODs I used to get other crashes of a different more frequent type, but these were because of a faulty video card, which I removed.
Now, after enjoying a BSOD free computer for a few hours I suddently get this one.
Using the program WhoCrashed it says this:

On Thu 12/6/2012 5:01:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120512-14648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0xA (0x100000041, 0x2, 0x1, 0xFFFFF80003A9B468)
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 Thu 12/6/2012 5:01:17 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: 0xA (0x100000041, 0x2, 0x1, 0xFFFFF80003A9B468)
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.

They are apparently random and don't happen very frequently. (once every three hours or so)

I would really appreciate anyone's help. Thank you for your time.

SPECS: http://www.sevenforums.com/member.php?u=256508
Attatched BSOD info.

 

[koolkat77]

Welcome to SevenForums

AVG can contribute in BSOD-s. Please uninstall it and replace with Microsoft Security Essentials (To test).

• AVG | Download tools and utilities

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

1. Microsoft Security Essentials - Free Antivirus for Windows
2. Malwarebytes - Free
3. http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html
​

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

---

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

• 
  1. Click on the rb:
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

---

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

---

Free up the start-up, nothing except the antivirus is usually needed.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

---

Go to this link: Intel® Driver Update Utility and check the system for latest updates. Download and install all the recent driver(s) it finds.

*Post back if this brings stability or you get any BSOD-s after making these changes.
​

Then test RAM.
​

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:info: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

 

[ToxicFyre]

Wheww, that took a long time.
Ok after testing one RAM stick for 8 passes, and the other two for 16 passes, I found two errors on one of them after 15 passes. (I don't know if only two errors is enough )
So I took out that RAM stick with the errors, and am now checking if it will crash. Will post again if it does.

Thank you

 

[ToxicFyre]

I just got a crash...

Here is the dump:

Thank's everyone who viewed this thread, and thank you koolkat77 for replying.
And for everyone that's gonna reply in the future, thanks in advance.

 

[koolkat77]

Why'd you enable driver verifier?

 

[ToxicFyre]

I used it to fix another problem I was having with my drivers a while ago.
Is it still on?!?!

How do I turn it off?

Thanks, ToxicFyre

 

[koolkat77]

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[ToxicFyre]

There. Driver Verifier disabled.

 

[koolkat77]

OK.

Post when you have new dumps.

 

[ToxicFyre]

Crash, after a full day of crash free bliss.
Here is the dump:
Thank you so much for helping me.
I really appreciate it.

P.S. If it helps, here is my "WhoCrashed" Dump about these recent crashes:

On Sun 12/23/2012 1:06:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-10280-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x1A (0x41287, 0x77000109A788, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 



On Sun 12/23/2012 12:08:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-10280-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80003A8051B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

PP.S Ohh, and both recent crashes happened while I was playing BF3.

 

[koolkat77]

Have you taken memtest?

 

[ToxicFyre]

Do you mean again?
Or the one I did before:
Stick 1 - 7 passes nor errors
Stick 2 - 16 passes no errors
Stick 1 and 2 at the same time: 7 passes no errors

(I previously removed stick 3 because it found two errors after 15 passes)

So should I make another memtest with these sticks? (1 and 2)

 

[koolkat77]

Did you remove the stick or did you replace it?
How many sticks of RAM do you have exactly?

Is the firmware for your SSD up to date?

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

Usual causes:  Memory corruption, Hardware (memory in particular), 
[B]Overclocking failure[/B], Installing a faulty or mismatched hardware 
(especially memory) or a failure after installing it, 3rd party firewall, 
Device drivers, SCSI/network/[B]BIOS updates needed[/B], Improperly seated cards, 
Incompatible storage devices, Overclocking, Virus scanner, Backup tool, 
Bad motherboard, Missing Service Pack
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80003a8051b

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff80003a89569 to fffff80003a89fc0

STACK_TEXT:  
fffff880`0368eee8 fffff800`03a89569 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0368eef0 fffff800`03a87a32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0368f030 fffff800`03a8051b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
ffff7880`036b0a40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x2b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03a87a32 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

If you are overclocking your system, please return all overclocked components to their stock speeds.
If the BSOD's are found not to be caused by the overclock, you can re-overclock the components
to a stable speed once we have finished the diagnostics.

!sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7 CPU       X 990  @ 3.47GHz"
MaxSpeed:     3470
CurrentSpeed: 3549

Check for a more recent BIOS version.

BIOS Version/Date	American Megatrends Inc. 1401, 5/12/2011

Uninstall any overclocking software because it can lead to system instability and BSOD's.
Please reset all components to their stock speeds and then remove the software.

For monitoring the heat/celsius of the system, use Speccy or HWinfo:

• Speccy - System Information - Free Download
• CPUID - System & hardware benchmark, monitoring, reporting

Perform a System File Check:

• Click on the start rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Disk Check on your hard drive for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

 

[ToxicFyre]

I have 3 RAM sticks.
There are three slots on my motherboard.
So when I test each stick I just remove the other two.
So stick one is in slot one, and stick two is in stick two.

The SSD, BIOS and overclocking seems complicated. I'll find out how to chack and do it, and get back to you later .

The my graphics card's max temperature is 91, and the processor's way below that.

File check found no errors, or corruptions.

Checking disk right now, will edit post when I get the results.

Thnaks for your help.

 

[koolkat77]

Don't edit your post. It often goes un-noticed.
Post update on a new reply.

 

[ToxicFyre]

Disk Check found no errors.
Now I'll try to figure out the hard stuff. Will post when done.
Thank you

 

[ToxicFyre]

Ok. The bios is now updated, and the SSD was already updated.
I reseted the bios to defaults and the overclocking is gone. However every time I boot I get a message: "CPU Fan 1 Error". (I have water cooling in my processor, but everything else is fans)
I can just dismiss it with F1 and boot normally, but it keeps bothering me.
Will post again when a crash appears.

Thank you so much. Toxic

 

[koolkat77]

Good to hear that the system is stable now.
I've requested a friend to take a look at your thread.

Please wait for a reply.

 

[Britton30]

Ok. The bios is now updated, and the SSD was already updated.
I reseted the bios to defaults and the overclocking is gone. However every time I boot I get a message: "CPU Fan 1 Error". (I have water cooling in my processor, but everything else is fans)
I can just dismiss it with F1 and boot normally, but it keeps bothering me.
Will post again when a crash appears.

Thank you so much. Toxic

That often happens with a water cooling system. You can plug in one of your fans to the CPU_FAN header or go to BIOS/UEFI fan control and set it so CPU fan monitoring is disabled or RPM limits ignored.

 

[ToxicFyre]

I just got a crash. This one is different though, it's not a Blue Screen, my computer completely froze (but I was able to move my mouse). When I ctrl-alt-deleted it said Preparing Security Options or something like that, and it stayed like that until I plugged the computer off.
It was as if everything stopped responding, my mouse had the loading sign.
This isn't new though, a few days ago I started getting these along with the BSODs but I don't get the BSODs anymore.
I would also like to mention that when I boot right back again, and windows just starts, it happens again in the same way. (The freezing) I have to wait a few minutes to boot the computer again for it to be usable, and not get freezes at start-up.

I got this while playing BF3, although it's fair to say that my computer crashes way less after I removed the overclocking.
Thanks so much for your help guys, I appreciate it with all my being.
Here's my new crashlog: