Results 1 to 12 of 12

Thread: 0x0000001E showing up on screen. What is this?

  1. #1
    Junior Member
    Join Date
    Mar 2012
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    Rep Power
    0
    Reputation
    30

    Angry 0x0000001E showing up on screen. What is this?

    Sighs... Hello guys. I'm having a little bit of a trouble and I could really use some help from someone.
    Anytime I play games or use photoshop on my PC, my computer goes on a rampage.
    I mean the screen literally turns blue. Since its something that recurs, I actually managed to make jottings
    of the writing that was presented whenever my computer went "boy blue". I saw this error 0x0000001E.

    I don't know what to do.
    Is there something wrong with my computer hardware or is it the software that's gone bad?
    How do you fix this pest?



Look Here ->
  • #2
    Senior Member
    Downunder35m's Avatar
    Join Date
    May 2009
    Posts
    4,063
    Thanks
    101
    Thanked 1,796 Times in 862 Posts
    Rep Power
    630
    Reputation
    15704

    Default

    Invest in proper hardware that can keep up to your needs.
    Without any details I wouls assume on board graphics and limited Ram.
    Apart from that you are in the wrong section and did not provide any details that might be useful to help you.
    Tomtom GO730 ,Navcore 9.004 ,Bootloader 5.5256 ,Map :Australia 845.2661
    ttmaps and Tomplayer on 16GB SDHC class6
    Password for all my files: downunder

  • #3
    Administrator
    mtv's Avatar
    Join Date
    Jan 2008
    Posts
    19,893
    Thanks
    7,508
    Thanked 15,066 Times in 6,761 Posts
    Rep Power
    5647
    Reputation
    239305

    Default

    Thread moved to PC section.

    This type of error is often caused by incorrect/corrupted drivers.... possibly RAM.

    Have you updated drivers recently?

    Possibly video drivers, as you say it's Photoshop and games, which are likely to be graphics and/or RAM intensive.

    It would help if you mentioned your OS and PC configuration.

    Googling the error comes up with several suggestions.

  • #4
    Banned

    Join Date
    Feb 2012
    Posts
    2,361
    Thanks
    166
    Thanked 1,205 Times in 607 Posts
    Rep Power
    0
    Reputation
    16611

    Default

    It seems NOT to be Windows 8.x you have running, because then the BSOD would look like




    What error text do you get, the line printed out in uppercase letters after "Windows has been shut down to prevent damage to your computer." line ?

    I suspect "KMODE_EXCEPTION_NOT_HANDLED"

    The "KMODE_EXCEPTION_NOT_HANDLED" bug check indicates that a kernel-mode program generated an exception which the error handler did not catch. Mostly this is due to a breakpoint in the program code that shipped with the final release: Programmer simply forgot to remove this / these.



    BTW:
    All pre-Windows 8 STOP Codes and their equivalent Error text .
    Last edited by jwoegerbauer; 02-08-14 at 03:30 AM.

  • The Following User Says Thank You to jwoegerbauer For This Useful Post:

    Tiny (02-08-14)

  • #5
    Premium Member
    hoe's Avatar
    Join Date
    Jan 2008
    Age
    60
    Posts
    6,367
    Thanks
    266
    Thanked 4,596 Times in 1,948 Posts
    Rep Power
    1820
    Reputation
    70528

    Default

    I would Suspect dodgy ram.

  • The Following User Says Thank You to hoe For This Useful Post:

    Philquad (02-08-14)

  • #6
    Crazy Diamond
    Tiny's Avatar
    Join Date
    Dec 2010
    Location
    Tasmania
    Age
    64
    Posts
    6,391
    Thanks
    10,996
    Thanked 5,436 Times in 2,651 Posts
    Rep Power
    2156
    Reputation
    89057

    Default

    This article describes how to troubleshoot a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message.

    Cheers, Tiny
    "You can lead a person to knowledge, but you can't make them think? If you're not part of the solution, you're part of the problem.
    The information is out there; you just have to let it in."

  • #7
    Banned

    Join Date
    Feb 2012
    Posts
    2,361
    Thanks
    166
    Thanked 1,205 Times in 607 Posts
    Rep Power
    0
    Reputation
    16611

    Default

    After the lines "If problems continue ... then select Safe mode." at BSOD a line similiar

    ***WXYZ.SYS - Address FA12345B base at C00000000, Datestamp 34567890

    is shown: So you always are told which file (application/driver) caused the crash, in this example it's WXYZ.SYS

  • #8
    Junior Member
    Join Date
    Mar 2012
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    Rep Power
    0
    Reputation
    30

    Default

    Quote Originally Posted by Downunder35m View Post
    Invest in proper hardware that can keep up to your needs.
    Without any details I wouls assume on board graphics and limited Ram.
    Apart from that you are in the wrong section and did not provide any details that might be useful to help you.


    Thanks for the suggestion you've offered, it's much appreciated. Unfortunately your suggestion did not work pertaining to investing in proper hardware that's able to keep up with my needs and its definitely not a situation where I have limited RAM. Why am I so confident its not limited RAM? I actually had some research done which highlighted the limited RAM issue and I also read this article [ which helped me to understand the problem my computer had. Thanks for the suggestion. I actually found something that works in another suggestion made on this post.

  • #9
    Junior Member
    Join Date
    Mar 2012
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    Rep Power
    0
    Reputation
    30

    Default

    Quote Originally Posted by mtv View Post
    Thread moved to PC section.

    This type of error is often caused by incorrect/corrupted drivers.... possibly RAM.

    Have you updated drivers recently?

    Possibly video drivers, as you say it's Photoshop and games, which are likely to be graphics and/or RAM intensive.

    It would help if you mentioned your OS and PC configuration.

    Googling the error comes up with several suggestions.


    Thanks alot!!!
    This solved my problem!!!

  • #10
    Crazy Diamond
    Tiny's Avatar
    Join Date
    Dec 2010
    Location
    Tasmania
    Age
    64
    Posts
    6,391
    Thanks
    10,996
    Thanked 5,436 Times in 2,651 Posts
    Rep Power
    2156
    Reputation
    89057

    Default

    Quote Originally Posted by mhansomme View Post
    Thanks alot!!!
    This solved my problem!!!
    That's great, good outcome.

    So was it video card driver or Ram??
    Cheers, Tiny
    "You can lead a person to knowledge, but you can't make them think? If you're not part of the solution, you're part of the problem.
    The information is out there; you just have to let it in."

  • #11
    Administrator
    mtv's Avatar
    Join Date
    Jan 2008
    Posts
    19,893
    Thanks
    7,508
    Thanked 15,066 Times in 6,761 Posts
    Rep Power
    5647
    Reputation
    239305

    Default

    Quote Originally Posted by mhansomme View Post
    Thanks alot!!!
    This solved my problem!!!
    Pleased you got it sorted.

    What was the problem and what did you do to fix it?

  • #12
    Junior Member
    Join Date
    Mar 2012
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    Rep Power
    0
    Reputation
    30

    Default

    Hey guys,

    I have been out for a while so I am just getting the chance to report back to you guys.
    Sorry. Be patient with me guys. It turns out that there was an incompatible or outdated third party driver installed on my device which was causing the conflict. It was a problematic video driver I'd say. To fix the problem I had to remove the third party driver.

  • The Following 2 Users Say Thank You to mhansomme For This Useful Post:

    mtv (13-08-14),Tiny (13-08-14)

  • Bookmarks

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •