BSOD while looking around computer error 0x0000000A

NoelDP · 15 Mar 2013

Please post a new MGADiag report - no-one will respond until we are certain that the installation is genuine.

duday · 15 Mar 2013

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-7M8J4-4K8B2-T2XVD
Windows Product Key Hash: AjYMrgikGZcX4bh/dis/s7Zx8Ss=
Windows Product ID: 00359-OEM-9812096-04286
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {2FD56953-D867-4E53-A4D9-5CFA562FBBA9}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130104-1431
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{2FD56953-D867-4E53-A4D9-5CFA562FBBA9}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-T2XVD</PKey><PID>00359-OEM-9812096-04286</PID><PIDType>8</PIDType><SID>S-1-5-21-1576101520-3596118410-1190433730</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>G5245nl</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>6.13   </Version><SMBIOSVersion major="2" minor="5"/><Date>20100908000000.000000+000</Date></BIOS><HWID>83F93407018400F2</HWID><UserLCID>0413</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00196-120-904286-02-1043-7601.0000-0732013
Installation ID: 008884362751890684594433504265996800603371379166740023
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: T2XVD
License Status: Initial grace period
Time remaining: 42060 minute(s) (29 day(s))
Remaining Windows rearm count: 3
Trusted time: 15-3-2013 14:11:04

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: KgAAAAEAAAABAAEAAQABAAAAAQABAAEA6GHcYmKIVtEu2YAg6J42W0Ia

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			HPQOEM		SLIC-CPC
  FACP			HPQOEM		SLIC-CPC
  SRAT			AMD   		FAM_F_10
  HPET			HPQOEM		SLIC-CPC
  MCFG			HPQOEM		SLIC-CPC
  OEMB			HPQOEM		SLIC-CPC
  SLIC			HPQOEM		SLIC-CPC
  SSDT			HPQOEM		SLIC-CPC

NoelDP · 15 Mar 2013

That's fine :)
Don't forget to activate it!

duday · 15 Mar 2013

Hi there again!
Don't worry I will activate it tomorrow :)

I just had a rain of bluescreens of death, for real!
Very often it happens when I'm watching some videos on youtube etc.
After this BSOD I couldn't launch the system, i just saw for a while some blue screen and it reboot again, it was like 5-6 times in a row, then I just launched a Setup Repair, it couldn't help me either.
I had another BSOD with same error as last time.

Update1: While ago whole PC just crashed, just everything stood still, couldn't do anything.

Update2: Okay guys, it's pretty annoying. 2 minutes ago I just reboot my PC again after another BSOD, but I wrote such a things that I'm too lazy to write it again in the same way. I really appreciate what you already did for me, for your help. I'm really glad that I get on your website and could get any help from you. I will attach another BSOD's but if it's still wouldn't work, I'll just take my PC to the service.
I did notice maybe not so important thing, but I had never a bluescreen when I was playing some games (League of Legends, Starcraft 2, Call of Duty Black Ops etc.).
I hope you guys could help me as soon as possible.
Cheers.

koolkat77 · 15 Mar 2013

Seems like hardware errors continue:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff960001660cb, fffff880069e2030, 0}

Probably caused by : hardware ( win32k!HANDLELOCK::vLockHandle+27 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff960001660cb, Address of the instruction which caused the bugcheck
Arg3: fffff880069e2030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!HANDLELOCK::vLockHandle+27
fffff960`001660cb 1e              ???

CONTEXT:  fffff880069e2030 -- (.cxr 0xfffff880069e2030)
rax=fffff900c073d770 rbx=00000000069e3a0c rcx=fffff880069e2a50
rdx=00000000000007e4 rsi=0000000000000ad2 rdi=0000000000000000
rip=fffff960001660cb rsp=fffff880069e2a10 rbp=fffff900c02103b0
 r8=0000000000000000  r9=0000000000000ad2 r10=fffffa800567fd70
r11=fffffa8005e51510 r12=0000000000000000 r13=ffffffff97011092
r14=0000000000000001 r15=fffff880069e2be8
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
win32k!HANDLELOCK::vLockHandle+0x27:
fffff960`001660cb 1e              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!HANDLELOCK::vLockHandle+27
fffff960`001660cb 1e              ???

LAST_CONTROL_TRANSFER:  from fffff960002c770b to fffff960001660cb

STACK_TEXT:  
fffff880`069e2a10 fffff960`002c770b : 00000000`000007e4 fffff900`c0132b30 00000000`00000001 00000000`00000004 : win32k!HANDLELOCK::vLockHandle+0x27
fffff880`069e2a50 fffff960`0027d324 : fffff900`c0132b30 fffff900`c01d5370 fffff900`c01d5370 fffff900`c0841a90 : win32k!DEC_SHARE_REF_CNT+0x3b
fffff880`069e2ab0 fffff960`001893d5 : ffffffff`97011092 fffff880`069e2ca0 00000000`00000001 fffff880`069e2ca0 : win32k!GreGetDxRgn+0x294
fffff880`069e2b50 fffff800`02ecbed3 : fffffa80`05e51510 00000000`00000000 00000000`00000020 00000000`00000000 : win32k!NtUserHwndQueryRedirectionInfo+0x249
fffff880`069e2c20 00000000`77a23d9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0333f518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a23d9a


FOLLOWUP_IP: 
win32k!HANDLELOCK::vLockHandle+27
fffff960`001660cb 1e              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HANDLELOCK::vLockHandle+27

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880069e2030 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80049f8028, b671c000, 135}

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: fffffa80049f8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b671c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, 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:  MsMpEng.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdba88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


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
---------

3: kd> !errrec fffffa80049f8028
===============================================================================
Common Platform Error Record @ fffffa80049f8028
-------------------------------------------------------------------------------
Record Id     : 01ce21e055433d81
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/16/2013 0:57:09 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80049f80a8
Section       @ fffffa80049f8180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f53
Processor ID  : 0x0000000000000003

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80049f80f0
Section       @ fffffa80049f8240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000003
CPU Id        : 53 0f 10 00 00 08 04 03 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80049f8240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80049f8138
Section       @ fffffa80049f82c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)
  Status      : 0xb671c00000000135
  Address     : 0x00000001169a49c0
  Misc.       : 0x0000000000000000

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

How to Test and Diagnose RAM Issues with Memtest86+

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.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

duday · 16 Mar 2013

As I said in my last posts, I already did the RAM test, after 8 passes I didn't notice any error there.
I just had another BSOD. Same problem. At monday I'll take my PC to the computer service.

Thanks a lot for help!