The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    is this a GPU problem?

    Discussion in 'Alienware M15x' started by Ovenmitt, Dec 22, 2011.

  1. Ovenmitt

    Ovenmitt Notebook Guru

    Reputations:
    4
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    15
    I've had my computer screen lockup with the image that was just on it frozen. The computer still runs and I can talk on skype but can't alt tab or cntrl ult delete...have to hardboot. The screen will either be the image that was on it before, a black screen, and sometimes it will go to the blue screen dumping memory screen.

    It only happens when I play League of Legends for a long period of time normally 3-5 games and it will happen. If I play for an 8 hour session it will happen 2-3 times. I do not have a FPS issue...it is always at 60 FPS in game and I never get video lag it will just lock up.

    I repasted about 6 months ago and checked my temps while I am in the middle of a game and they are normal. I ran Memtest86 and everything passed. I checked the fans to make sure they were dust free and they were. I have tried to update the drivers, flashed to A09, and tried to adjust the TDRdelay and so far nothing has worked.

    Assuming that this is a GPU problem then I am going to get the 6970m and just upgrade but I want to make sure that I dont spend all this money and find out that its another issue and not have the money to actually fix the problem so I can play with no lockups. Please any help would be appreciated!!

    Also I am running the 260m
     
  2. khetik

    khetik Notebook Deity

    Reputations:
    101
    Messages:
    812
    Likes Received:
    17
    Trophy Points:
    31
    Have you tried different drivers? Try out the 280.66 they worked really well for me and no issues at all
     
  3. Ovenmitt

    Ovenmitt Notebook Guru

    Reputations:
    4
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    15
    Ok maybe I'm just an idiot but I'm having a hard time find a place to download that driver =/
     
  4. t_man

    t_man Notebook Geek

    Reputations:
    81
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
  5. Ovenmitt

    Ovenmitt Notebook Guru

    Reputations:
    4
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    15
    downloaded it and will check it out....thankyou!!! +rep

    Below are the last four crashes...they all seem like different reasons...wanted to do the :spoiler: but couldnt find it.... so sorry for the spam

    On Tue 12/20/2011 11:54:06 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: Unknown (0xFFFFF80002C99C40)
    Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003364180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
    Google query: Unknown CLOCK_WATCHDOG_TIMEOUT




    On Sun 12/18/2011 6:57:58 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121811-22105-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC3BAE4)
    Bugcheck code: 0x116 (0xFFFFFA800CAD90E0, 0xFFFFF88010138AE4, 0xFFFFFFFFC000009A, 0x4)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 285.79
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 285.79
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.79 , NVIDIA Corporation).
    Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR




    On Mon 12/12/2011 4:30:04 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121111-16707-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
    Bugcheck code: 0x116 (0xFFFFFA800C1AC4E0, 0xFFFFF8801012AAE4, 0xFFFFFFFFC000009A, 0x4)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 12/6/2011 9:52:39 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120611-17222-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x116 (0xFFFFFA80074FF170, 0xFFFFF8801005BAE4, 0xFFFFFFFFC000009A, 0x4)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
     
  6. t_man

    t_man Notebook Geek

    Reputations:
    81
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    Looks like the display driver is giving you a problem; if it were me I would go back to the default Dell driver for a little while to see if it fixes the problem it certainly couldn't hurt.
    I had this same crash dump results on another system which turned out
    to be the video card; but I knew it was the video card because of the lines
    and color distortion I was getting when I booted the system ..
     
  7. Ovenmitt

    Ovenmitt Notebook Guru

    Reputations:
    4
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    15
    I am having a real hard time finding where to get drivers....is there a specific place to get older ones that may be more stable? I know Khetik mentioned the 280.66 but could not find a place to download it at.
     
  8. t_man

    t_man Notebook Geek

    Reputations:
    81
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15