Menu

blue-screen crash at debugging

2004-08-18
2012-09-26
  • Nobody/Anonymous

    Everything is fine, but during debugging
    I got a blue-screen death. Crash occurs only
    at debugging manipulations, such as stop executed program, or just start of debugging.

    Blue screen says: error OE at address:
    0028:C00316FC. Base value 0028 always the same, but offset (last 5 digits) vary.

    System: Win98 SE. Memory 64 k.

    Thanks to everyone

     
    • Wayne Keen

      Wayne Keen - 2004-08-18

      64K of memory?  I think your units are wrong there.

      What version of Dev are you running?

      Wayne

       
    • Nobody/Anonymous

      (1) if possible upgrade to either NT 4.0, Windows 2000, or XP. The Win9x platform is pretty bad development - a stray pointer is very likely to result in s BSOD

      Assuming you can't upgrade your OS ...

      (2) Is your machine overclocked? Or do you have overly aggressive memory timings? You may need to slow down your machine, or make your memory timings less agressive.

      (3) There are a few knowledge base articles at www.microsoft.com (search on error 0E). One of these may apply to you:

      http://support.microsoft.com/default.aspx?scid=kb;en-us;190915
      http://support.microsoft.com/default.aspx?scid=kb;en-us;243037
      http://support.microsoft.com/default.aspx?scid=kb;en-us;302826
      http://support.microsoft.com/default.aspx?scid=kb;en-us;187214
      http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=error+0e

      (4) You might try repairing your installation. Usually the simplest is to go to Control Panel -> Add/Remove Programs -> Internet explorer and choose the repair option.

      (5) as a last resort FORMAT C: and reinstall windows.

      (6) I've also heard that anti-virus programs may cause grief.

      In addition to saying error 0E, it should also tell you which module the error occured in (vwin32, wserver, vios, etc ...)

      rr

       
    • Nobody/Anonymous

      Sorry guys for a pause.

      2 Waynee:

      Of course is 46 megs of memory :DD.
      Dev-C++ is 4.9.9.0.

      2 rr:
      (1)
      Well, I have another machine with 512 megs and XP, so will see.

      (2)
      No, I didn't overklock machine. All timings for mem
      and proc are default factory values.

      (3)
      OK, Thanks a lot for this one.

      (4)
      Sorry, why do you think that other stuff  installed
      may evoke error in dev-c++? Or you mean reinstall
      dev-c++?
      BTW, on the same machine i can start such heavy
      soft as corel draw, corel photopaint etc. It's slow
      but works.

      (5)
      :-(

      ()

       
      • Nobody/Anonymous

        My suggestions are simply wild guesses on what the problem could be.

        Unfortunately, you have to do all the detective work. I can only suggest places to look.

        Obviously, FORMAT C: is a last resort (and who knows, maybe installing and reinstalling dev-cpp might fix the problem).

        The reason I suggested fixing Internet Explorer because it often fixes much more than internet explorer itself (and because there is no fix windows options).

        rr

         
    • Nobody/Anonymous

      *I'm getting the same problem...*

      I have a Pentium 3 650 with 64 ram running Windows 98 (i think SE, not sure)...
      When i ask for stop the execution of the debugging program, the blue-screen-of-death comes and freezes everything... i have to restart my computer...
      I think this bug is in the Dev-cpp...

       
    • Nobody/Anonymous

      Yes. IMHO the problem is in Dev-C++.
      It would be very nice if guys overlooked
      the code responsible for debugging.
      I'm trying to locate at which operation
      the crash most often.

      Thanks

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.