Eventid 1003 BSoD

By mHatter ยท 4 replies
May 2, 2010
  1. I set up remote desktop on windows XP over the internet. Terminal services caused some printer driver issues. The first set of problems seems to have been remedies by a wizard I found on the MS support page.

    But there are more. I am pretty certain it is more printer driver problems because I can operate in safe mode. Anyway, I am lost. Here are several dump files.

    Basically, the system will boot and within about a minute it goes to BSoD. I don't know how to get any useful information from the dumps. THere were a few devices in device manager (some sort of unidentified human interface device that had yellow exclamations on them. I disabled and then uninstalled these. This did not seem to hurt or help anything but they probably were related to the printers. this is a fresh xp install. Any help or pointers would be most greatly appreciated.

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    I read five of the files and all report the same error 0xF4: CRITICAL_OBJECT_TERMINATION
    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.

    And all report the same Windows OS driver as the cause of your crashes: csrss.exe

    Normally OS drivers are too general to be of much help but in this case it might help: This file is actually a Client/Server Runtime Server Subsystem ... This is the user-mode portion of the Win32 subsystem (with Win32.sys being the kernel-mode portion). Csrss stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. Csrss is responsible for console windows, creating and and/or deleting threads, and some parts of the 16-bit virtual MS-DOS environment. The csrss.exe which is from Microsoft is located in the c:\windows\System32 folder.

    * What were those yellow exclamations next to what devices? Deleting them was quite possibly not good.
  3. mHatter

    mHatter TS Rookie Topic Starter

    I can't say what the small yellow exclamation points were for the unidentified hardware devices. It did not seem to hurt anything when uninstalled. (or help).

    ANyway, so if it is this windows OS driver, what should I do to try to fix it? Plus, if you happen to know, why did it break when I started Remote Desktop.

    (and also, do you have any leads I can follow on learning how to many sense of those dump files? )
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    Those yellow triangles were telling you what devices were possibly the cause of your issues.

    In order to read the minidump files your first need the latest Debugging Tool and a boatload of Symbols. Downloading them takes a long time. Start with Windows XP, then XP1 and so on.

    See link: http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx#E3
  5. mHatter

    mHatter TS Rookie Topic Starter

    They were "human interface devices" but I have no idea what that means in this context because no new hardware was added. The other driver problems were all printer problems.

    So what is the solution? A clean wipe? Or is there a way I can fix it?

    THanks for the lead on dump files.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...