Jump to content

Re: Lockup issues! Post here please


Nyarlathotep
 Share

Recommended Posts

Guest Cannibal Snowman

ok i tested them and this was what happened.

sound: tested good

music: tested good

video: problem. it tested good on DirectX 7, but it said "Failure at Step 5 (3d not available)" or something like that when it tested DirectX 8

[This message has been edited by Cannibal Snowman (edited 04-02-2002).]

Link to comment
Share on other sites

hey mad mine is broken too ( .*. )

had it handed to me on a platter last nite in a 2v1 :D

( .*. )

______ did someone order an @ss on a platter

sorry doc am done... will stick to topic...

[This message has been edited by djcid (edited 04-03-2002).]

Link to comment
Share on other sites

Guest Eagle-

Ey Doc,

Would you have any info on problems under Win2k ??

Have been following yr replies and suggestions here, tried them out. Also those on yr sascho website. But to no avail.

Game keeps crashing. It will let me play for about 5 minutes (no difference for MP or SP) and then the pc crashes with alternating stop errors. Either 0x01e or 0x00a.

Strange thing is that on my portable the game is running without any problems. Must say that there I am running win2k pro and on my desktop (with the crashes) win2k server.

Have already tried disabling everything unnecessary, upgraded all my drivers etc, changed a couple things in my bios and in my nvidia settings (according to yr website) but nothing helps.

Anymore suggestions or have you heard of other people who r running the game under win2k server ?

Tnx !!

Link to comment
Share on other sites

Guest Eagle-

Doc,

Hm, don't really like posting a long list like that here, no wonder this topic is 39 pages long ...

Anyway, here it goes, hope it will help you (and me) :)

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

System Information

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

Time of this report: 4/4/2002, 17:08:02

Machine name: DATAMINI

Operating System: Microsoft Windows 2000 Server (5.0, Build 2195) Service Pack 2

Language: English (Regional Setting: English)

System Manufacturer: American Megatrends Inc.

System Model: VIA694X/686A

BIOS: Version 1.00

Processor: Intel Pentium III, ~864MHz

Memory: 384MB RAM

Page File: 160MB used, 382MB available

Primary File System: NTFS

DirectX Version: DirectX 8.1 (4.08.01.0881)

DX Setup Parameters: Not found

DxDiag Version: 5.01.2600.0881 32bit Unicode

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

DxDiag Notes

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

DirectX Files Tab: No problems found.

Display Tab 1: The file nv4_disp.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs. You may be able to get a signed driver from the manufacturer of the hardware device.

DirectDraw test results: All tests were successful.

Direct3D test results: All tests were successful.

Sound Tab 1: DirectSound test results: All tests were successful.

Music Tab: DirectMusic test results: All tests were successful.

Input Tab: No input devices detected.

No problems found.

Network Tab: The registry information for the DirectPlay application 'Submarine Titans' is missing or damaged. You should reinstall that application.

DirectPlay test results: All tests were successful.

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

DirectX Components

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

ddraw.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 252416 bytes

ddrawex.dll: 5.00.2134.0001 English Final Retail 12/7/1999 20:00:00 24336 bytes

dxapi.sys: 5.00.2180.0001 English Final Retail 12/15/1999 00:00:00 10064 bytes

d3d8.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 1178624 bytes

d3dref8.dll: 5.01.2258.0400 English Final Retail 11/7/2000 15:16:46 181760 bytes

d3dim.dll: 5.00.2180.0001 English Final Retail 12/15/1999 00:00:00 446224 bytes

d3dim700.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 791040 bytes

d3dref.dll: 5.01.2258.0400 English Final Retail 11/7/2000 15:16:46 90112 bytes

d3dramp.dll: 5.00.2180.0001 English Final Retail 12/15/1999 00:00:00 591120 bytes

d3drm.dll: 5.00.2134.0001 English Final Retail 12/15/1999 00:00:00 364816 bytes

d3dxof.dll: 5.00.2135.0001 English Final Retail 12/15/1999 00:00:00 49424 bytes

d3dpmesh.dll: 5.00.2134.0001 English Final Retail 12/15/1999 00:00:00 37648 bytes

dplayx.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 213504 bytes

dpmodemx.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 20992 bytes

dpwsockx.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 50176 bytes

dplaysvr.exe: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 26624 bytes

dpnsvr.exe: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 18944 bytes

dpnet.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 156672 bytes

dpnlobby.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 38912 bytes

dpnwsock.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 61952 bytes

dpnaddr.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 26624 bytes

dpnmodem.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 62464 bytes

dpvoice.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 206336 bytes

dpvsetup.exe: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 59904 bytes

dpvvox.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 113152 bytes

dpvacm.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 24064 bytes

dpnhpast.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 30208 bytes

dpnhupnp.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 55808 bytes

dinput.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 150016 bytes

dinput8.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 166400 bytes

dimap.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 44032 bytes

diactfrm.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 386048 bytes

joy.cpl: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 75264 bytes

gcdef.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 61440 bytes

pid.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 31744 bytes

gameenum.sys: 5.00.2134.0001 English Final Retail 9/25/1999 18:35:58 9552 bytes

dsound.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 330752 bytes

dsound3d.dll: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 1294336 bytes

dswave.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 15872 bytes

dsdmo.dll: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 176128 bytes

dsdmoprp.dll: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 66560 bytes

dmusic.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 93696 bytes

dmband.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 26112 bytes

dmcompos.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 59904 bytes

dmime.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 170496 bytes

dmloader.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 31232 bytes

dmstyle.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 110592 bytes

dmsynth.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 132096 bytes

dmscript.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 78848 bytes

dx7vb.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 595456 bytes

dx8vb.dll: 5.01.2600.0881 English Final Retail 10/30/2001 08:10:00 1187840 bytes

mfc40.dll: 4.01.00.6140 English Final Retail 12/7/1999 20:00:00 924432 bytes

mfc42.dll: 6.00.8665.0000 English Beta Retail 12/7/1999 20:00:00 995383 bytes

wsock32.dll: 5.00.2195.2871 English Final Retail 5/4/2001 12:05:02 21776 bytes

amstream.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 62976 bytes

devenum.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 49664 bytes

dxmasf.dll: 6.04.09.1121 English Final Retail 9/21/2001 14:39:24 498960 bytes

mciqtz32.dll: 6.03.01.0400 English Final Retail 10/30/2001 08:10:00 33792 bytes

mpg2splt.ax: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 148992 bytes

msdmo.dll: 6.03.01.0400 English Final Retail 10/30/2001 08:10:00 11264 bytes

qasf.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 152576 bytes

qcap.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 167936 bytes

qdv.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 229888 bytes

qdvd.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 347136 bytes

qedit.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 517120 bytes

qedwipes.dll: 6.03.01.0400 English Final Retail 10/30/2001 08:10:00 734208 bytes

quartz.dll: 6.03.01.0881 English Final Retail 10/30/2001 08:10:00 999936 bytes

strmdll.dll: 4.01.00.3925 English Final Retail 4/20/2001 13:14:22 251904 bytes

iac25_32.ax: 2.00.05.0053 English Final Retail 12/7/1999 20:00:00 199680 bytes

ir41_32.ax: 4.51.16.0003 English Final Retail 12/7/1999 20:00:00 848384 bytes

ir41_qc.dll: 4.30.62.0002 English Final Retail 12/7/1999 20:00:00 120320 bytes

ir41_qcx.dll: 4.30.64.0001 English Final Retail 4/10/2001 14:51:07 338432 bytes

ir50_32.dll: 5.2562.15.0055 English Final Retail 12/7/1999 20:00:00 755200 bytes

ir50_qc.dll: 5.00.63.0048 English Final Retail 12/7/1999 20:00:00 200192 bytes

ir50_qcx.dll: 5.00.64.0048 English Final Retail 12/7/1999 20:00:00 183808 bytes

ivfsrc.ax: 5.10.02.0051 English Final Retail 12/7/1999 20:00:00 154624 bytes

mswebdvd.dll: 6.03.01.0400 English Final Retail 10/30/2001 08:10:00 244224 bytes

ks.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 121344 bytes

ksproxy.ax: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 116736 bytes

ksuser.dll: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 4096 bytes

stream.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 41792 bytes

mspclock.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 4800 bytes

mspqm.sys: 5.00.2134.0001 English Final Retail 9/25/1999 18:36:32 4816 bytes

mskssrv.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 6400 bytes

swenum.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 3456 bytes

mstee.sys: 5.01.2258.0400 English Final Retail 10/30/2001 08:10:00 4896 bytes

bdaplgin.ax: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 14336 bytes

bdasup.sys: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 4992 bytes

msdvbnp.ax: 6.03.01.0400 English Final Retail 10/8/2001 12:58:38 51200 bytes

psisdecd.dll: 6.03.01.0400 English Final Retail 10/8/2001 12:58:38 365568 bytes

psisrndr.ax: 6.03.01.0400 English Final Retail 10/8/2001 12:58:38 35840 bytes

ipsink.ax: 5.01.2600.0881 English Final Retail 10/16/2001 08:17:14 13824 bytes

ndisip.sys: 5.01.2600.0881 English Final Retail 10/16/2001 08:17:14 7840 bytes

mpe.sys: 5.01.2600.0881 English Final Retail 10/16/2001 08:17:14 13952 bytes

streamip.sys: 5.01.2600.0881 English Final Retail 10/16/2001 08:17:14 14400 bytes

msvidctl.dll: 6.03.01.0400 English Final Retail 10/8/2001 12:58:38 464384 bytes

slip.sys: 5.01.2600.0881 English Final Retail 10/16/2001 08:17:14 10368 bytes

nabtsfec.sys: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:38 86016 bytes

ccdecode.sys: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 15264 bytes

vbisurf.ax: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:38 30208 bytes

msyuv.dll: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:38 14336 bytes

kstvtune.ax: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 52736 bytes

ksxbar.ax: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 37888 bytes

kswdmcap.ax: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:36 82944 bytes

wstdecod.dll: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:40 45568 bytes

msdv.sys: 5.01.2258.0400 English Final Retail 10/8/2001 12:58:38 55968 bytes

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

Display Devices

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

Card name: NVIDIA RIVA TNT2 Model 64/Model 64 Pro

Manufacturer: NVIDIA

Chip type: RIVA TNT2 Model 64

DAC type: Integrated RAMDAC

Device ID: EnumPCIVEN_10DE&DEV_002D&SUBSYS_00000000&REV_15

Display Memory: 32.0 MB

Current Mode: 1024 x 768 (16 bit) (60Hz)

Monitor: Plug and Play Monitor

Monitor Max Res: 1600,1200

Driver Name: nv4_disp.dll

Driver Version: 6.13.10.2311 (English)

DDI Version: 7

Driver Attributes: Final Retail

Driver Date/Size: 11/29/2001 01:28:00, 3549225 bytes

Driver Signed: No

WHQL Date Stamp: None

VDD:

Mini VDD: nv4_mini.sys

Mini VDD Date: 11/29/2001 01:28:00, 793065 bytes

Device Identifier: {D7B71E3E-436D-11CF-B76A-0A20B7C2CB35}

Vendor ID: 0x10DE

Device ID: 0x002D

SubSys ID: 0x00000000

Revision ID: 0x0015

Registry: OK

DDraw Status: Enabled

D3D Status: Enabled

AGP Status: Enabled

DDraw Test Result: All tests were successful.

D3D7 Test Result: All tests were successful.

D3D8 Test Result: All tests were successful.

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

Sound Devices

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

Description: SB Live! Wave Device

Device ID: PCIVEN_1102&DEV_0002&SUBSYS_80611102&REV_07

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: emu10k1f.sys

Driver Version: 5.12.01.3509 (English)

Driver Attributes: Final Retail

Driver Signed: Yes

Date and Size: 8/14/2001 15:17:52, 775296 bytes

Other Files:

Driver Provider: Creative

HW Accel Level: Full

Registry: OK

Sound Test Result: All tests were successful.

-----------

DirectMusic

-----------

DLS Path: C:WINNTSYSTEM32driversGM.DLS

Version: 1.00.16.0002

Ports:

Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port

SB Live! Wave Device, Software (Kernel Mode), Output, DLS, Internal

Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal

A: SB Live! MIDI Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal

B: SB Live! MIDI Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal

SB Live! Soft Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal

SB Live! MIDI UART [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External

Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal

SB Live! MIDI UART [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External

Registry: OK

Music Test Result: All tests were successful.

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

DirectShow Filters

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

WDM Streaming VBI Codecs:

NABTS/FEC VBI Codec,0x00200000,2,1,ksproxy.ax,5.01.2258.0400

CC Decoder,0x00200000,2,1,ksproxy.ax,5.01.2258.0400

WST Codec,0x00200000,1,1,ksproxy.ax,5.01.2258.0400

DirectShow Filters:

WMAudio Decoder DMO,0x00600800,1,1,,

WMVideo 8 Decoder DMO,0x00800001,1,1,,

MSScreen decoder DMO,0x00600800,1,1,,

WMVideo Decoder DMO,0x00800001,1,1,,

Mpeg4 Decoder DMO,0x00800001,1,1,,

RTP Source Filter,0x00200000,0,1,dxmrtp.dll,5.00.2195.2290

RTP Render Filter,0x00200000,1,0,dxmrtp.dll,5.00.2195.2290

Full Screen Renderer,0x00200000,1,0,quartz.dll,6.03.01.0881

DV Muxer,0x00400000,0,0,qdv.dll,6.03.01.0881

Color Space Converter,0x00400000,1,1,quartz.dll,6.03.01.0881

WM ASF Reader,0x00400000,0,0,qasf.dll,6.03.01.0881

Intel RTP SPH for G.711/G.723.1,0x00200000,1,1,dxmrtp.dll,5.00.2195.2290

AVI Splitter,0x00600000,1,1,quartz.dll,6.03.01.0881

VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,6.03.01.0881

Indeo

Link to comment
Share on other sites

Eagle, for one, you haven't got the latest Nvidia drivers.. Download the latest and try again. Also, there are known issues concerning VIA and Creative. Make sure you've got the latest VIA chipset drivers downloaded..

Regarding the stop error.. this could be due to several things, but I need a more detailed message to be able to tell you what yours means. Stop errors are generated by not having the right Service pack, wrong drivers (or conflicting), or BIOS settings..

Try updating the drivers first and keep me updated !

"Doc" Nyar...

Link to comment
Share on other sites

Guest Eagle-

Ey Doc,

I installed the latest nVidia drivers couple days ago, but they gave me a lot of problems (crashing, unstable), so I went back to the ones before that.

Regarding latest SP's and drivers, I am up to date, since I am a freak :) in keeping all drivers up to date.

About VIA, well, I know that for some time now, if I had known that before I bought this motherboard, I would never have bought is. Horribly bad quality. I want only intel chipsets anymore, but hey, have to do with VIA for now.

Will copy/paste the error msg's below:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xe394fbea, 0x00000000, 0x06ee79e0). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:WINNTMinidumpMini040402-03.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000004, 0x00000002, 0x00000001, 0x80431c22). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:WINNTMinidumpMini040402-01.dmp.

Euh, what else to say ? Dunno, anything more I should tell you ?

Have you heard before about problems with emperor and Win2k server ?

Link to comment
Share on other sites

Crazy, I haven't studied for it.. I flunked school and got kicked off. My teacher told me I would end up in the gutter.. a couple of months ago I saw him on his bike in the rain.. I waved to him while I was driving my new BMW :D

What I know now is due to doing my own research and trying stuff.. But I didn't study for it..

"Doc" Nyar...

Link to comment
Share on other sites

Guest Eagle-

I think that for a lot of people it is like that.

I never followed ANY classes whatsoever related to computers, but still, people are asking me all the time to solve their problems. Just not related to games and crashing because of them, in that field I don't know much.

Link to comment
Share on other sites

Eagle, EBFD should run on your system without a doubt !

About the error messages (I assume it only happens while playing EBFD ?)..

1) Check your BIOS settings for anything incorrect (your RAM speed for example). Check the manual for your motherboard for detailed explanation on the settings.

2) Update your BIOS.

3) Try to run the game with the option -s behind the game's shortcut.

4) If you have any Norton programs installed, please uninstall and try to run the game again.

More explanation on the error message and how to retrieve more information:

The description and format of the event log differs from the format that is displayed when the computer is writing the Memory.dmp file, but the majority of the information is the same. Below is an example of the event log:

Event ID: 1001

Source: Save Dump

Description:

The computer has rebooted from a bugcheck. The bugcheck was : 0xc000021a (0xe1270188, 0x00000001, 0x00000000, 0x00000000).

Microsoft Windows NT (v15.1381). A dump was saved in: C:WINNTMEMORY.DMP.

This information contains the stop code 0xc000021a and the four parameters. These can be very useful when troubleshooting certain types of stop codes. The parameters will mean different things depending on what type of stop code it is.

If you use Dumpchk.exe from the Service Pack 3 CD, you can determine all of the above information as well as the address of the driver that generated the stop message. This information can often give you a direction to begin troubleshooting. Before you run Dumpchk.exe, be sure to adjust the properties of the command prompt so that the screen buffer size height is set to 999.

This height will allow you to scroll back to see the output. Run Dumpchk.exe from the command prompt with the following syntax:

dumpchk.exe Memory.dmp

This is an example of the portions of the output that are most useful:

MachineImageType i386

NumberProcessors 1

BugCheckCode 0xc000021a

BugCheckParameter1 0xe1270188

BugCheckParameter2 0x00000001

BugCheckParameter3 0x00000000

BugCheckParameter4 0x00000000

ExceptionCode 0x80000003

ExceptionFlags 0x00000001

ExceptionAddress 0x8014fb84

Note that not all sections will give the same information. This will depend on the type of stop code. The information above tells you the stop code (0xc000021a) and the parameters (0xe1270188, 0x00000001, 0x00000000, 0x00000000), as well as the address of the driver that called the exception (0x8014fb84). This address can be used to identify the driver name by using the output from running Pstat.exe, which can be found in the Resource Kit. Dumpchk.exe will also verify that the dump is valid.

Pstat.exe, a Resource Kit utility, will give you a picture of the processes and drivers currently running on your system. For these purposes, the most useful information will be the list of loaded drivers that appears at the end of the output. All you need to do is run Pstat.exe from the command line. The information given by Pstat.exe can be piped to a file by using the following syntax:

pstat.exe > filename

This is an example of the driver list at the end of the output (hope it comes out right):

ModuleName Load Addr Code Data Paged LinkDate

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

ntoskrnl.exe 80100000 270272 40064 434816 Sun May 11 00:10:39 1997

hal.dll 80010000 20384 2720 9344 Mon Mar 10 16:39:20 1997

aic78xx.sys 80001000 20512 2272 0 Sat Apr 05 21:16:21 1997

SCSIPORT.SYS 801d7000 9824 32 15552 Mon Mar 10 16:42:27 1997

Disk.sys 80008000 3328 0 7072 Thu Apr 24 22:27:46 1997

CLASS2.SYS 8000c000 7040 0 1632 Thu Apr 24 22:23:43 1997

INO_FLPY.SYS 801df000 9152 1472 2080 Tue May 26 18:21:40 1998

Ntfs.sys 801e3000 68160 5408 269632 Thu Apr 17 22:02:31 1997

Floppy.SYS f7290000 1088 672 7968 Wed Jul 17 00:31:09 1996

Cdrom.SYS f72a0000 12608 32 3072 Wed Jul 17 00:31:29 1996

Cdaudio.SYS f72b8000 960 0 14912 Mon Mar 17 18:21:15 1997

Null.SYS f75c9000 0 0 288 Wed Jul 17 00:31:21 1996

KSecDD.SYS f7464000 1280 224 3456 Wed Jul 17 20:34:19 1996

By using the starting address shown above under the "load addr" column, you can match the exception address to the driver name. Using 8014fb84 as an example, you can determine that Ntoskrnl.exe has the nearest load address below the exception address and is most likely the driver that called the exception.

"Doc" Nyar...

Link to comment
Share on other sites

Guest Eagle-

Ey Doc,

Tnx for long explanation.

I have been able to get the following information.

Downloaded the Ms Customer Debugging tools (100MB) which included the dumpchk.exe file (since I don't have the resource kit).

With that I made a printout of the memory dumps I had.

But it is too much for me to go analyse the output. I don't understand the debugging or the assembly code in there. If you want, I can copy/paste the output of the debug files here, so that you can have a look at it.

What I did find is:

0x01e: kmode_exception_not_handled

with exception code: 0xC0000005: STATUS_ACCESS_VIOLATION. A memory access violation occurred. (Parameter 4 of the bug check is the address which the driver attempted to access.)

0x00a: IRQL_NOT_LESS_OR_EQUAL This signals that the driver accessed paged memory at DISPATCH_LEVEL or above.

That is about it what I can tell you about it now. Does it help you in saying what is wrong ?

You are talking about Norton, I do have the antivirus installed. Will try out if I deactivate those processes from memory, if that will help.

Will also try the -s option.

Tnx already !!

Link to comment
Share on other sites

Eagle, feel free to post that output here.. who knows, it may contribute to solving your problem.

"0x01e: kmode_exception_not_handled" still could mean several things. How ever, I bet on a driver issue or a program that you have installed.

1) Do you have "Logitech MouseWare" installed ? If so, upgrade it.

2) Make sure that the drivers you have installed, are microsoft certified. There are ocasions that this error comes up whith drivers that are not microsoft certified.

3) Make sure you have checked the BIOS settings..

4) If you can, try to install your videovard as a default VGA adapter.

Keep me updated !

"Doc" Nyar...

Link to comment
Share on other sites

Guest Eagle-

Ey Doc,

Will be out for the weekend. Will continue on monday with this and yr hints.

Have a nice weekend !

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...