BSOD, 0x0000001a and 0x0000004e

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 25
    Windows 7 Home
    Thread Starter
       #11

    YoYo155 said:
    Thanks for the update :) .

    A few things come to mind in that situation, all of the following are taking into consideration
    that the display is in a working order.

    Bad RAM (possibly slot as well), overheating, failing HDD, failing PSU, bad GPU.

    Do you have an idea of any of those (or event another part) you think might be particularly
    at fault based on age and past experience?
    As embarrassing as this is, in that particular incident it appears it was a loose DVI cable! I have not had any problems since. At the time of that freeze, I was watching a video and running MBAM.

    I understand you can't analyse the logs yet, but should I be uninstalling AVG? That appeared to be least one of the drivers at fault when I was running Driver Verifier.
      My Computer


  2. Posts : 3,056
    Windows 10
       #12

    Ha ha don't worry it happens, that is what the screws are for .

    I appreciate your understanding :), just to shed some light on the subject it due to a recent
    security update Microsoft has released which changed the time stamp of a vital file which they haven't
    updated yet in the symbol server.
    That is always a good idea (unfortunately) 3rd party AV programs have been proven troublesome in the past.

    Please do so while using the AVG Removal Tool and install MSSE as a reliable alternative :) .

    Update:

    I was finally able to properly read the bugchecks, and as you DV blames AVG Anti-Rootkit
    driver for the bugchecks, let us know how things are going after removing it :) .
    Last edited by YoYo155; 18 Oct 2013 at 07:11. Reason: symbols.
      My Computer


  3. Posts : 25
    Windows 7 Home
    Thread Starter
       #13

    YoYo155 said:
    Ha ha don't worry it happens, that is what the screws are for .

    I appreciate your understanding :), just to shed some light on the subject it due to a recent
    security update Microsoft has released which changed the time stamp of a vital file which they haven't
    updated yet in the symbol server.
    That is always a good idea (unfortunately) 3rd party AV programs have been proven troublesome in the past.

    Please do so while using the AVG Removal Tool and install MSSE as a reliable alternative :) .

    Update:

    I was finally able to properly read the bugchecks, and as you DV blames AVG Anti-Rootkit
    driver for the bugchecks, let us know how things are going after removing it :) .
    Thanks YoYo, your help has been much appreciated. I have removed it now and let you know if any further problems crop up. :)
      My Computer


  4. Posts : 3,056
    Windows 10
       #14

    You're welcome :) .
    Be sure to update whichever way things turn out to be .
      My Computer


  5. Posts : 25
    Windows 7 Home
    Thread Starter
       #15

    Hi, everything had been running very smoothly with no issues at all - until just 5 minutes ago when I had a crash when playing a game.

    I didn't actually display a BSOD - I had to do a forced reset. The PC froze up and the speakers made a buzzing noise.

    I have attached the files.
      My Computer


  6. Posts : 3,056
    Windows 10
       #16

    Hi Tom :) .

    Good to hear, I do see almost a month had passed between bugchecks which is great!
    As this post will explain below your PC did generate a dump but didn't really bug check.

    What you're experiencing is called a TDR (Timeout Detection & Recovery) and its not a real crash
    in the sense that something wrong occurred in the Kernel.
    TVeblen said:
    "Display driver xxxxx stopped responding and was recovered"

    Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.
    .
    .
    .
    .
    There are numerous reports of hardware solutions to TDR's. The most common are:

    • Poor Cooling
    • Problems with the power supply
    • Overclocking Issues
    • Bad System memory or incorrect memory timings
    • Defective PC Components

    • More details HERE, please read.


    As things have been stable for a month or so I think it's a thermal issue or perhaps a recently
    changed hardware/device driver.

    What has changed recently?


    Test for thermals 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.
      • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

      My Computer


  7. Posts : 25
    Windows 7 Home
    Thread Starter
       #17

    Sorry for the late reply, been very busy. I downloaded and ran Furmark just there and my PC crashed almost straight away when it got to around 49-50 degrees - so something isn't right.
      My Computer


  8. Posts : 3,056
    Windows 10
       #18

    Don't worry about it :) .
    Did the PC restart itself or bug check?
    Is it reproducible, meaning does Furmark crash the machine every time?
    How long can the machine handle the stress?
    What is the make, model and age of your PSU?

    Fill out this form and post back the result:


    Good practice, open up the case and re-seat all types of connection.

    • SATA Cables (HDD/SSD/ODD).
    • SATA-Power.
    • Motherboard 24-pin.
    • Motherboard 4/8-pin (CPU).
    • Re-seat the RAM.
    • Re-seat the GPU.
      My Computer


  9. Posts : 25
    Windows 7 Home
    Thread Starter
       #19

    1. It bug checked.
    2. I ran it twice, the first time I got the following message: "The NVIDIA OpenGL driver lost connection with the display
    driver due to exceeding the Windows Time-Out limit and is unable to continue. The application must close". The second time it just crashed.
    3. I can run it more to find out?
    4. It was about 20-30 seconds. Crashed around the same temp both times.

    I had a look at the power calculator, but I had to guess a fair bit. It came out at 532 minimum and 582 recommended.

    Without opening it up, I can't tell you the exact model of PSU. But its Corsair branded, 650w and is almost exactly two years old.
      My Computer


  10. Posts : 3,056
    Windows 10
       #20

    That Wattage is a bit too close for my liking, can you name the exact model of the PSU?
    Please fill out your system specs by following this tutorial so you won't have to guess :) .

      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 00:11.
Find Us