BSOD PFN List Corrupt

[eksgunner]

Greetings and thanks in advance for your help. Our system is experiencing frequent BSOD issues. Attached are the requested files per the posting instructions.

Our system is running Win7 64 Home Premium. We have an EVGA 750i SLI mobo and an EVGA GTX560 video card. Memory is 4GB (2 sticks, 2GB ea) of Kingston HyperX. We have a WD hard drive. The CPU is a Core2Quad Q6600 at 2.4 GHz.

In addition to the BSOD issues we also have constant video card crashes when playing Battlefield3.

Thanks!

 

[zigzag3143]

Nothing is attached try this method.
We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[eksgunner]

Sorry. I believe I've got the files attached and uploaded correctly this time.

 

[JMH]

1.Kaspersky is a frequent cause of BSOD's.
Please remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows

2. These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[eksgunner]

Thanks. We removed Kaspersky (ZoneAlarm), replaced it with Microsoft Security Essentials, and ran memtest overnight. Memtest completed 10 passes without any failures. We'll move on to the driver verifier next.

Edit: We had a new BSOD event yesterday referencing 'Bad Pool Caller'.

 

[JMH]

Submit any further DMP's.

NB. It is much easier to find patterns, etc, when there is more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

Please upload them when you have collected 2 or more.

 

[eksgunner]

Greetings. I've attached the last two dump files. Both were Bad Pool Caller related. Please let me know if you need anything else. Thanks.

 

[eksgunner]

The crashes keep coming. Attached are a few more dump files.

 

[JMH]

* Did you install Microsoft Security Essentials?

* Please provide us with your Event Viewer administrative logs by following these steps:

Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

* I suggest you download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[eksgunner]

Thanks, yes, we did install the security essentials right after removing Kaspersky.

I've attached the errors file you requested and will work on getting Malwarebytes installed.

Unfortunately our 'fun and free' weekend is ending now so we may not respond again until tomorrow evening but thanks very much for your help.

 

[eksgunner]

A few more dump files are attached, we plan to discontinue verifier as soon as the mwb scan is complete.

So, I have a question. I've looked for but not found an 'about' page for sevenforums. How does sevenforums exist and provide the support that it does, how is this service paid for?

Thanks!

 

[eksgunner]

I didn't see the file attachment on the last post. Sending again to be sure.

 

[zigzag3143]

Thanks, yes, we did install the security essentials right after removing Kaspersky.

I've attached the errors file you requested and will work on getting Malwarebytes installed.

Unfortunately our 'fun and free' weekend is ending now so we may not respond again until tomorrow evening but thanks very much for your help.

I must say a rather interesting event viewer log.

First You need to change your DMP to small dmp. that is the reason it is not in \minidump.

Second you have a large variety of errors from as far back as Feb, 2012 but it seems like your problems accelerated when you updated your nvidia driver (see snips)

You need to uninstall the driver and OpenGL and re-install the newest available of both

When upgrading your graphic driver you MUST remove all traces of the current driver.

In order to do that we recommend using
http://phyxion.net/item/driver-sweeper.html

When it is removed then download and install the fresh copy.

 

[JMH]

A few more dump files are attached, we plan to discontinue verifier as soon as the mwb scan is complete.

So, I have a question. I've looked for but not found an 'about' page for sevenforums. How does sevenforums exist and provide the support that it does, how is this service paid for?

Thanks!

Event viewer logs are being looked after by my partner....

Re us "the workers" here... We are volunteers from all around our world who donate our time attending the others problems.

To find out how Seven Forums exists {& where the money comes from to pay for the service} you would be best advised to address that question to the Admin.

 

[JMH]

Analysis of recent Dmp's indicate

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

CPUID - System & hardware benchmark, monitoring, reporting

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[eksgunner]

Thanks. We ran the mwb full scan last night and no malicious items were found.

Regarding the cooling possibility we've gone to great lengths to try to ensure good cooling. This coolermaster case we have has some massive fans and the h80 cpu cooler is, as I'm sure you know, liquid cooled. I don't think there's much more we can do but I'll look into the monitoring sw you recommended and will put compressed air to use to ensure things are clean again.

We will also work on re-installing the video driver cleanly.

Thanks again for all of the help. I've been getting a bit upset about not being able to deal with this myself. I've had a good number of PC's, servers, and workstations around in my time and never had one with issues that couldn't be resolved by a simple driver update or hardware swap at worst case. In fact I've been wondering if this mobo is a lemon and I'm still wondering if it is a lemon.

 

[zigzag3143]

Did you follow all the suggestions in the link? What were the results to the memory stressing?

 

[eksgunner]

Hi. Yes, we followed every suggestion except the most recent for re-installing the video driver. The memory test was run for about 12 hours, I believe it made 10 passes, there were no failures. Thank you!

 

[JMH]

Thanks for letting us know.

 

[eksgunner]

Bad Mobo

Greetings. I wanted to followup and close this out. We eventually elected to send our mobo to the manufacturer (EVGA) for analysis. They determined it was 'bad' and sent us a replacement. As our memory-related BSOD's stacked up and we could find no issue with our RAM or hard drive we began to suspect that it was the mobo hardware. We've got the replacement unit installed and it is working without issue, including playing Battlefield 3, which was a sure bet to cause a BSOD or other crash. Thanks much for your help which really provided the confidence to suspect the mobo as opposed to some other hardware or driver related issue. Thank you!