well i can't believe dosbox is too blame except for the fact that dosbox may warm your pc up.

Bluescreens make me feel loved. They are my friends.

Darlcon wrote:

The error number that came up with the blue screen of death were 0x000000C2 (0x00000CD4 0x20676E69 0x8060F986)

It looks like there is a problem in some device driver. According to the Microsoft KB, 0xC2 errors are caused by faulty memory management inside a device driver. Take a look at those articles: 265879 and 314492.

Darlcon wrote:

I know there's a site you can look this up at

A quick way to find more about blue screen errors is to open the MS support site and do a search for "stop" and the error code, even without the leading zeros. In this case i simply did a search for "stop 0xc2".

Darlcon wrote:

I'm really looking to understand what's causing this, and what I can do to stop it from causing this.

If there is a problem with a device driver, the first step is to locate which driver is responsible for the problem. Can you set your system to generate a small memory dump at each error, as explained in article 315263? Never mind the instructions about the debuggin tools, just make sure that the settings to generate the mini dumps are correct. You could then reproduce the problem, reboot your machine and run DUMPCHK in the generated dump. Post the start of the dump here, without the messages about validation of the file. With some luck we will be able to locate the faulty driver.

Regards,

Given the fact that so many times on this forum a faulty graphics driver was to blame, I'd start looking there...

JAL

One issue, I don't appear to have dumpchk on my system, and the last time I moved houses(and cities infact) several boxes were "lost" to the moving company, one of which contained many of my CDs such as my windows CD... Is there any way, that you know of, that I could get dumpchk without having the WIN XP CD? Would I be able to install the file from a friend's WIN XP CD?

Btw, the latest error code I got when my computer crashed(thru blue screen of death) was an 0x0A error while just letting my computer "idle" with only dosbox running(with a game, XCOM 1, sitting idle in it as well). I looked it up to see that it "indicates that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address."

Qbix ---> the reason that I brought this up in this forum was because dosbox was the only new software I'd installed onto my computer within the week before the problem started occuring. When I tried playing a seperate game(which I haven't ever had a regular problem with) with no relation to the Dosbox, after I'd had a couple BSoD's crash my computer, it ended up giving me a BSoD as well(can't find my papers with the error codes on it). The only other time I had a problem like this was with a previous harddrive(since removed) when a different program messed things up. Thus it's a fairly large concern I have into hopefully fixing said issue of the BSoD appearing...

whoops, forgot to login, that was me above if you couldn't guess. 😜

Did you try updating your video drivers as suggested?

Just did that last night after posting. Still having my computer crash when running both programs(although the main concern here is obviously the Dosbox as it's their forums AND what seems to have ignited the problem). :s

Still looking for an answer as to dumchk, my WINXP CD being lost in a move can I get the tool off a friend's CD or must it be the exact copy that I installed it with? I'm off to find my friend and find his XP CD to try regardless, but was hoping for an answer right away while I was busy with RL things.

In the continuing tradition of shooting in the dark, you may have bad RAM.
Try memtest.

Not to shoot down your reply, but wouldn't other games crash as well (and in a similar fashion/code #) were it bad RAM? I've played a couple other games on here that are more memory demanding than the aforementioned game and they don't seem to have problems... :s

Also, I can't seem to figure out how to run the test from memtest... I've made the bootdisk for it, but it says that you just need to have the disk in when you reboot. I'm running XP(not sure if that matters for the process of rebooting properly), and when I reboot it doesn't mention anything or even pause to consider the diskette in the drive...

I wasn't quite sure what was meant when you wanted just the start of it. I did a "dumpchk p"(headers without validation) of a couple of them. They are the first 2 times it gave me the BSoD while running dosbox I believe.

Loading dump file mini080904-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0f8e6000
PfnDataBase 80543e58
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 000000d1
BugCheckParameter1 ffffffbd
BugCheckParameter2 000000ff
BugCheckParameter3 00000000
BugCheckParameter4 ffffffbd
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 000004ff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 00000740
DriverListOffset 000030f0
DriverCount 00000078
StringPoolOffset 00005490
StringPoolSize 00002488
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack f60498c0
DebuggerDataOffset 00002e60
DebuggerDataSize 00000290

Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Mon Aug 09 16:58:35 2004
System Uptime: 4 days 19:19:09
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr 24 08:
57:43 2003 (3EA80977)

Unloaded modules:
f5beb000 f5bfb000 NAVENG.Sys Timestamp: unavailable (00000000)
ef77e000 ef814000 NavEx15.Sys Timestamp: unavailable (00000000)
f58db000 f58eb000 NAVENG.Sys Timestamp: unavailable (00000000)
ef77e000 ef814000 NavEx15.Sys Timestamp: unavailable (00000000)
f4a2d000 f4a3d000 NAVENG.Sys Timestamp: unavailable (00000000)
ef825000 ef8bb000 NavEx15.Sys Timestamp: unavailable (00000000)
f9e3a000 f9e40000 LwAdiHid.sys Timestamp: unavailable (00000000)
f6538000 f6548000 NAVENG.Sys Timestamp: unavailable (00000000)
ef825000 ef8bb000 NavEx15.Sys Timestamp: unavailable (00000000)
f4a8d000 f4a9d000 NAVENG.Sys Timestamp: unavailable (00000000)
f036d000 f0403000 NavEx15.Sys Timestamp: unavailable (00000000)
f9e32000 f9e38000 LwAdiHid.sys Timestamp: unavailable (00000000)
f605a000 f606a000 NAVENG.Sys Timestamp: unavailable (00000000)
f036d000 f0403000 NavEx15.Sys Timestamp: unavailable (00000000)
f4cbd000 f4ccd000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f4e23000 f4e33000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
ed428000 ed44f000 kmixer.sys Timestamp: unavailable (00000000)
f1bef000 f1bff000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f1bcf000 f1bdf000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
ed428000 ed44f000 kmixer.sys Timestamp: unavailable (00000000)
f4e23000 f4e33000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f601a000 f602a000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f603a000 f6048000 swmidi.sys Timestamp: unavailable (00000000)
ed428000 ed44f000 kmixer.sys Timestamp: unavailable (00000000)
f1d0c000 f1d1c000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f584b000 f585b000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f4e13000 f4e23000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f4cbd000 f4ccd000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f57b3000 f57c3000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f4e63000 f4e73000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f83b5000 f83c5000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f1d4c000 f1d5c000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f4ef3000 f4f03000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)
f5a53000 f5a63000 NAVENG.Sys Timestamp: unavailable (00000000)
ed470000 ed506000 NavEx15.Sys Timestamp: unavailable (00000000)

Finished dump check

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Loading dump file mini080904-02.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0e00d000
PfnDataBase 80543e58
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000000a
BugCheckParameter1 00000000
BugCheckParameter2 00000002
BugCheckParameter3 00000001
BugCheckParameter4 804fb018
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 000004ff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 00000654
DriverListOffset 00003008
DriverCount 00000078
StringPoolOffset 000053a8
StringPoolSize 00002488
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack f83439ac
DebuggerDataOffset 00002d78
DebuggerDataSize 00000290

Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Mon Aug 09 17:14:15 2004
System Uptime: 0 days 0:14:28
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr 24 08:
57:43 2003 (3EA80977)

Unloaded modules:
f5c1b000 f5c2b000 NAVENG.Sys Timestamp: unavailable (00000000)
f43f0000 f4486000 NavEx15.Sys Timestamp: unavailable (00000000)
f61d3000 f61e3000 NAVENG.Sys Timestamp: unavailable (00000000)
f43f0000 f4486000 NavEx15.Sys Timestamp: unavailable (00000000)
f9bf2000 f9c02000 NAVENG.Sys Timestamp: unavailable (00000000)
f81da000 f8270000 NavEx15.Sys Timestamp: unavailable (00000000)
fa022000 fa023000 drmkaud.sys Timestamp: unavailable (00000000)
f61d3000 f61e0000 DMusic.sys Timestamp: unavailable (00000000)
f608d000 f60b0000 aec.sys Timestamp: unavailable (00000000)
f9fd0000 f9fd2000 splitter.sys Timestamp: unavailable (00000000)
f9d2a000 f9d30000 LwAdiHid.sys Timestamp: unavailable (00000000)
f9e12000 f9e1a000 processr.sys Timestamp: unavailable (00000000)
f9dc2000 f9dc7000 Cdaudio.SYS Timestamp: unavailable (00000000)
f9ede000 f9ee1000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

~~~~~~~~~~~~~~

I hope this is what's needed to help sort it out. I have a number of other dumpchks(a few for the other game that started BSoD'ing me as well) if you'd like to look at them. If you want me to run dumpchk in a different fashion(just normally, or with whatever specific command) just ask. I'll get it up here asap. 😀

Is there anyone around with the expertise to help a stranded gamer?

I know these forums are fairly busy with other help needed for other issues. Is there no one that can clear up this issue with me?

Even lead me in the right direction to head from that information I've posted?

Check that there is not anything overheating (chipset, graphic, processor).
If yes, then change the fan or add a new one.
If no, then reinstall Windows (it takes some time, but it is very good method to solve mysterious problems).

Mirek

Yes, it would be recommended (even though it is a pain and stupid) to reinstall windows every couple of years. It's been like this through pretty much all Microft Windows OS incarnations that strange bugs pop up for no explicable reason and doing a wipe and reinstall of Windows usually solves it.
(I recommend backing up all your precious information onto CDs or Iomega ZIP disks before doing so.)
Also I dunno but I hear both good and bad sides of the SP2 update for Windows XP but since it's not available as a download except only for the whopping 266 mb Network Developer or IT professional download , as an automatic update through microsoft.windowsupdate.com, and as a (completely) free order cd from Microsoft except you have to wait 4-6 weeks. (I'm doing the latter)

But if you're getting a blue screen of death I assume you're not using XP.. or maybe you are.. I have not yet gotten a BSoD on Windows XP. I've seen the blue screen every now and then when Windows XP had the idea that my E parition was a little funky for a few days but no BSoD yet.

Oh lord, not reinstalling windows AGAIN... I just did that about 7 months ago when something through Kazaa created some bad sectors on my HD and it simply wouldn't load any games, etc. off it(ALL my games were on that HD). I still have the HD as if I load up a couple of the games onto my new HD I have saved files I can transfer over, but anyways.

I am running XP pro, I've had great luck in having the BSoD appear on two occasions in the last year. One was the aforementioned HD f'up, the other is this instance. I removed dosbox a while ago, fixed up a couple things and the game I mentioned earlier in the thread has stopped screwing up(had some corrupt drivers, as was suspected when I learned what the BSoD stop code for that stop meant).

Nothing's been overheating that I know of, I added a new fan anyways but my computer's generally fairly cool. Need to find out how to check my RAM to see if there's a problem there, provided I get the same problem when I redownload dosbox tonight.

Thanks for the suggestions tho, reinstalling windows is always a last chance option in my books but it's always an option to help.

Maybe you couldn't boot with your Memtest diskette, because you haven't checked in the BIOS the boot secuence. You have to set the floppy drive (or CD, depends on what media you've used) as the first booting device.
If you need help doing this, I'm here to help 😀

In your dump there are quite a lot of occurences of nav*.sys.
Seems to me, Norton Antivirus is causing you troubles, maybe because of a faulty installation or an outdated version.
Maybe you should check this...

Qbix -> I changed your avatar without green pixel on all the edge ! do you want it ??? It's better version ... with no antialias ... 😀

contact me ! 😀