Blue Screen error with usbvideo.sys debug help please

Page 1 of 2 12 LastLast

  1. Posts : 11
    Windows 7 Home Premium 64bit
       #1

    Blue Screen error with usbvideo.sys debug help please


    I have the following blue screen error that is happening intermittently. It gives me an error with file usbvideo.sys.

    Any help would be greatly appreciated.

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    0x1000007e
    ffffffff`c0000005
    fffff880`0743301a
    fffff880`03177998
    fffff880`03177200

    I am running Windows 7 Home Premium 64bit.

    Thanks.
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    dtvgirl said:
    I have the following blue screen error that is happening intermittently. It gives me an error with file usbvideo.sys.

    Any help would be greatly appreciated.

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    0x1000007e
    ffffffff`c0000005
    fffff880`0743301a
    fffff880`03177998
    fffff880`03177200

    I am running Windows 7 Home Premium 64bit.

    Thanks.

    Hi dtvgirl

    Please read & follow what the link advises.....


    https://www.sevenforums.com/tutorials...en-forums.html
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    dtvgirl said:
    I have the following blue screen error that is happening intermittently. It gives me an error with file usbvideo.sys.

    Any help would be greatly appreciated.

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    0x1000007e
    ffffffff`c0000005
    fffff880`0743301a
    fffff880`03177998
    fffff880`03177200

    I am running Windows 7 Home Premium 64bit.

    Thanks.
    It is a memory exception but we cant tell you what caused it until we see the actual dmp file

    We really need the actual DMP file.

    If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    * Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.
      My Computer


  4. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Here is a copy of the dump file. Thanks.
      My Computer


  5. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    Also, it happens on startup just after the desktop is shown. It always happens like this and it's random. It occurs about once or twice a week.

    I have a Dell XPS Studio 1645 laptop and I received it March 3rd, 2010.
      My Computer


  6. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #6

    dtvgirl said:
    Also, it happens on startup just after the desktop is shown. It always happens like this and it's random. It occurs about once or twice a week.

    I have a Dell XPS Studio 1645 laptop and I received it March 3rd, 2010.

    Is your computer under warranty?
      My Computer


  7. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Yes.
      My Computer


  8. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #8

    In my humble opinion you should seek support / help under the terms of the warranty conditions.
    It is what I would do if I was having your problems with my new computer.
      My Computer


  9. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Dell is recommending that I get the video card replaced. I want to seek a professional opinion first before I send the computer in for repair.

    I only want to send it in for repair if that's what the problem really is. They didn't ask for too much information and based on the fact it is a problem with usbvideo.sys, they automatically said I need to have the video card replaced.

    They had me run some hardware system tests and everything was fine.

    They may be right but I want to verify first before sending it.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    dtvgirl said:
    Here is a copy of the dump file. Thanks.
    This one was caused by USBVIDEO.sys as suggested but there are two other factors. First old drivers, your storage driver (RAID) and several others.

    Then the USBVIDEO caused (or was caused by) a memory exception.

    If I were you I would do the following

    1-reinstall the USBVIDEO driver.

    2-run a memory test
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    3-Update the old drivers and if overclocking STOP

    4- run a system file check
    Run a system file check to verify and repair your system files.
    To do this type cmd in search, then right click to run as administrator, then
    SFC /SCANNOW

    read here for more information SFC /SCANNOW Command - System File Checker

    Let us know the results from the report at the end.

    Ken

    Old drivers needing updating
    Code:
    amdxata.sys        fffff880`011c7000    fffff880`011d2000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
    iaStor.sys        fffff880`0105d000    fffff880`01179000    0x0011c000    0x4a287aa4    6/4/2009 21:53:40                        
    dump_iaStor.sys        fffff880`02a00000    6800f881`02b1c000    0x680100010011c000    0x4a287aa4    6/4/2009 21:53:40                        
    CtClsFlt.sys        fffff880`05000000    30453ecd`0502a2a0    0x3045464d0002a2a0    0x4a35d6e1    6/15/2009 01:06:41                        
    PxHlpa64.sys        fffff880`01291000    fffff880`0129ce00    0x0000be00    0x4a416253    6/23/2009 19:16:35                        
    SynTP.sys        fffff880`0465c000    fffff880`046a5000    0x00049000    0x4a451503    6/26/2009 14:35:47                        
    risdpe64.sys        fffff880`05b4a000    fffff300`05b63000    0xfffffa8000019000    0x4a4b2d0d    7/1/2009 05:31:57                        
    rimspe64.sys        fffff880`05b63000    fffff880`05b7c000    0x00019000    0x4a4bf749    7/1/2009 19:54:49                        
    rixdpe64.sys        fffff880`05b7c000    fffff300`05bd2000    0xfffffa8000056000    0x4a4f2e74    7/4/2009 06:27:00
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\090710-15896-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
    Debug session time: Tue Sep  7 20:19:37.651 2010 (GMT-4)
    System Uptime: 0 days 0:00:41.711
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8800743301a, fffff88003177998, fffff88003177200}
    
    Probably caused by : usbvideo.sys ( usbvideo!LoadPowerLineFrequency+2ce )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800743301a, The address that the exception occurred at
    Arg3: fffff88003177998, Exception Record Address
    Arg4: fffff88003177200, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    usbvideo!LoadPowerLineFrequency+2ce
    fffff880`0743301a 448b4a44        mov     r9d,dword ptr [rdx+44h]
    
    EXCEPTION_RECORD:  fffff88003177998 -- (.exr 0xfffff88003177998)
    ExceptionAddress: fffff8800743301a (usbvideo!LoadPowerLineFrequency+0x00000000000002ce)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000044
    Attempt to read from address 0000000000000044
    
    CONTEXT:  fffff88003177200 -- (.cxr 0xfffff88003177200)
    rax=000000000000003c rbx=0000000000000000 rcx=fffff8a002d27900
    rdx=0000000000000000 rsi=fffffa80073fb510 rdi=fffff8a002c0ee60
    rip=fffff8800743301a rsp=fffff88003177bd0 rbp=fffffa8007f943e0
     r8=0000000000000002  r9=0000000000000040 r10=fffff80002e0f000
    r11=fffffa8003b69b60 r12=fffffa8007f88d60 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    usbvideo!LoadPowerLineFrequency+0x2ce:
    fffff880`0743301a 448b4a44        mov     r9d,dword ptr [rdx+44h] ds:002b:00000000`00000044=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000044
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b70e0
     0000000000000044 
    
    FOLLOWUP_IP: 
    usbvideo!LoadPowerLineFrequency+2ce
    fffff880`0743301a 448b4a44        mov     r9d,dword ptr [rdx+44h]
    
    BUGCHECK_STR:  0x7E
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    LAST_CONTROL_TRANSFER:  from fffff8800743663a to fffff8800743301a
    
    STACK_TEXT:  
    fffff880`03177bd0 fffff880`0743663a : fffffa80`00000010 fffffa80`00000002 ffffffff`8000093c fffffa80`073fb510 : usbvideo!LoadPowerLineFrequency+0x2ce
    fffff880`03177c50 fffff800`0317bc43 : 00000000`00000000 fffffa80`077a2f40 fffffa80`077a2f40 fffffa80`03b69b60 : usbvideo!PassiveWakeup+0x26
    fffff880`03177c80 fffff800`02e8c961 : fffff800`03024500 fffff800`0317bc20 fffffa80`03b69b60 00000000`00000000 : nt!IopProcessWorkItem+0x23
    fffff880`03177cb0 fffff800`03123c06 : 00000000`00520068 fffffa80`03b69b60 00000000`00000080 fffffa80`03b50b30 : nt!ExpWorkerThread+0x111
    fffff880`03177d40 fffff800`02e5dc26 : fffff880`02f67180 fffffa80`03b69b60 fffff880`02f720c0 00000000`00000031 : nt!PspSystemThreadStartup+0x5a
    fffff880`03177d80 00000000`00000000 : fffff880`03178000 fffff880`03172000 fffff880`031770d0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  usbvideo!LoadPowerLineFrequency+2ce
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: usbvideo
    
    IMAGE_NAME:  usbvideo.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc24
    
    STACK_COMMAND:  .cxr 0xfffff88003177200 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce
    
    BUCKET_ID:  X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce
    
    Followup: MachineOwner
    ---------
      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 09:47.
Find Us