BSOD Bugcheck error 0x0000000a event id 1001 help.

Hello ive been getting crashes with as the title states a bugcheck error. any help trying to figure out whats causing this would be appreciated. im using avg antivirus and malwarebytes to protect my pc. cheers!

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          20/03/2014 21:55:07
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Nabz-PC
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff8000308593c). A dump was saved in: C:\Windows\Minidump\032014-8970-01.dmp. Report Id: 032014-8970-01.
Event Xml:
<Event xmlns="">
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <TimeCreated SystemTime="2014-03-20T21:55:07.000000000Z" />
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Security />
    <Data Name="param1">0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff8000308593c)</Data>
    <Data Name="param2">C:\Windows\Minidump\032014-8970-01.dmp</Data>
    <Data Name="param3">032014-8970-01</Data>


Thanks for the dumps!

We have various bug checks:


This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.


This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

If we take a look at the call stack:

0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`044ba4f8 fffff800`03092169 : 00000000`0000000a fffff800`0000003d 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`044ba500 fffff800`03090de0 : 00000000`00000000 fffff880`0f23dda5 fffffa80`06ffa000 fffffa80`0001b6ff : nt!KiBugCheckDispatch+0x69
fffff800`044ba640 fffff800`0000003d : fffffa80`00000000 fffff880`0f1f2c0e 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260 (TrapFrame @ fffff800`044ba640)
fffff800`044ba7d8 fffffa80`00000000 : fffff880`0f1f2c0e 00000000`00000000 00000000`00000001 fffffa80`08dd72f0 : 0xfffff800`0000003d
fffff800`044ba7e0 fffff880`0f1f2c0e : 00000000`00000000 00000000`00000001 fffffa80`08dd72f0 00000000`00000000 : 0xfffffa80`00000000
fffff800`044ba7e8 00000000`00000000 : 00000000`00000001 fffffa80`08dd72f0 00000000`00000000 fffffa80`09283ba0 : nvlddmkm+0x1a0c0e

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1a0c0e )

^^ nVidia video driver.


This indicates that a kernel-mode program generated an exception which the error handler did not catch.


This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff88004a9fd8d, fffff8800333f3b8, fffff8800333ec10}

^^ The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred:

2: kd> .exr 0xfffff8800333f3b8
ExceptionAddress: fffff88004a9fd8d (athrx+0x0000000000250d8d)
   ExceptionCode: c0000005 (Access violation)

^^ The violation occurred in athrx.sys which is the Atheros network adapter driver.


1. Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes as it's likely causing NETBIOS conflicts:

AVG removal -


2. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

3. Ensure your network drivers (specifically Atheros) are up to date via Gigabyte's website.



Debugger/Reverse Engineer.

32 people found this reply helpful


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated December 3, 2020 Views 22,367 Applies to: