help with bluescreen error, hardware issue?

Page 2 of 3 FirstFirst 123 LastLast

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

    Code:
    
    Loading Dump File [F:\Kingston\BSODDmpFiles\beagrie07\Windows_NT6_BSOD_jcgriff2\020512-54272-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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`03053000 PsLoadedModuleList = 0xfffff800`03298670
    Debug session time: Sun Feb  5 15:07:45.438 2012 (GMT-7)
    System Uptime: 0 days 0:01:57.312
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {224, fffff88006d47710, fffff9801799a9d0, ffffffffc00000bb}
    
    Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
    	IRP's IoStatus.Status field.
    Arg2: fffff88006d47710, The address in the driver's code where the error was detected.
    Arg3: fffff9801799a9d0, IRP address.
    Arg4: ffffffffc00000bb, Expected status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_224
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224
    
    FAULTING_IP: 
    HIDCLASS!HidpMajorHandler+0
    fffff880`06d47710 48895c2410      mov     qword ptr [rsp+10h],rbx
    
    FOLLOWUP_IP: 
    HIDCLASS!HidpMajorHandler+0
    fffff880`06d47710 48895c2410      mov     qword ptr [rsp+10h],rbx
    
    IRP_ADDRESS:  fffff9801799a9d0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  ts3client_win6
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800035593dc to fffff800030cfc40
    
    STACK_TEXT:  
    fffff880`0a1ae638 fffff800`035593dc : 00000000`000000c9 00000000`00000224 fffff880`06d47710 fffff980`1799a9d0 : nt!KeBugCheckEx
    fffff880`0a1ae640 fffff800`0356347a : fffff800`035579f0 fffff880`06d47710 fffff980`1799a9d0 ffffffff`c00000bb : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0a1ae680 fffff800`035643f3 : fffff880`06d47710 fffffa80`0a7270c8 ffffffff`c00000bb 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0a1ae6d0 fffff800`0356f759 : 00000000`00000008 fffffa80`0a727010 fffffa80`0a7270c8 00000000`00000000 : nt!VfErrorReport4+0x83
    fffff880`0a1ae7c0 fffff800`0356fb63 : fffffa80`0a727010 00000000`00000002 fffffa80`096f3b70 fffff980`1799a9d0 : nt!IovpCallDriver2+0x179
    fffff880`0a1ae820 fffff800`03575c2e : fffff980`1799a9d0 fffff980`1799a9d0 00000000`00000002 fffffa80`096f3b70 : nt!VfAfterCallDriver+0x353
    fffff880`0a1ae870 fffff800`033eaa97 : fffffa80`08708850 fffff880`0a1aeb60 fffffa80`08708850 fffffa80`0a727010 : nt!IovCallDriver+0x57e
    fffff880`0a1ae8d0 fffff800`033eb2f6 : fffff683`ff7d7590 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`0a1aea00 fffff800`030ceed3 : fffffa80`0a4f89d0 0000007f`ffffffff fffffa80`0a644060 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
    fffff880`0a1aea70 00000000`7767138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`05e6e5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767138a
    
    
    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_224_VRF_HIDCLASS!HidpMajorHandler+0
    
    BUCKET_ID:  X64_0xc9_224_VRF_HIDCLASS!HidpMajorHandler+0
    
    Followup: MachineOwner
    ---------
    Caused by driver verifier (which is a good thing). Points to Human Interface Devices (USB, Bluetooth, keyboard, mouse, gaming devices, etc). Disable Verifier for the time being. Start with USB Driver - General Fix for Problems to fix any USB related conflicts. Once finished with those steps, re-enable Verifier as before.
    Last edited by writhziden; 05 Feb 2012 at 17:56. Reason: Re-enable Verifier after resolving USB conflicts.
      My Computer


  2. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #12

    I've disabled some HID-Compliant Devices before as they were conflicting with a game I was playing. I'm glad it was that rather than something else!
      My Computer


  3. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #13

    I ran the memtest for a bit last night and managed 2 passes, no errors.

    I was watching a movie earlier though and when I closed VLC I got a BSOD.

    I uploaded the results again.
      My Computer


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

    Code:
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\BSODDmpFiles\beagrie07\Windows_NT6_BSOD_jcgriff2\020612-9375-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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`03019000 PsLoadedModuleList = 0xfffff800`0325e670
    Debug session time: Mon Feb  6 08:38:44.640 2012 (GMT-7)
    System Uptime: 0 days 3:16:11.404
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 213177, 2, 10d48b}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 0000000000213177, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 000000000010d48b, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  vlc.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000311ed7c to fffff80003095c40
    
    STACK_TEXT:  
    fffff880`0b339088 fffff800`0311ed7c : 00000000`0000004e 00000000`00000099 00000000`00213177 00000000`00000002 : nt!KeBugCheckEx
    fffff880`0b339090 fffff800`0303d9e6 : 00000000`00000000 fffffa80`0102e730 0000000f`ffffffff 00000000`00000000 : nt!MiBadShareCount+0x4c
    fffff880`0b3390d0 fffff800`0308b671 : b6b00000`00000000 fffff680`0004ace0 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x336d1
    fffff880`0b339150 fffff800`03082e62 : fffffa80`0908e700 fffff880`00000000 fffffa80`0d6d4b30 fffffa80`0d6d4ec8 : nt!MiDecommitPages+0x1a1
    fffff880`0b3399e0 fffff800`03094ed3 : ffffffff`ffffffff 00000000`0472e810 00000000`0472e808 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
    fffff880`0b339ae0 00000000`77af14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0472e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77af14fa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`0311ed7c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    Part 2, 3.
    Let it run until at least 7 passes are completed, or errors are found (whichever comes first). The longer you run it, the better.
      My Computer


  5. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #15

    Ok, I ran it last night and managed 7 passes. What to do now?
      My Computer


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

    Windows memory diagnostic tool for five passes. Other than that, keep running normally (with Verifier enabled on non-Microsoft drivers) until you get a few crashes to identify any patterns.
      My Computer


  7. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #17

    Done the Windows Memory Diagnostic, no problems. I'll keep running for now see if I get a problem.
      My Computer


  8. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #18

    Hi, I had anoher blue screen, at the time I was exiting Audacity and it happened.

    I've uploaded the zip again.
      My Computer


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

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\BSODDmpFiles\beagrie07\BSOD 13-12-2012\Windows_NT6_BSOD_jcgriff2\021312-9141-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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`0301e000 PsLoadedModuleList = 0xfffff800`03263670
    Debug session time: Mon Feb 13 06:42:42.735 2012 (GMT-7)
    System Uptime: 0 days 2:08:12.499
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 3d295, 0, 106315}
    
    Unable to load image \SystemRoot\system32\DRIVERS\symsnap.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for symsnap.sys
    *** ERROR: Module load completed but symbols could not be loaded for symsnap.sys
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 000000000003d295, page frame number
    Arg3: 0000000000000000, current page state
    Arg4: 0000000000106315, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  audacity.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80003123d7c to fffff8000309ac40
    
    STACK_TEXT:  
    fffff880`0a58aa48 fffff800`03123d7c : 00000000`0000004e 00000000`00000099 00000000`0003d295 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0a58aa50 fffff800`030514a1 : 00000000`0003d295 00000000`002004d1 fffffa80`0600e730 00000000`0003d695 : nt!MiBadShareCount+0x4c
    fffff880`0a58aa90 fffff800`03069532 : 00000000`00000000 fffffa80`08c71900 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2d885
    fffff880`0a58ab80 fffff880`0169351b : fffffa80`06ba20c8 00000000`00000000 fffff880`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
    fffff880`0a58abf0 fffff880`016b4033 : fffff880`0a58b460 fffff8a0`04bcf010 fffff8a0`04514bc0 fffff880`0a58aef8 : Ntfs!NtfsDeleteFile+0x57b
    fffff880`0a58ae70 fffff880`01622cc9 : fffffa80`00000000 fffff8a0`040418c8 fffff880`0a58b3c0 00000000`00006000 : Ntfs!NtfsCommonCleanup+0x1653
    fffff880`0a58b280 fffff800`030a7618 : fffff880`0a58b3c0 00000000`00000000 00000000`073cdbb0 fffff880`01522dca : Ntfs!NtfsCommonCleanupCallout+0x19
    fffff880`0a58b2b0 fffff880`01622d42 : fffff880`01622cb0 00000000`00000000 fffff880`0a58b700 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0a58b390 fffff880`016c1a04 : fffff880`0a58b460 fffff880`0a58b460 fffff880`0a58b460 fffff880`0a58b510 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
    fffff880`0a58b400 fffff880`01515bcf : fffff880`0a58b460 fffffa80`08c71b80 fffffa80`08c71f68 fffffa80`09ed2d30 : Ntfs!NtfsFsdCleanup+0x144
    fffff880`0a58b670 fffff880`015146df : fffffa80`06ed9de0 00000000`00000000 fffffa80`06db0c00 fffffa80`08c71b80 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0a58b700 fffff880`0157a70c : fffffa80`06ed9de0 00000000`09000001 00000000`00000000 00000000`00000000 : fltmgr!FltpDispatch+0xcf
    fffff880`0a58b760 fffffa80`06ed9de0 : 00000000`09000001 00000000`00000000 00000000`00000000 00000000`00000000 : symsnap+0x770c
    fffff880`0a58b768 00000000`09000001 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`06ed9de0
    fffff880`0a58b770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`06060000 : 0x9000001
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`03123d7c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    Caused by: StorageCraft Volume Snap-Shot or Symantec/Norton Backup Exec driver. Recommend removing the offending program.
      My Computer


  10. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #20

    Ok I'll look for a decent backup alternative to Norton and continue using the comp. Any recommendations for a backup program?

    Cheers
      My Computer


 
Page 2 of 3 FirstFirst 123 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 04:51.
Find Us