BSOD, 0x0000001a and 0x0000004e

[TomR1991]

Hi all.

I am not particularly computer literate, so you might have to bare with me!

On the 9/10 whilst browsing the web, the system blue screened and presented a 'Memory_Management' error. Yesterday (10/10), having ran fine previously for the whole day the system blue screened again and this time gave a 'PFN_List_Courrupt' error; once again, this occurred whilst I was doing something similarly unintensive.

I ran Memtest over night and there was no errors. But I am not sure where to go from here. Hopefully I have correctly attached the dump files. There are also two earlier dumps from last year - I can't remember what the first one was, but the second one was a result of bad RAM which was subsequently replaced.

Thanks in advance.

 

[YoYo155]

Hello and welcome to 7Forums .

One of the bugchecks is corrupted so no help there, and the other doesn't hold a whole lot of useful information
beside the fact that the graphics drivers were somehow involved (those were the drivers from May before the update).

Please run Driver Verifier and crash the machine for a couple of times, then post back with the results.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Please enable driver verifier following this TUTORIAL | But using these settings:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

 

[TomR1991]

Should I "add currently not loaded drivers to the list"?

 

[YoYo155]

No need to do so unless you're suspicious about a particular device driver that recently changed .

 

[TomR1991]

No need to do so unless you're suspicious about a particular device driver that recently changed .

OK.

I will update you whenever I get a crash.

EDIT: Almost as soon as I posted this it crashed. Will wait to see if it happens again.

 

[YoYo155]

Thanks for the update ,
a couple more will hopefully provide enough information.

 

[TomR1991]

Thanks for the update ,
a couple more will hopefully provide enough information.

OK, I have three crash dumps for you.

While I am sure there is more to it BlueScreenView is pointing to AVG as the probable culprit - which I did update to the 2014 version in the last couple of weeks. Attempting to run a scan would cause a crash.

In terms of other details, on one of the crashes I was stuck at the 'Windows Error Recovery' screen for a minute or two and couldn't launch into safemode because the keyboard was unresponsive. Also after each crash I have had to remove and insert my USB wireless adapter as well to get it to be recognised.

 

[YoYo155]

Thank for that .
Unfortunately we (the debugging community) are experiencing technical difficulties at the moment as there appears
issues with the public symbols server which we are dependent upon in order to read the dump files
in any meaningful way.
As things stand patience must be at the utmost of priority.

Thank you for understanding.

 

[TomR1991]

I disabled AVG scan's the other day and the system seemed relatively stable (also turned Verifier off) - not that I have been doing much.

But this evening the PC froze while streaming a video and I had to do a forced shutdown. I turned it back on straight away and it simply wouldn't boot - or at least there was nothing on the screen.

 

[YoYo155]

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?

 

[TomR1991]

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.

 

[YoYo155]

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 .

 

[TomR1991]

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.

 

[YoYo155]

You're welcome .
Be sure to update whichever way things turn out to be .

 

[TomR1991]

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.

 

[YoYo155]

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.

"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).

 

[TomR1991]

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.

 

[YoYo155]

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:

• Power Supply Calculator

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.

 

[TomR1991]

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.

 

[YoYo155]

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 .

• http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html