BSOD Win7

kj101 · 24 Apr 2013

please let me know if I need to provide any more additional information...

koolkat77 · 24 Apr 2013

Activation

Crashes indicate a possible issue with the windows installation. Please post this report before we begin:Windows Genuine and Activation Issue Posting Instructions

kj101 · 24 Apr 2013

Code:

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

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-J26FT-6HQBC-WVMR3
Windows Product Key Hash: IHKaPwwOEgyINuGKexRX9lcrX80=
Windows Product ID: 00371-OEM-9045082-12730
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {78419E66-EF66-4329-9CD1-29C9A943D4B7}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130318-1533
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>{78419E66-EF66-4329-9CD1-29C9A943D4B7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-WVMR3</PKey><PID>00371-OEM-9045082-12730</PID><PIDType>3</PIDType><SID>S-1-5-21-3607924691-3951151938-3609923115</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>D5468AT-ABA ALONPAV</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>5.27 </Version><SMBIOSVersion major="2" minor="4"/><Date>20080610000000.000000+000</Date></BIOS><HWID>D3603307018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HP-CPC</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, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00180-450-812730-02-1033-7601.0000-0762013
Installation ID: 019821210960188121299435502755021731290674197454117911
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: WVMR3
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 4/24/2013 10:21:06 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 3:19:2013 12:29
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MAAAAAEAAgABAAEAAQACAAAAAQABAAEAliumbZZ7humSAK5iMmQ+HA4rq3Xa2Sbp

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			HP-CPC		SLIC-CPC
  FACP			HP-CPC		SLIC-CPC
  HPET			HP-CPC		SLIC-CPC
  MCFG			HP-CPC		SLIC-CPC
  SSDT			HP-CPC		SLIC-CPC
  SLIC			HP-CPC		SLIC-CPC

Arc · 25 Apr 2013

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

kj101 · 26 Apr 2013

when it crashes do i post another crash report? How do I send in the results?

Arc · 26 Apr 2013

kj101 said:

when it crashes do i post another crash report? How do I send in the results?

By following the Blue Screen of Death (BSOD) Posting Instructions.

kj101 · 26 Apr 2013

here you go..

Arc · 26 Apr 2013

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Update the drivers for all your Logitech protects .... keyboard, mouse, camera, USB monitor, all..... from Logitech - Support & Software Downloads

Let us know the results.
_______________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff8800f05b710, fffff98004b50dc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff8800f05b710, The address in the driver's code where the error was detected.
Arg3: fffff98004b50dc0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0f05b710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0f05b710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff98004b50dc0

DEVICE_OBJECT: fffffa8006579b90

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80002cddb80 -- (!locks fffff80002cddb80)

Resource @ nt!PiEngineLock (0xfffff80002cddb80)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002cddb80
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002f674ec to fffff80002ad9c00

STACK_TEXT:  
fffff880`02fd30e8 fffff800`02f674ec : 00000000`000000c9 00000000`0000023b fffff880`0f05b710 fffff980`04b50dc0 : nt!KeBugCheckEx
fffff880`02fd30f0 fffff800`02f7158a : fffff800`02f65b00 fffff880`0f05b710 fffff980`04b50dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02fd3130 fffff800`02f72593 : 00000000`0000023b 00000000`c0000010 fffff980`04b50dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02fd3180 fffff800`02f72c52 : fffff980`04b50f20 fffff880`0f05b710 00000000`00000000 00000000`00000000 : nt!VfErrorReport1+0x63
fffff880`02fd3220 fffff800`02f67181 : fffffa80`063431c8 00000000`00000001 00000000`00000000 fffff980`04b50f20 : nt!ViGenericVerifyIrpStackUpward+0x62
fffff880`02fd3250 fffff800`02f73c3d : fffffa80`06558200 fffffa80`06343010 fffff980`04b50dc0 fffff980`04b50dc0 : nt!VfMajorVerifyIrpStackUpward+0x91
fffff880`02fd3290 fffff800`02f8561d : fffff980`04b50f20 fffff880`02fd3480 00000000`c0000010 fffff980`04b50f20 : nt!IovpCompleteRequest2+0xad
fffff880`02fd3300 fffff800`02add5c1 : fffff980`04b50f23 00000000`00000000 00000000`000000ff fffff800`02f68ffa : nt!IovpLocalCompletionRoutine+0x9d
fffff880`02fd3360 fffff800`02f7d2af : fffff980`04b50dc0 fffff880`0f065400 fffffa80`06579c00 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02fd3450 fffff800`02abeb56 : fffff880`00000013 fffff880`02fd3578 fffff980`04b50f20 fffffa80`06579ce0 : nt!IovCompleteRequest+0x19f
fffff880`02fd3520 fffff880`0f05ba0f : 00000000`00000000 fffffa80`06579ce0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`02fd3550 fffff880`0f05b7fb : 00000000`00000000 fffffa80`06579ce0 fffff980`04b50dc0 fffff880`02fd3600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`02fd3590 fffff800`02f83d26 : fffff980`00000002 fffff980`04b50dc0 00000000`00000002 fffff800`02f7f48e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`02fd3600 fffff800`02f82d52 : fffff980`04b50f68 00000000`00000002 fffffa80`0656bd10 fffffa80`06c16be0 : nt!IovCallDriver+0x566
fffff880`02fd3660 fffff800`02f83d26 : fffff980`04b50dc0 00000000`00000002 fffffa80`0656bbc0 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`02fd3690 fffff800`02f82e68 : fffff980`04b50dc0 fffffa80`0656bbc0 00000000`00000000 fffffa80`064e4010 : nt!IovCallDriver+0x566
fffff880`02fd36f0 fffff800`02f82f52 : fffffa80`04c46e30 00000000`00000001 fffffa80`04c46e30 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`02fd3760 fffff800`02f700bf : fffffa80`04c46b60 00000000`000007ff fffff800`02c185b8 fffff800`02e72fa9 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`02fd3800 fffff800`02b8c692 : fffffa80`04c46b60 00000000`00000000 ffffffff`ffffffff 00000000`00000016 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`02fd3830 fffff800`02ec756c : fffffa80`04c46b60 00000000`00000001 00000000`00000000 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`02fd3860 fffff800`02ec9164 : fffffa80`04c46b60 fffffa80`04c46b60 fffffa80`04c43010 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`02fd3950 fffff800`02ec964c : fffff800`02cdb500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x264
fffff880`02fd3bc0 fffff800`02bdc7f2 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`02fd3c10 fffff800`02ae3251 : fffff800`02bdc4f0 fffffa80`03ffe601 00000000`00000000 fffffa80`03ffe660 : nt!PnpDeviceActionWorker+0x302
fffff880`02fd3cb0 fffff800`02d77ede : 00000000`00000000 fffffa80`03ffe660 00000000`00000080 fffffa80`03fee9e0 : nt!ExpWorkerThread+0x111
fffff880`02fd3d40 fffff800`02aca906 : fffff880`009ea180 fffffa80`03ffe660 fffff880`009f4f40 083e0b06`38090534 : nt!PspSystemThreadStartup+0x5a
fffff880`02fd3d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

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

VistaKing · 26 Apr 2013

Code:

STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: HIDCLASS!HidpMajorHandler+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: HIDCLASS IMAGE_NAME: HIDCLASS.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a665 FAILURE_BUCKET_ID: X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0 BUCKET_ID: X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0 Followup: MachineOwner

Have you updated your USB drivers ?

Added: Didn't see Archie's post

kj101 · 26 Apr 2013

I have not