Posted 23 December 2006 - 07:55 PM
Posted 23 December 2006 - 08:32 PM
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive.
from another forum,
It sounds from this that you have some corrupted system files. If you can get to the desktop do a search for drwtsn32. open it up and look at the Application Exception entries. You just need to look at the first part. The most recent will be towards the bottom. See what program is causing it, or if there are different ones. Actually before doing that if you get to the desktop try to run the system file checker. Go to start/run and type in sfc /scannow and let it run. It will repair or replace any corrupted system files.
Example of what to look for in drwtsn32:
Application exception occurred:
App: C:\Program Files\Deepnet Explorer\Deepnet.exe (pid=5472)
When: 8/31/2005 @ 14:03:59.937
Exception number: c0000005 (access violation)
To tell you the real truth if you cannot find where the problem is relatively quickly a repair install may be the quickest way to fix it.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users