280.26 error WTH

Im not sure what my next move should be. been having (windows kernel mode driver 280.26 has crashed and succesfully recovered) for a little bit now, bout 4 weeks. Just today I got BSOD (SYSTEM_SERVICE_EXCEPTION)

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.

Re a 116 / 117....

"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

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Please follow JMH's suggestions first. These two drivers may be contributing as one of them is a display driver. They both need updating

Related to PCASp50a64.sys NDIS 5.0 SPR Protocol Driver (AMD64) from Printing Communications Assoc., Inc. Yours from 2006 and needs to updated to current

Related to TBPANELX64.SYS Display Control Program from Microsoft. Yours is from 2005 and needs to be updated or removed.


ALSO IT IS NEVER A GOOD IDEA TO HAVE TWO MALWARE APPS RUNNING. i WOULD REMOVE THEM BOTH AND REPLACE WITH MSE AT LEAST TO TEST.


Avast can be a contributing cause of BSOD'S . Please remove and replace Avast & Norton with Microsoft Security Essentials AT LEAST TO TEST



http://us.norton.com/support/kb/web_...080710133834EN


http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

solved for now...much appreciation threadgoers!