Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while looking around computer error 0x0000000A


06 Jan 2013   #1

Windows 7 64bit
 
 
BSOD while looking around computer error 0x0000000A

Actually in my .zip I have 5 BSOD's but the most important are their from a new year, it happens to me a couple minutes ago while I was looking around computer, Youtube, Facebook etc.
It never happened before to me, that often.
After first "blue screen" I tried to restart computer, but after "loading image" it happened again, then I choiced "repair Windows etc." besides "run Windows normally" and after loading screen with "Windows is loading a files" there were another blue screen.

I'm sorry for my english, I know it's not perfect but I did my best.

I hope that you can help me.

Best Regards, duday.

My System SpecsSystem Spec
.

08 Jan 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to SevenForums.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004890028, b4052000, 91000145}

Probably caused by : AuthenticAMD

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004890028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b4052000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000091000145, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  LolClient.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdba88 fffff800`03603a37 : 00000000`00000124 00000000`00000000 fffffa80`04890028 00000000`b4052000 : nt!KeBugCheckEx
fffff880`02fdba90 fffff800`03194cc3 : 00000000`00000001 fffffa80`04663b00 00000000`00000000 fffffa80`04663b50 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdbad0 fffff800`036036fc : 00000000`00000728 fffffa80`04663b00 fffff880`02fdbe30 00000000`068c0700 : nt!WheaReportHwError+0x263
fffff880`02fdbb30 fffff800`0360304e : fffffa80`04663b00 fffff880`02fdbe30 fffffa80`04663b00 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdbc80 fffff800`035f6e8f : 00000000`000002ce 00000000`00000001 fffff880`02fdbeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdbcc0 fffff800`0308362c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fdbcf0 fffff800`03083493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdbe30 00000000`61484b12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`00718520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x61484b12


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

The above is a hardware error, see this link for additional information:
Stop 0x124 - what it means and what to try
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80074f74e0, fffff8800fcb6aa4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\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+ca1aa4 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80074f74e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fcb6aa4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+ca1aa4
fffff880`0fcb6aa4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04982b88 fffff880`04ca4000 : 00000000`00000116 fffffa80`074f74e0 fffff880`0fcb6aa4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04982b90 fffff880`04c77867 : fffff880`0fcb6aa4 fffffa80`05f91000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04982bd0 fffff880`04ca3e0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`074f74e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04982c80 fffff880`04d7303d : fffffa80`05ff2010 00000000`00000080 00000000`00000000 fffffa80`05f65280 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04982d00 fffff800`03161eca : 00000000`0d265c3d fffffa80`05fad060 fffffa80`0366ab30 fffffa80`05fad060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04982d40 fffff800`02eb89e6 : fffff880`02f63180 fffffa80`05fad060 fffff880`02f6dfc0 fffff880`01469a50 : nt!PspSystemThreadStartup+0x5a
fffff880`04982d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+ca1aa4
fffff880`0fcb6aa4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+ca1aa4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f347ad2

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f015000 fffff880`0fd33000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Feb 10 08:02:58 2012 (4F347AD2)
    CheckSum:         00D075A7
    ImageSize:        00D1E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
For TDR errors please check the troubleshooting method mentioned in this link:
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 4060008, fffffa8006c45280}

*** WARNING: Unable to verify timestamp for aswrdr2.sys
*** ERROR: Module load completed but symbols could not be loaded for aswrdr2.sys
GetPointerFromAddress: unable to read from fffff800030b6100
GetUlongFromAddress: unable to read from fffff800030b61c0
Probably caused by : fwpkclnt.sys ( fwpkclnt!WfpNamedPoolFree+19 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000004060008, Memory contents of the pool block
Arg4: fffffa8006c45280, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa8006c45280 Nonpaged pool

FREED_POOL_TAG:  Fwpp

BUGCHECK_STR:  0xc2_7_Fwpp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fb1be9 to fffff80002e84d40

STACK_TEXT:  
fffff880`05d0f6b8 fffff800`02fb1be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`04060008 : nt!KeBugCheckEx
fffff880`05d0f6c0 fffff880`017be1a1 : 00000000`00000000 fffff8a0`025fc6e0 fffffa80`06c45288 fffff880`017b6de4 : nt!ExDeferredFreePool+0x1201
fffff880`05d0f770 fffff880`017ecd68 : 00000000`00000000 fffffa80`06c45280 fffff8a0`02256c10 00000000`00000000 : fwpkclnt!WfpNamedPoolFree+0x19
fffff880`05d0f7a0 fffff880`017e746e : 00000000`00000000 fffff880`017e36a8 fffffa80`06bb53c0 fffff880`017e36a8 : fwpkclnt!FwppSessionDestroy+0x64
fffff880`05d0f7d0 fffff880`0454092b : fffffa80`06c45280 00000000`000007ff fffff8a0`025fe058 fffffa80`0659c040 : fwpkclnt!FwpmEngineClose0+0x42
fffff880`05d0f810 fffffa80`06c45280 : 00000000`000007ff fffff8a0`025fe058 fffffa80`0659c040 fffff880`04545978 : aswrdr2+0x492b
fffff880`05d0f818 00000000`000007ff : fffff8a0`025fe058 fffffa80`0659c040 fffff880`04545978 fffffa80`0366494c : 0xfffffa80`06c45280
fffff880`05d0f820 fffff8a0`025fe058 : fffffa80`0659c040 fffff880`04545978 fffffa80`0366494c fffffa80`0366494c : 0x7ff
fffff880`05d0f828 fffffa80`0659c040 : fffff880`04545978 fffffa80`0366494c fffffa80`0366494c fffff8a0`025fe030 : 0xfffff8a0`025fe058
fffff880`05d0f830 fffff880`04545978 : fffffa80`0366494c fffffa80`0366494c fffff8a0`025fe030 fffff8a0`025fe058 : 0xfffffa80`0659c040
fffff880`05d0f838 fffffa80`0366494c : fffffa80`0366494c fffff8a0`025fe030 fffff8a0`025fe058 fffff8a0`025f7030 : aswrdr2+0x9978
fffff880`05d0f840 fffffa80`0366494c : fffff8a0`025fe030 fffff8a0`025fe058 fffff8a0`025f7030 00000000`00000000 : 0xfffffa80`0366494c
fffff880`05d0f848 fffff8a0`025fe030 : fffff8a0`025fe058 fffff8a0`025f7030 00000000`00000000 fffff8a0`025fc8b0 : 0xfffffa80`0366494c
fffff880`05d0f850 fffff8a0`025fe058 : fffff8a0`025f7030 00000000`00000000 fffff8a0`025fc8b0 fffff8a0`025fe060 : 0xfffff8a0`025fe030
fffff880`05d0f858 fffff8a0`025f7030 : 00000000`00000000 fffff8a0`025fc8b0 fffff8a0`025fe060 fffff800`0311d4aa : 0xfffff8a0`025fe058
fffff880`05d0f860 00000000`00000000 : fffff8a0`025fc8b0 fffff8a0`025fe060 fffff800`0311d4aa 00000000`00000000 : 0xfffff8a0`025f7030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fwpkclnt!WfpNamedPoolFree+19
fffff880`017be1a1 48b8faaddbbafaaddbba mov rax,0BADBADFABADBADFAh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fwpkclnt!WfpNamedPoolFree+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fwpkclnt

IMAGE_NAME:  fwpkclnt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eb4a31c

FAILURE_BUCKET_ID:  X64_0xc2_7_Fwpp_fwpkclnt!WfpNamedPoolFree+19

BUCKET_ID:  X64_0xc2_7_Fwpp_fwpkclnt!WfpNamedPoolFree+19

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

Avast antivirus has been contributing to your crashes. Please uninstall it using its removal tool.
Use Microsoft security essentials in its place. Make a full scan also.
avast! Uninstall Utility | Download aswClear for avast! Removal
Microsoft Security Essentials - Microsoft Windows
Perform a clean boot:
Troubleshoot Application Conflicts by Performing a Clean Startup
Run the System File Checker:
SFC /SCANNOW Command - System File Checker
Please follow all steps in the 124 link.

Hope this helps for now.
My System SpecsSystem Spec
14 Mar 2013   #3

Windows 7 64bit
 
 

Hi again!

I think every solution above helps me a lot but after a while, maybe 1-2 weeks i'm getting a rain of bluescreens. I didn't count them but i think it's like 100 BSODs. Almost every has other problem. But in my zip i have only 2 bluescreens idk why, maybe i did bad configuration of dumps.
Even while i did my first version of this post I had another bsod.

I hope you guys will help me again.
My System SpecsSystem Spec
.


14 Mar 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Please update your BIOS:
Code:
Wersja/data systemu BIOS    American Megatrends Inc. 6.13, 2010-09-08
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Note   Note
Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

Check for heat issues:Perform a System File Check to check the integrity of all protected Windows 7 :
  1. Click on the start
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type
    Code:
    SFC /scannow
Full tutorial here:Then enable driver verifier and see if it catches any misbehaving drivers:
My System SpecsSystem Spec
14 Mar 2013   #5

Windows 7 64bit
 
 

I have a problem to find good BIOS update, my motherboard is this one:
Motherboard Specifications, M2N68-LA (Narra6) | HP® Support
Looks exactly same but i can't find BIOS drivers to M2N68-LA to others like M2N68, M2N68-VM etc. they have many drivers.
I'll try to find some information at the start of BIOS.

Heat system is ok.
Log from HWMonitor attached.

SFC done, there says that some of system files cannot be repaired and details are in CBS.log (attached - I needed to do this in .zip 'cause it says i cannot upload a text file with 4mb)

Now I'll try the driver verifier and tonight as you said before going to bed, I'll do a RAM test.

Thank you very much for any help!
My System SpecsSystem Spec
14 Mar 2013   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Ok, take your time with the BIOS.

Tell me have you followed the steps in the 124 and 116 troubleshooting links?
My System SpecsSystem Spec
14 Mar 2013   #7

Windows 7 64bit
 
 

124 I'm pretty sure that yes i did it but with 116 I had a problems with that troubleshooting.

I updated my last post.
My System SpecsSystem Spec
14 Mar 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

I'm calling my friend to take a look at that CBS log.

Let us know the results from memtest and driver verifier later.
My System SpecsSystem Spec
14 Mar 2013   #9

Windows 7 64bit
 
 

Thank you!

I'll let you know after 24 hours or something like that.
My System SpecsSystem Spec
14 Mar 2013   #10

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

One critical line in the CBS report states....
"Repairing 678 (0x00000000000002a6) components"

An appreciable part of your OS has gone AWOL for some reason - there is no point in attempting to manually repair the damage, as it almost certainly extends further than the report shows.

You will need to do at least a repair install - and more likely a clean install - to fix the problems.
My System SpecsSystem Spec
Reply

 BSOD while looking around computer error 0x0000000A




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:55 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33