BSOD when launching Portal 2 on Steam (Win 7 Professional)

Discussion in 'Windows 7 Help and Support' started by thatcoolnerd, Jul 27, 2012.

  1. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    View attachment 072712-32370-01.dmp

    That's the minidump that I get when I try to launch Portal 2. It gets to the title screen, and I have about 4 seconds to do whatever, but then my computer blue screens.

    Help?
     
  2. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello there!

    Seems like it's avgidsfiltera.sys which belongs to AVG. Please remove AVG completely and run the AVG Removal Tool and install Microsoft Security Essentials instead.

    Bugcheck:

    Code:
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    STACK_TEXT:  
    fffff880`031aef48 fffff800`0312befa : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
    fffff880`031aef50 fffff800`030decd7 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffffa80`04bf1800 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`031aefe0 fffff800`03017895 : fffff800`0303d460 fffff880`031af190 fffff800`0303d460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`031af0e0 fffff800`030d1713 : 00000000`0d12d266 fffff800`03247e80 fffffa80`0794a9e0 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`031af110 fffff800`030d9fe0 : fffff800`03247e80 00000000`00000001 00000000`00000000 fffff880`031af398 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`031af2a0 fffff800`03118fbc : fffff880`031af598 00000000`00000000 00000000`00000000 fffff800`031173b1 : nt!KeFlushMultipleRangeTb+0x260
    fffff880`031af370 fffff800`03115df1 : fffffa80`069fd040 00000000`00000000 fffff880`031af598 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
    fffff880`031af470 fffff880`012dea07 : fffffa80`095efe98 00000000`00000000 fffff8a0`00000000 fffff8a0`00001000 : nt!CcFlushCache+0x561
    fffff880`031af570 fffff880`012def46 : fffffa80`0a11d290 fffff8a0`00118bc0 00000000`00000000 00000000`00000001 : Ntfs!NtfsFlushBootCritical+0x73
    fffff880`031af5e0 fffff880`012df6b4 : fffffa80`0a11d290 fffffa80`08a57bd0 fffffa80`095ef4f0 fffff8a0`00118bc0 : Ntfs!NtfsCommonFlushBuffers+0x3f2
    fffff880`031af6c0 fffff880`010e5bcf : fffffa80`08a57fb8 fffffa80`08a57bd0 fffffa80`0a11d290 fffff880`031af6e8 : Ntfs!NtfsFsdFlushBuffers+0x104
    fffff880`031af730 fffff880`010e46df : fffffa80`07931950 00000000`00000000 fffffa80`07931900 fffffa80`08a57bd0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`031af7c0 fffff880`06232b88 : 00000000`00000002 fffff880`031afb10 00000000`00000000 fffffa80`0883fb90 : fltmgr!FltpDispatch+0xcf
    fffff880`031af820 00000000`00000002 : fffff880`031afb10 00000000`00000000 fffffa80`0883fb90 fffffa80`08a57bd0 : avgidsfiltera+0x1b88
    fffff880`031af828 fffff880`031afb10 : 00000000`00000000 fffffa80`0883fb90 fffffa80`08a57bd0 fffff800`033d8eab : 0x2
    fffff880`031af830 00000000`00000000 : fffffa80`0883fb90 fffffa80`08a57bd0 fffff800`033d8eab 00000000`00000002 : 0xfffff880`031afb10
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    --------- 
     
  3. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    Is there any way that I can use AVG still, or is uninstall the only option? I looked up a comparison of the two antivirus' mentioned and tit seems as though MSE isn't as good as AVG.

    By the way, thank you for the fast response. On my last thread of Just Cause 2 nobody replied at all.
     
  4. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Sorry that we missed out your thread.

    You can reinstall it later. That particular driver got corrupted so can complete cleanup would be the best option. Once everything is fine you can reinstall AVG back.
     
  5. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    So basically:

    - Uninstall AVG
    - Install MSE
    - Run Portal 2, play for a while (to make sure the problem has gone away)
    - Install AVG
    - Uninstall MSE

    Yes?

    By the way, it's fine. People missing threads happens, I'm just happy to finally get help. I bought Portal 2 almost 2 weeks ago, so the sooner the better.
     
  6. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    I just uninstalled AVG, rebooted, and attempted this again.

    My system failed again, but there was no blue screen, however there was a new minidump file.

    Sorry to keep posting, but I just want this to work :(

    View attachment 072712-24195-01.dmp
     
  7. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    Well, looks like my blue screen will be ever-going
     
  8. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello there!

    Seems like the latest dump file is pointing to Hardware. Let's run a Hardware Diagnostic Hardware Diagnostic | Captain Debugger

    Code:
    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: fffffa80076558f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031af5b0 fffff800`032caca9 : fffffa80`076558d0 fffffa80`06ab0040 00000000`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031afad0 fffff800`031ab547 : fffffa80`076558d0 fffff800`032252d8 fffffa80`06ab0040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031afb00 fffff800`03112945 : fffff800`03286ae0 00000000`00000001 fffffa80`07603820 fffffa80`06ab0040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031afb40 fffff800`03091841 : fffff880`010cce00 fffff800`03112920 fffffa80`06ab0000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031afb70 fffff800`0331ee6a : 00000000`00000000 fffffa80`06ab0040 00000000`00000080 fffffa80`069f6040 : nt!ExpWorkerThread+0x111
    fffff880`031afc00 fffff800`03078ec6 : fffff880`02fd7180 fffffa80`06ab0040 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031afc40 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`04306740 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    --------- 
     
  9. thatcoolnerd

    thatcoolnerd New Member

    Joined:
    Jul 22, 2012
    Messages:
    20
    Likes Received:
    0
    I carefully update my BIOS and it works perfectly! Thanks Captain Jack! :D
     
  10. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Your Welcome. Thanks for reporting back :)
     

Share This Page

Loading...