Thread: the dreaded blue screen has emerged!

  1. #1
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158

    the dreaded blue screen has emerged!

    So our computer for no reason just terminated. It starts up in safe mode, but we can't find anything wrong. When we try to start it in regular mode we get the blue screen saying this:
    Code:
    *** STOP: 0x0000001E (0xC0000005, 0x804200E4, 0x00000000, 0x0000001D) ***
    KMOD_EXCEPTION_NOT_HANDLED
    
    *** Address 804200E4 base at 80400000, DateStamp 3EE6C002 - notskrnl.exe ***
    What now? All I can tell from this is that the kernal hit an error that it couldn't deal with.
    Oh, and starting it with last known good config doesn't work either.
    Please help!

  2. #2
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    Not sure what to do, but the 0xC0000005 means that it tries to use memory at an invalid address.. 0x0000001E, which is the bugcheck error means that this happens in kernel mode.

    In this error code, the fourth number is the address the code tried to access, and the second one, so code at 0x804200E4 tried to read or write to address 0x0000001D, which unsurprisingly failed.

    If you have a second machine, you can use WinDBG to find out which module is loaded at 0x804200E4 [and even which function that is].

    As to how to fix it ... Does it boot in safe-mode? If so, replacing the driver that causes the fault could be an idea. It may be a registry setting that causes a problem for that particular driver [e.g. something changed the "how much memory my driver should allocate" from 100K to 10000000K - which obviously doesn't work, and there was no good checking for that situation, so it fails].

    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  3. #3
    Cat without Hat CornedBee's Avatar
    Join Date
    Apr 2003
    Posts
    8,895
    In addition, KMOD_ suggests that it's a kernel module, i.e. a device driver, that caused the error.
    All the buzzt!
    CornedBee

    "There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
    - Flon's Law

  4. #4
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    Actually, it's NTOSKRNL itself - but it's probably some other component that passes in a bad datavalue (e.g. a NULL pointer).
    *** Address 804200E4 base at 80400000, DateStamp 3EE6C002 - notskrnl.exe ***
    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  5. #5
    Reverse Engineer maxorator's Avatar
    Join Date
    Aug 2005
    Location
    Estonia
    Posts
    2,318
    It is certainly the problem of a device driver, since the basic difference between safe mode and regular mode is that safe mode doesn't load kernel mode device drivers. Have you lately updated/installed/reconfigured some device drivers?
    "The Internet treats censorship as damage and routes around it." - John Gilmore

  6. #6
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Okay, this is making scene here. We reinstalled the OS. But now the modem isn't working, even though the drivers are installed. It's error is 10 (cannot start device). Would that mean it's busted?

  7. #7
    (?<!re)tired Mario F.'s Avatar
    Join Date
    May 2006
    Location
    Ireland
    Posts
    8,446
    I had a similar problem with a board mounted modem before. Is this your case? If so, try to uninstall the drivers from the Device Manager (right-click on My Computer>Properties>Hardware) and then reboot. When windows finds the new hardware install from your computer drivers cd.
    Originally Posted by brewbuck:
    Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.

  8. #8
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    One of the biggest problems with Windows is that it doesn't actually remove the driver files when you delete the driver, which can cause problems later. If you can, get rid of all the driver files. You could use an install monitor to monitor what the heck it installs.

    It's amazing how much difference just wiping out old files can help, since it helped me get rid of the blue screen when installing the sound drivers.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  9. #9
    Registered User VirtualAce's Avatar
    Join Date
    Aug 2001
    Posts
    9,607
    The old Win98 trick of deleting the folder where the drivers are also works unless of course they were put into System. Sometimes Windows continues to use the old folder even if you try to install new drivers. Not sure why this bug was never squashed.

  10. #10
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Amazingly, we unplugged it, cleaned it up a bit (we have a dust problem ) and plugged it back in, and all signs of the problem went away and now it works. We did clean uninstall and then reinstall the drivers like mario said though, maybe it's really what did it. Thanks for the help.

  11. #11
    Cogito Ergo Sum
    Join Date
    Mar 2007
    Location
    Sydney, Australia
    Posts
    463
    I haven't got a BSOD since XP came out
    =========================================
    Everytime you segfault, you murder some part of the world

  12. #12
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    Then lucky you. I have gotten it countless times.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  13. #13
    Cogito Ergo Sum
    Join Date
    Mar 2007
    Location
    Sydney, Australia
    Posts
    463
    Quote Originally Posted by Elysia View Post
    Then lucky you. I have gotten it countless times.
    I really don't understand what people are doing to get BSOD's, i've barely gotten them ever.

    Must be bad luck.

    Kuwabara, kuwabara
    =========================================
    Everytime you segfault, you murder some part of the world

  14. #14
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    Bad luck? How about poor drivers and Windows throwing a tantrum?
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  15. #15
    Reverse Engineer maxorator's Avatar
    Join Date
    Aug 2005
    Location
    Estonia
    Posts
    2,318
    Quote Originally Posted by Elysia View Post
    Bad luck? How about poor drivers and Windows throwing a tantrum?
    I have got blue screen once on WinXP - when I tested the drivers I made. :X
    "The Internet treats censorship as damage and routes around it." - John Gilmore

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. windows XP blue screen of death =-o!
    By MisterSako in forum Tech Board
    Replies: 14
    Last Post: 05-08-2006, 08:22 PM
  2. Feedback: Functional Specification Wording
    By Ragsdale85 in forum C++ Programming
    Replies: 0
    Last Post: 01-18-2006, 04:56 PM
  3. char copy
    By variable in forum C Programming
    Replies: 8
    Last Post: 02-06-2005, 10:18 PM
  4. i am not able to figure ot the starting point of this
    By youngashish in forum C++ Programming
    Replies: 7
    Last Post: 10-07-2004, 02:41 AM
  5. blue screen at startup
    By lambs4 in forum Tech Board
    Replies: 11
    Last Post: 11-21-2002, 04:16 PM