Random BSODs playing videos, idling, start up, etc..

Page 1 of 2 12 LastLast

  1. Posts : 7
    Wondows 7 Home 64 bit
       #1

    Random BSODs playing videos, idling, start up, etc..


    Hi,

    I'm having a few problems with my pc since a few months.
    Its getting heavier since a month or two.

    I'm getting lots of crashes, mostly randoms.

    It can crash while viewing a video (vlc or online browsing), While playing music (foobar), at start up (crashes 30 seconds or more after the whole log on has been done).

    Yesterday it has crashed while idling and the internal speakers made continious short small beeps (Happened only once)

    Sometimes the video card (GeForce GTS 240) makes lots of noise.

    I updated everything i could (video driver), but i havent done the bios.

    Thanks a lot!

    Is Windows 7 Home Basic
    - x86 (32-bit) or x64 ? x64
    - the original installed OS on the system? Yes
    - an OEM or full retail version? OEM
    - OEM = came pre-installed on system
    - Full Retail = you purchased it from retailer

    - What is the age of system (hardware)? 2 years and a half
    - What is the age of OS installation (have you re-installed the OS?) 2 years and a half
      My Computer


  2. Posts : 7
    Wondows 7 Home 64 bit
    Thread Starter
       #2

    Here's an update of my minidump.

    I ran driver verifier on all non-microsoft driver and had crashes at every start up (after all applications loaded).

    I had to disable it in safe mode.

    Im not too good with all this but HIDCLASS.SYS was comming out of this in the BSODs screen.

    Thanks!
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [K:\BSODDmpFiles\yeffiely\Windows_NT6_BSOD_jcgriff2\013012-28891-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329c670 Debug session time: Mon Jan 30 10:37:35.308 2012 (GMT-7) System Uptime: 0 days 0:02:07.369 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {23b, fffff88006f11710, fffff9801f0f4dc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) Followup: MachineOwner --------- 4: 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: fffff88006f11710, The address in the driver's code where the error was detected. Arg3: fffff9801f0f4dc0, IRP address. Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0xc9_23b DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23b FAULTING_IP: HIDCLASS!HidpMajorHandler+0 fffff880`06f11710 48895c2410 mov qword ptr [rsp+10h],rbx FOLLOWUP_IP: HIDCLASS!HidpMajorHandler+0 fffff880`06f11710 48895c2410 mov qword ptr [rsp+10h],rbx IRP_ADDRESS: fffff9801f0f4dc0 DEVICE_OBJECT: fffffa800ae9f500 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LOCK_ADDRESS: fffff800032d2b80 -- (!locks fffff800032d2b80) Resource @ nt!PiEngineLock (0xfffff800032d2b80) 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 : 0xfffff800032d2b80 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff8000355d3dc to fffff800030d3c40 STACK_TEXT: fffff880`0337e0e8 fffff800`0355d3dc : 00000000`000000c9 00000000`0000023b fffff880`06f11710 fffff980`1f0f4dc0 : nt!KeBugCheckEx fffff880`0337e0f0 fffff800`0356747a : fffff800`0355b9f0 fffff880`06f11710 fffff980`1f0f4dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`0337e130 fffff800`03568483 : 00000000`0000023b 00000000`c0000010 fffff980`1f0f4dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`0337e180 fffff800`03568b42 : fffff980`1f0f4f20 fffff880`06f11710 00000000`00000000 00000000`00000000 : nt!VfErrorReport1+0x63 fffff880`0337e220 fffff800`0355d071 : fffffa80`0aa971c8 00000000`00000001 00000000`00000000 fffff980`1f0f4f20 : nt!ViGenericVerifyIrpStackUpward+0x62 fffff880`0337e250 fffff800`03569b2d : fffffa80`0a6c5610 fffffa80`0aa97010 fffff980`1f0f4dc0 fffff980`1f0f4dc0 : nt!VfMajorVerifyIrpStackUpward+0x91 fffff880`0337e290 fffff800`0357b50d : fffff980`1f0f4f20 fffff880`0337e480 00000000`c0000010 fffff980`1f0f4f20 : nt!IovpCompleteRequest2+0xad fffff880`0337e300 fffff800`030d7021 : fffff980`1f0f4f23 00000000`00000000 00000000`000000ff fffff800`0355eeea : nt!IovpLocalCompletionRoutine+0x9d fffff880`0337e360 fffff800`0357319f : fffff980`1f0f4dc0 fffff880`06f1b400 fffffa80`0ae9f600 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`0337e450 fffff800`030b9876 : fffff880`00000013 fffff880`0337e578 fffff980`1f0f4f20 fffffa80`0ae9f650 : nt!IovCompleteRequest+0x19f fffff880`0337e520 fffff880`06f11a0f : 00000000`00000000 fffffa80`0ae9f650 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16 fffff880`0337e550 fffff880`06f117fb : 00000000`00000000 fffffa80`0ae9f650 fffff980`1f0f4dc0 fffff880`0337e600 : HIDCLASS!HidpIrpMajorDefault+0x8b fffff880`0337e590 fffff800`03579c16 : fffff980`00000002 fffff980`1f0f4dc0 00000000`00000002 fffff800`0357537e : HIDCLASS!HidpMajorHandler+0xeb fffff880`0337e600 fffff800`03578c42 : fffff980`1f0f4f68 00000000`00000002 fffffa80`0ae9f3f0 fffffa80`0a9cba00 : nt!IovCallDriver+0x566 fffff880`0337e660 fffff800`03579c16 : fffff980`1f0f4dc0 00000000`00000002 fffffa80`0ae9f2a0 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62 fffff880`0337e690 fffff800`03578d58 : fffff980`1f0f4dc0 fffffa80`0ae9f2a0 00000000`00000000 fffffa80`0a7514d0 : nt!IovCallDriver+0x566 fffff880`0337e6f0 fffff800`03578e42 : fffffa80`0a571cc0 fffffa80`06d948e0 fffffa80`0a571cc0 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8 fffff880`0337e760 fffff800`03565faf : fffffa80`0aa97d90 00000000`000007ff fffff800`0320d5b8 fffff800`03469899 : nt!VfWmiTestStartedPdoStack+0x72 fffff880`0337e800 fffff800`031809d2 : fffffa80`0aa97d90 00000000`00000000 00000000`00000010 00000000`00010282 : nt!VfMajorTestStartedPdoStack+0x5f fffff880`0337e830 fffff800`034bde5c : fffffa80`0aa97d90 fffffa80`06d948e0 00000000`00000001 00000000`00000000 : nt!PpvUtilTestStartedPdoStack+0x12 fffff880`0337e860 fffff800`034bfa54 : fffffa80`0aa97d90 fffffa80`0aa97d90 fffffa80`06d948e0 00000000`00000001 : nt!PipProcessStartPhase3+0x55c fffff880`0337e950 fffff800`034c0018 : fffff800`032d0500 00000000`00000000 00000000`00000010 fffff800`034bff80 : nt!PipProcessDevNodeTree+0x264 fffff880`0337ebc0 fffff800`031d08e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98 fffff880`0337ec10 fffff800`030de001 : fffff800`031d05c0 fffff800`033ca901 fffffa80`06d7fb00 fffff800`032836a0 : nt!PnpDeviceActionWorker+0x327 fffff880`0337ecb0 fffff800`0336efee : 00000000`00000000 fffffa80`06d7fb60 00000000`00000080 fffffa80`06d59040 : nt!ExpWorkerThread+0x111 fffff880`0337ed40 fffff800`030c55e6 : fffff880`03186180 fffffa80`06d7fb60 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0337ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+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 ---------
    2. Loading Dump File [K:\BSODDmpFiles\yeffiely\Windows_NT6_BSOD_jcgriff2\122311-18876-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305f670 Debug session time: Fri Dec 23 09:44:28.528 2011 (GMT-7) System Uptime: 0 days 0:00:50.463 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {5, fffffa8008caa1a0, 80863b3c, fffffa800946dc48} Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa8008caa1a0, Device extension pointer of the host controller Arg3: 0000000080863b3c, PCI Vendor,Product id for the controller Arg4: fffffa800946dc48, Pointer to Endpoint data structure Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88004484f7e to fffff80002e96c40 STACK_TEXT: fffff880`031aea58 fffff880`04484f7e : 00000000`000000fe 00000000`00000005 fffffa80`08caa1a0 00000000`80863b3c : nt!KeBugCheckEx fffff880`031aea60 fffff880`0444bfac : 00000000`bd779180 fffffa80`08cab6a0 00000000`00000000 fffffa80`0946ddc0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a fffff880`031aeaa0 fffff880`0444bb73 : fffffa80`0946dc48 fffffa80`08e18a00 fffffa80`0946ddc0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c fffff880`031aeb30 fffff880`04450d91 : fffffa80`0946dc48 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53 fffff880`031aeb70 fffff880`04458e8b : 00000000`00000002 fffffa80`08caa1a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41 fffff880`031aebb0 fffff880`0445d9d1 : 00000000`00000040 00000000`00000004 fffffa80`0946da00 fffffa80`08caa050 : USBPORT!MPf_PollEndpoint+0x9b fffff880`031aebe0 fffff880`04469077 : fffffa80`08caa1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff880`031aec40 fffff880`04459f89 : fffffa80`08caa050 00000000`00000000 fffffa80`08caaa02 fffffa80`08caaa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff880`031aeca0 fffff800`02ea20ac : fffff880`03186180 fffffa80`08caaa18 fffffa80`08caaa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`031aecd0 fffff800`02e8e96a : fffff880`03186180 fffff880`031910c0 00000000`00000000 fffff880`04459db0 : nt!KiRetireDpcList+0x1bc fffff880`031aed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: usbehci!EHCI_sMode_PollEndpointSlot+6c fffff880`0444bfac 4533c9 xor r9d,r9d SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbehci IMAGE_NAME: usbehci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00 FAILURE_BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c Followup: MachineOwner ---------
    1. HIDCLASS.SYS is usually blamed when an external device (external hard drive, gaming device, mouse, keyboard, etc) is plugged into the computer.
    2. Appears to be a usb device that you have plugged in causing the crashes, or possibly a usb device that is lingering on the system.

    Disable Driver Verifier. Then start with the steps outlined for USB Driver - General Fix for Problems and post back when finished.
      My Computer


  4. Posts : 7
    Wondows 7 Home 64 bit
    Thread Starter
       #4

    Alright, i did uninstall all the faded drivers except for one that just wouldnt disapear, RAS asynch card, under network card (Sorry for the bad term translation since my OS isnt installed in english). I also deleted INFCACHE.1.

    Whats next?
    Should i try reinstalling my usb drivers or run the driver verifier again?

    Thanks a lot for your help.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Install the USB drivers for only the essential items (mouse, keyboard, etc.) and then let it run for a while to test stability. Then install one USB driver at a time, test stability after each, and determine if one of your other devices is causing the crashes.
      My Computer


  6. Posts : 7
    Wondows 7 Home 64 bit
    Thread Starter
       #6

    Too bad i dont think uninstalling all unused drivers did the thing. I still had a few crashes today. Also, i had a crash each time i tried to run the Windows Performance Index... Also the internal speakers made continious short small beeps again when i tried rebooting.
    Thanks!
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    Alright, I was hoping it was just the USB issue. Short beeps typically mean bad hardware of some kind; you would have to call the vendor to find out what exactly your beeps mean. The number of beeps would be significant. We can do hardware testing with software in Windows if you'd like, but it would be better if you can find out what the beeps signify.



    Did you determine which hardware was causing problems?
    Last edited by writhziden; 22 Feb 2012 at 12:30. Reason: Update?
      My Computer


  8. Posts : 7
    Wondows 7 Home 64 bit
    Thread Starter
       #8

    Actually i havent had a crash in a week,
    I updated my video card and removed OpenOffice quick start up.
    Im kinda convinced the problem's the video card.
    Thanks
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    You're welcome. Glad you tracked it down. :)
      My Computer


  10. Posts : 7
    Wondows 7 Home 64 bit
    Thread Starter
       #10

    Bad news... I had a run of about two weeks without a single crash. Then i had 3 crashes de same night, then another week without a crash, then i had about like 4 or 5 crashes in 2 days. I really dont know what to do. i uploaded my new BSOD dump if you guys can see anything new in there. Thanks!
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 20:20.
Find Us