locked
Problem caused by Device Driver RRS feed

  • Question

  • I've no idea if this is the right place to put this, but I'm having an issue.  My computer will randomly just bluescreen me and reset itself.  Below is the error message:

     

     

    You received this message because a device driver installed on your computer caused the Windows operating system to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.

    More information



    Problem report summary

    Problem type

    Windows stop error (a message appears on a blue screen with error code information)

    Solution available?

    No

    What does this problem mean?

    Windows has encountered a problem it cannot recover from and it needs to be restarted

    Cause

    Unknown

    Computer symptoms

    A message appears on a blue screen with error code information (for example: 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED)

    Additional steps for you to take

    Please continue to send problem reports so analysts at Microsoft can study and try to correct the problem as quickly as possible

     

    ^^^

    So I'm sending this to you guys, to see if you can help me figure out what driver is fubar.  I am using Windows Ultimate on an upgrade through XP>Home Basic>Ultimate.

     

     

    Wednesday, August 15, 2007 7:30 AM

All replies

  • There is nothing more to the error message than what you put as an example? There should be more to that error message with the driver causing the issue displayed at teh end of the message (ie - Driver.sys).

    Have you tried looking under Control Panel > Administrative Tools > Event Viewer > Windows Logs > System for additional information after one of these Stop errors occur? There may be a more detailed error in the logs.

    HTH,

    Tim

    Wednesday, August 15, 2007 3:38 PM
  • I am having a similar problem. What is a device driver anyway?

    -------------------------------------------------------------------------------- 
    Technical Information
    How to Troubleshoot Hardware and Software Driver Problems in Windows XP (Q322205)
     
     

     
     
    Problem caused by Device Driver

    You received this message because a device driver installed on your computer caused the Windows operating system to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.

    More information

    --------------------------------------------------------------------------------



    Problem report summary


    Problem type
     Windows stop error (a message appears on a blue screen with error code information)
     
    Solution available?
     No
     
    What does this problem mean?
     Windows has encountered a problem it cannot recover from and it needs to be restarted
     
    Cause
     Unknown
     
    Computer symptoms
     A message appears on a blue screen with error code information (for example: 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED)
     
    Additional steps for you to take
     Please continue to send problem reports so analysts at Microsoft can study and try to correct the problem as quickly as possible
     
     

    --------------------------------------------------------------------------------
    Thursday, August 23, 2007 10:31 AM
  • I am having a similar report problem

     

    0x0000001e (0xffffffffc0000005, 0xfffff8000188d60a, 0x0000000000000001, 0x000000000000012e

     

    0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000

     

    0x0000003b (0x00000000c000001d, 0xfffff8000188d7bf, 0xfffff9800e2742c0, 0x0000000000000000

     

    These are just some of the error codes I keep getting once the BSOD appears.

    Saturday, October 27, 2007 11:22 AM
  •  AThomp wrote:

    I've no idea if this is the right place to put this, but I'm having an issue.  My computer will randomly just bluescreen me and reset itself.  Below is the error message:

     

     

    You received this message because a device driver installed on your computer caused the Windows operating system to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.

    More information



    Problem report summary

    Problem type

    Windows stop error (a message appears on a blue screen with error code information)

    Solution available?

    No

    What does this problem mean?

    Windows has encountered a problem it cannot recover from and it needs to be restarted

    Cause

    Unknown

    Computer symptoms

    A message appears on a blue screen with error code information (for example: 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED)

    Additional steps for you to take

    Please continue to send problem reports so analysts at Microsoft can study and try to correct the problem as quickly as possible

     

    ^^^

    So I'm sending this to you guys, to see if you can help me figure out what driver is fubar.  I am using Windows Ultimate on an upgrade through XP>Home Basic>Ultimate.

     

     

    Friday, November 2, 2007 4:08 PM
  •  ZEECHOPPAH wrote:
    I am having a similar report problem

     

    0x0000001e (0xffffffffc0000005, 0xfffff8000188d60a, 0x0000000000000001, 0x000000000000012e

     

    0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000

     

    0x0000003b (0x00000000c000001d, 0xfffff8000188d7bf, 0xfffff9800e2742c0, 0x0000000000000000

     

    These are just some of the error codes I keep getting once the BSOD appears.

    I get the same EXACT errors as you but i also get "7e"
    so i get "7e", "3b" and "1e". either one takes turns. im  on Vista x64.
    How did you fix this?
    Tuesday, March 25, 2008 8:50 AM
  • I had the same issue with Vista 32 and 64 and now windows 7 Beta. The issue of 0x0000003b is a memory handler device error which was to be fixed by the next release candidate. I use the Nvidia SLI chipset on my MB's and I know it is an sys config error which just hasn't been redressed.
      I am disapointed with MS over this issue as with only 4GB of memory installed on the Motherboard I expected a better response this time around to the common issues. This was and is a common issue.
    Memory handlers are the biggest issue with Microsoft operating systems. They got it wrong with windows 98 and they haven't addressed it correctly since. only supplying patches to a working system. I cannot get even a 64 bit windows O/S up and running from boot installation without this exception and having to remove the memory and perhaps when the kernal kicks in taking over the memory handling.
    I am fed up having to edit XML files to build my own instalation sequences into windows when the provider I.E. Microsoft should have solved the simple script end handle errors by now.
      I certainly will not be upgrading to windows 7 if I cannot do a simple thing like install the O/S no matter how glossy it looks. I may be tempted to go Apple completely.
    Friday, January 9, 2009 10:44 AM