BSOD after about 30 hours of use, believe it is catalyst 12.2 related

name prety much says it all. re installed catalyst, gunna c if it helped, but after i re installed i saw fraphixs tearing on startup.

yes i OC, however i turn it off when im not gaming or developing so i dont c why it should be an issue. when i OC my temps always stay below 70c, and 55 on my CPU, but yesterday was kinda hot and my cpu reached 56.8 so i stopped OCing for the day, prolly wont today iether, again kinda hot.

i get BSODs seemingly only on idle, its happend 3 times in 3 days now, hasnt happend again yet, but i found my pc off this morning, not sure if it was a windows update or another bsod, i left it off while i was gone. it was a windows update so i stand at 3

going to try... AGAIN... reinstalling the drivers

i should mention, i tryed rolling back the drivers, but windows just delieted them and kept catalyst, and amd doesnt offer older versions of vcc so i had to get 12.2 again

it might be a cpu thing, but not sure, i cant think of any thing else i might have installed that would have caused it.

i would run trend micro, but when i run a full system check, it gets stuck at 0pct in my autodesk files it just sits there for days. getting nowhere. quick scan might turn up some cookies or trojans on a thumb drive but not anything already on the computer usually. any ideas on these issues?

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.

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.

zigzag3143 said:

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.

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.

i dont crash on startup, like i said, 30 hours of use, then... bye bye... ill look for the file

zigzag3143 said:

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.

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.

is it possible i can look at the file, im not sure i feel confident puting up my information online like this. i can get blescreenviewer and view the files and go over the recent downloads and updates

zigzag3143 said:

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.

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.

i think i found the culprets... dxgmms1.sys... you have posted about this on other posts, this is a common one, atikmpag.sys... and dxgkrnl.sys


the atikmpag would be my display drivers getting insufficiant power... dunno how, might be overclocking the volatage too high, however i dont leave OC on all the time like mentioned, only when i game, which is a few hours out of every day


now how to solve is the problem now, i re installed my graphics drivers YET AGAIN, and have seen some improvement in the way of tearing, and images are loading faster... but i still worry about dxkrnl which is having to do with dx drivers and dxgmms1.sys

Thornton said:

zigzag3143 said:

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.

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.

i think i found the culprets... dxgmms1.sys... you have posted about this on other posts, this is a common one, atikmpag.sys... and dxgkrnl.sys


the atikmpag would be my display drivers getting insufficiant power... dunno how, might be overclocking the volatage too high, however i dont leave OC on all the time like mentioned, only when i game, which is a few hours out of every day


now how to solve is the problem now

\

Um, Dont Overclock

zigzag3143 said:

Thornton said:

zigzag3143 said:

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.

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:
To ensure minidumps are enabled:

i think i found the culprets... dxgmms1.sys... you have posted about this on other posts, this is a common one, atikmpag.sys... and dxgkrnl.sys


the atikmpag would be my display drivers getting insufficiant power... dunno how, might be overclocking the volatage too high, however i dont leave OC on all the time like mentioned, only when i game, which is a few hours out of every day


now how to solve is the problem now

\

Um, Dont Overclock

lol, real easy to say for someone wh hasnt done it, i got away with it for months untill i upgraded my graphics drivers, no problems till then... graphics cards have problems, fact, they cause pcs to have more problems than usual fact, to have fun with a graphics card and really play games, you gotta tinker allittle, or be willing to settle for a 20fps drop, theres a fix for alla these, the question is what

Thornton said:

zigzag3143 said:

Thornton said:

i think i found the culprets... dxgmms1.sys... you have posted about this on other posts, this is a common one, atikmpag.sys... and dxgkrnl.sys


the atikmpag would be my display drivers getting insufficiant power... dunno how, might be overclocking the volatage too high, however i dont leave OC on all the time like mentioned, only when i game, which is a few hours out of every day


now how to solve is the problem now

\

Um, Dont Overclock

lol, real easy to say for someone wh hasnt done it, i got away with it for months untill i upgraded my graphics drivers, no problems till then... graphics cards have problems, fact, they cause pcs to have more problems than usual fact, to have fun with a graphics card and really play games, you gotta tinker allittle, or be willing to settle for a 20fps drop, theres a fix for alla these, the question is what

BSOD's are a unique combination of things. Drivers, updates, hardware, etc. You may have been able to do it for months, even years, but perhaps that newest game you downloaded and installed the exact thing that is conflicting with the OC currently.

I do BSOD's (perhaps over 10,000) and the vast majority of them are on gamers who OC.

I am not a gamer (obviously) so all I can say is if you need to, do it, but you are currently crashing right?

zigzag3143 said:

Thornton said:

zigzag3143 said:

\

Um, Dont Overclock

lol, real easy to say for someone wh hasnt done it, i got away with it for months untill i upgraded my graphics drivers, no problems till then... graphics cards have problems, fact, they cause pcs to have more problems than usual fact, to have fun with a graphics card and really play games, you gotta tinker allittle, or be willing to settle for a 20fps drop, theres a fix for alla these, the question is what

BSOD's are a unique combination of things. Drivers, updates, hardware, etc. You may have been able to do it for months, even years, but perhaps that newest game you downloaded and installed the exact thing that is conflicting with the OC currently.

I do BSOD's (perhaps over 10,000) and the vast majority of them are on gamers who OC.

I am not a gamer (obviously) so all I can say is if you need to, do it, but you are currently crashing right?

been good for a while, just reinstalled my driver without trendmicro on and my computer is running smoother, no crashes yet, usually takes about 30 hours or so though to tell for sure

Good luck and keep us in the loop. BTW Trend isnt recommended.