Laptop: Screen freezes followed by a buzzing sound during gameplay

Page 1 of 3 123 LastLast

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

    Laptop: Screen freezes followed by a buzzing sound during gameplay


    Hey guys. I've been having this problem on and off and with various games now. At some point during playing a game, my laptop will freeze and make a buzzing sound through the speakers/headphones. I have a Dell XPS L501x laptop with Windows 7 64bit on it. I have an Intel Core i7-2630QM CPU with 6GB of RAM. My video card is a Nvidia GeForce GT 540M.

    I've contacted Dell about this and they replaced my motherboard 3 times and the problem persisted. However, the replacements were about a year ago when this problem occurred while playing League of Legends. After Dell not really being able to help and their flawed and pointless circle logic became more of a nuisance than the buzzing problem, I decided to just endure the issues. The buzzing sound and the freezing did stop happening however after a few more times of encountering the problem. I didn't change anything or update anything to my knowledge. It just stopped happening.

    However, recently while playing Skyrim, I've been facing the same issues! The screen will freeze and a buzzing sound will play through my headphones. If I disconnect the headphones while it's buzzing, the sound doesn't come through the speakers though.

    Dell Support wasn't fully able to get rid of the problem, but maybe you guys can help me find the root of it. Let me know what other information you need and thank you all in advance!
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    All of the bugchecks are the same and are very old, throughout 2012.
    But still referring to a driver still present on the machine.

    Code:
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8005f004a0, Physical Device Object of the stack
    Arg3: fffff800044023d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa8005863a90, The blocked IRP
    Code:
    !irp fffffa8005863a90 1
    Irp is active with 9 stacks 8 is current (= 0xfffffa8005863d58)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
    Flags = 00000000
    ThreadListEntry.Flink = fffffa8005863ab0
    ThreadListEntry.Blink = fffffa8005863ab0
    IoStatus.Status = 00000000
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = fffffa8005863b08
    Tail.Overlay.Thread = 00000000
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = fffffa8006186ae8
    Tail.Overlay.ListEntry.Blink = fffff8000328fae0
    Tail.Overlay.CurrentStackLocation = fffffa8005863d58
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa8006e4ce20 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\system32\DRIVERS\SynTP.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SynTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
     \Driver\SynTP
                Args: 00014400 00000001 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005f0d010    
    
                Args: 00000000 00000000 00000000 00000000


    Code:
    lmvm SynTP
    start             end                 module name
    fffff880`03c2f000 fffff880`03d8c000   SynTP    T (no symbols)           
        Loaded symbol image file: SynTP.sys
        Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
        Image name: SynTP.sys
        Timestamp:        Fri Dec 17 18:51:13 2010 (4D0B9501)
        CheckSum:         00163764
        ImageSize:        0015D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    The driver is very old!

    Download the latest from your OEM website.






    I believe the problem you are experiencing is due to overheating.
    Your system event log is filled with these:


    Code:
    Event[837]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-12-31T19:02:07.863
      Event ID: 89
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: ModgePodge
      Description: 
    ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.             
    _PSV = 368K             
    _TC1 = 1             
    _TC2 = 5             
    _TSP = 1000ms             
    _AC0 = 0K             
    _AC1 = 0K             
    _AC2 = 0K             
    _AC3 = 0K             
    _AC4 = 0K             
    _AC5 = 0K             
    _AC6 = 0K             
    _AC7 = 0K             
    _AC8 = 0K             
    _AC9 = 0K             
    _CRT = 373K             
    _HOT = 0K             
    _PSL - see event data.
    
    ---------------------
    
    Event[840]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Processor-Power
      Date: 2012-12-31T19:02:10.749
      Event ID: 26
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: ModgePodge
      Description: 
    Processor 0 in group 0 exposes the following:
    
    2 idle state(s)
    14 performance state(s)
    8 throttle state(s)
    Test for overheating and stability:

    • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

    Post back with the results :) .
      My Computer


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

    Here's the idle and GPU for now. I'll do the CPU one tomorrow because it'll take more time. Also, do you want me to run both the CPU and GPU stress tests at the same time?
      My Computer


  4. Posts : 3,056
    Windows 10
       #4

    No don't stress this is crazy hot already!


       Warning
    The Following Steps Will Void Your Warranty!


    Addressing the overheating issue:

    • Make sure you can hear or see the fan working, if it is continue with these steps.


    1. Shut-Down the PC
    2. Unplug from the power brick.
    3. Remove the battery.
    4. Let the PC cool down for as long as needed until its only warm to the touch or not at all.
    5. Buy a can of compressed air.
    6. If you have a cover on the bottom that can be unscrewed, remove it for grater access.
    7. When using the compressed air, use short bursts and DO NOT! use it upside-down!!
    8. First blow into the intake (the grill with the fan) again short bursts.
    9. Next do the same to the exhaust.
    10. If you have access the opposite side of the fan blow through there as well.
    11. Next grab a flashlight and point it inward from the exhaust and look for anything that may be blocking the light from passing through when looking from the intake side (the fan).



    Happy cleaning :)


      My Computer


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

    Here's the CPU test after like 15 minutes. And I will clean everything out tomorrow and get back to you then! Thank you very much!
      My Computer


  6. Posts : 3,056
    Windows 10
       #6

    You're welcome!
    Keep posting updates :) .
      My Computer


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

    Well, it crashed again... kind of. I updated my drivers to the newest nvidia beta drivers and I had the same freeze and buzzing sound occur, but after like 10 seconds it exited the game (Skyrim), and it showed an error in the notification area with an error. I can't remember what the error said though. Either way, I rolled my drivers back to the newest official/stable drivers.

    EDIT: Here's the errors. It'll buzz and freeze but eventually stop and either allow me to keep playing, or it'll close the program. I haven't had to force shut down since I cleaned.
    Last edited by ModgePodge; 07 Sep 2013 at 19:06.
      My Computer


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

    Froze and buzzed again. This time I had to force shut down.

    Here's another one of these if you want it.
      My Computer


  9. Posts : 3,056
    Windows 10
       #9

    Thank for the update :) .
    No new dumps were created but that is inline with the fact that no bugchecks occurred.

    How did the cleaning process go?
    Post a new set of screenshots using Speccy as detailed above ( #4 ) .
      My Computer


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

    Cleaning went well I think. It takes a bit longer now for the GPU to heat up and it's not quite getting to the same temps.
      My Computer


 
Page 1 of 3 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 14:19.
Find Us