Server 2003 Stop Error - Please Help!!! :(

Help.

We have built a server for a customer and its now on-site and chucking up the same stop error at least twice a day. This company relies v. heavily on their I.T. and the matter urgently needs to be resolved

I noticed people have been pasting their stop errors on this forum and there are some really really nice people who actually help.

Please help


My memory dump is as follows.


Filename . . . . . . .C:\WINDOWS\MEMORY.DMP
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .3790
DirectoryTableBase . .0x00039000
PfnDataBase. . . . . .0x81000000
PsLoadedModuleList . .0x80568c08
PsActiveProcessHead. .0x8056ede8
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x0000007f
BugCheckParameter1 . .0x00000008
BugCheckParameter2 . .0x80042000
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x8053eec8

NumberOfRuns . . . . .0x2
NumberOfPages. . . . .0x3ff8f
Run #1
BasePage . . . . . .0x1
PageCount. . . . . .0x9f
Run #2
BasePage . . . . . .0x100
PageCount. . . . . .0x3fef0


**************
**************--> Validating the integrity of the PsLoadedModuleList
**************
validating ntoskrnl.exe 0x804de000 0x00235000
validating hal.dll 0x80713000 0x00028000
validating kdcom.dll 0xf7707000 0x00008000
validating BOOTVID.dll 0xf770f000 0x00008000
validating ACPI.sys 0xf7435000 0x00031000
validating WMILIB.SYS 0xf7487000 0x00009000
validating pci.sys 0xf7420000 0x00015000
validating isapnp.sys 0xf7497000 0x0000f000
validating ohci1394.sys 0xf74a7000 0x0000f000
validating 1394BUS.SYS 0xf74b7000 0x0000d000
validating pciide.sys 0xf7717000 0x00007000
validating PCIIDEX.SYS 0xf74c7000 0x0000d000
validating MountMgr.sys 0xf74d7000 0x0000f000
validating ftdisk.sys 0xf73fb000 0x00025000
validating dmload.sys 0xf771f000 0x00007000
validating dmio.sys 0xf73d1000 0x0002a000
validating volsnap.sys 0xf73b0000 0x00021000
validating PartMgr.sys 0xf74e7000 0x0000e000
validating atapi.sys 0xf7394000 0x0001c000
validating adpu160m.sys 0xf737b000 0x00019000
validating SCSIPORT.SYS 0xf7355000 0x00026000
validating si3112r.sys 0xf733d000 0x00018000
validating nvatabus.sys 0xf74f7000 0x00010000
validating SiWinAcc.sys 0xf7897000 0x00003000
validating disk.sys 0xf7507000 0x0000f000
validating CLASSPNP.SYS 0xf7327000 0x00016000
validating drvmcdb.sys 0xf7313000 0x00014000
validating Dfs.sys 0xf7517000 0x0000c000
validating KSecDD.sys 0xf72f2000 0x00021000
validating Ntfs.sys 0xf7255000 0x0009d000
validating NDIS.sys 0xf7214000 0x00041000
validating Gernuwa.sys 0xf789b000 0x00004000
validating nv_agp.sys 0xf7727000 0x00006000
validating Mup.sys 0xf71f2000 0x00022000
validating crcdisk.sys 0xf7527000 0x00009000
validating processr.sys 0xf6c9a000 0x0000c000
validating usbohci.sys 0xf774f000 0x00005000
validating USBPORT.SYS 0xf6b7a000 0x00022000
validating usbehci.sys 0xf7757000 0x00005000
validating nvax.sys 0xf6c5a000 0x0000a000
validating stdatw2k.sys 0xf7957000 0x00003000
validating TAPE.SYS 0xf6c4a000 0x0000a000
validating Rtlnic51.sys 0xf75e7000 0x00010000
validating nic1394.sys 0xf6b0f000 0x00012000
validating nv4_mini.sys 0xf45a6000 0x00259000
validating VIDEOPRT.SYS 0xf458d000 0x00019000
validating watchdog.sys 0xf5265000 0x00009000
validating aw_host5.sys 0xf7185000 0x00004000
validating fdc.sys 0xf5255000 0x0000b000
validating serial.sys 0xf4575000 0x00018000
validating serenum.sys 0xf5430000 0x0000a000
validating parport.sys 0xf455e000 0x00017000
validating i8042prt.sys 0xf4548000 0x00016000
validating kbdclass.sys 0xf5245000 0x0000a000
validating audstub.sys 0xf5174000 0x00008000
validating rasl2tp.sys 0xf4531000 0x00017000
validating ndistapi.sys 0xf5235000 0x00009000
validating ndiswan.sys 0xf4516000 0x0001b000
validating raspppoe.sys 0xf51f5000 0x0000e000
validating raspptp.sys 0xf4501000 0x00015000
validating TDI.SYS 0xf488f000 0x0000b000
validating ptilink.sys 0xf4e07000 0x0000b000
validating raspti.sys 0xf51e5000 0x00009000
validating rdpdr.sys 0xf44cd000 0x00034000
validating termdd.sys 0xf4df7000 0x0000f000
validating mouclass.sys 0xf5aea000 0x0000a000
validating swenum.sys 0xf7bc2000 0x00001000
validating ks.sys 0xf44ad000 0x00020000
validating update.sys 0xf447a000 0x00033000
validating NDProxy.SYS 0xf51d5000 0x0000e000
validating usbhub.sys 0xf4467000 0x00013000
validating USBD.SYS 0xf52f0000 0x00002000
validating nvapu.sys 0xf4418000 0x0004f000
validating portcls.sys 0xf43ed000 0x0002b000
validating drmk.sys 0xf43d8000 0x00015000
validating nvmcp.sys 0xf4324000 0x000b4000
validating nvarm.sys 0xf4313000 0x00011000
validating flpydisk.sys 0xf5460000 0x0000a000
validating Fs_Rec.SYS 0xf4e34000 0x00008000
validating Null.SYS 0xf518c000 0x00007000
validating Beep.SYS 0xf4e4c000 0x00007000
validating vga.sys 0xf6c8a000 0x0000c000
validating awlegacy.sys 0xf6bb4000 0x00003000
validating mnmdd.SYS 0xf7827000 0x00008000
validating RDPCDD.sys 0xf7777000 0x00008000
validating Msfs.SYS 0xf6e48000 0x0000a000
validating Npfs.SYS 0xf60eb000 0x0000c000
validating rasacd.sys 0xf63b9000 0x00008000
validating ipsec.sys 0xf41d7000 0x0001c000
validating msgpc.sys 0xf75f7000 0x0000f000
validating tcpip.sys 0xf4175000 0x00062000
validating netbt.sys 0xf4140000 0x00035000
validating netbios.sys 0xf486f000 0x0000d000
validating rdbss.sys 0xf4114000 0x0002c000
validating wanarp.sys 0xf482f000 0x0000d000
validating arp1394.sys 0xf4101000 0x00013000
validating mrxsmb.sys 0xf4094000 0x0006d000
validating mbmiodrvr.sys 0xf7b55000 0x00001000
validating Fips.SYS 0xf4081000 0x00013000
validating avg7core.sys 0xf402a000 0x00057000
validating avg7rsw.sys 0xf7bde000 0x00001000
validating avg7rsxp.sys 0xf4e44000 0x00005000
validating hidusb.sys 0xf484f000 0x00009000
validating HIDCLASS.SYS 0xf485f000 0x0000e000
validating HIDPARSE.SYS 0xf7857000 0x00006000
validating mouhid.sys 0xf7887000 0x00008000
validating Fastfat.SYS 0xf3ffd000 0x0002d000
validating dump_scsiport.sys 0xf480f000 0x00009000
validating dump_si3112r.sys 0xf3fe5000 0x00018000
validating win32k.sys 0xbf800000 0x001c6000
validating Dxapi.sys 0xf4da7000 0x0000a000
validating dxg.sys 0xbff80000 0x00016000
validating dxgthk.sys 0xf783f000 0x00007000
validating nv4_disp.dll 0xbf9c6000 0x00392000
validating afd.sys 0xf3adb000 0x0002f000
validating exifs.sys 0xf3a83000 0x00030000
validating ndisuio.sys 0xf5aaa000 0x00009000
validating mrxdav.sys 0xf394f000 0x00032000
validating srv.sys 0xf38c8000 0x0005f000
validating parvdm.sys 0xf55f9000 0x00007000
validating HTTP.sys 0xf35f0000 0x00058000
validating TDTCP.SYS 0xf3440000 0x0000a000
validating RDPWD.SYS 0xf3376000 0x00022000
validating Cdfs.SYS 0xf2846000 0x00018000
validating cdrom.sys 0xf267a000 0x00014000
validating redbook.sys 0xf2666000 0x00014000
validating sysaudio.sys 0xf2514000 0x00012000
validating splitter.sys 0xf7a19000 0x00002000
validating aec.sys 0xf24f1000 0x00023000

**************
**************--> Performing a complete check (^C to end)
**************
**************
**************--> Validating all physical addresses
**************
**************
**************--> Validating all virtual addresses
**************
**************
**************--> This dump file is good!
**************





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

validating dump_scsiport.sys 0xf480f000 0x00009000
validating dump_si3112r.sys 0xf3fe5000 0x00018000

The dump says the above - the fact the drivers have been listed as dump_<Driver>.<Extension> leads me to believe these are the drivers causing the trouble?! I'm not too hot on stop errors so I need all the help I can possibly get.

The spec of the machine is as follows:
AMD AthlonXP 3000+
Gigabyte GA-7N400-Pro2 (Rev 2.0)
1Gb of Crucial Ram
2x 120Gb SATA150 HDD
Geforce FX5200

I think it may also be the SATA - those Si3512's are shite.


Thankyou in advance, I am most gratefull.


Paul @ AIT

 

Paul, rather than use dumpchk.. can you run this through the debugger wizard from the thread over here: http://www.windowsbbs.com/showthread.php?t=33471

From the output though, there probably isnt going to be anything good from that dump. There is a very high probability you have a hardware problem. The bad news is that there will not be any clues about which component is doing it in the dump. Start with high probability stuff, replace all the ram, motherboard/cpu. you mentioned you suspect the sata stuff.. make sure your bios is flashed to latest.

BugCheckCode . . . . .0x0000007f
BugCheckParameter1 . .0x00000008
BugCheckParameter2 . .0x80042000
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

 

All part of life's learning curve my friend.

Stop errors arent something that I have really delved into up untill now.

I'll take a look @ that thread tomorrow when I'm in work, its 1:05 AM and I need some kip.

Night

 

Paul-AIT.

Suggest download and use this Microsoft document to try and track the problem. Click here for link.

Hope I set up the link right. Try and get someone to exactly copy the information that is displayed on the screen when the stop occurs. If it is a driver you might try and download an old driver and replace the current driver with it. Sometimes that works great. Also, you might bring your memory speed down a tick and see if that clears it up. Might just be a mismatch in sync signals through the motherboard re the memory clocks working the SATA's.

giles

 

Paul,
I recently resolved a BSOD error on my dual boot XP/W2K3 setup that was occurring in both OS's. The Gigabyte M/B I have has some cutely named performance enhancements such as M.I.B and C.I.A
I had the C.I.A (CPU Intelligent Accellerator) set around the middle boost setting which was causing problems. I set it back to low (cruise) and fixed the problem that I was sure was driver related. Not sure if the model Gigabyte you mention has any of these gadgets, but worth checking and setting everything back to standard defaults.

Might be worth also checking the integrity of the RAM with the following Memory diagnostic from Microsoft. Thanks Matt (Mattman)

http://oca.microsoft.com/en/windiag.asp

It looks to be fairly comprehensive and runs from a boot floppy or boot CD so rules out any OS problems if the RAM is suspect.
I refreshed my memory on creating a boot CD after saving the programme to a bootable floppy by visiting http://www.bootdisk.com/nero.htm

HTH
Paul

 

I personally don't like the memory tester for most situations. In my experience, it gives a false sense of authoritative results, despite clearly saying otherwise in the docs.

Typical scenario, box is double faulting once a week or so. User runs the tool, and it reports no errors. At this point, it becomes impossible to convince the user that the RAM is bad, because 'microsoft's tool said my hardware was fine'. This ultimately causes a delay is resolution, since they need to swap the ram out, working with the hardware vendor.

Its a great tool for what it does, which is exercise the ram to catch high failure rate errors however.

 

Paul, this won't do anygood for your current situation but I feel it is appropiate to bring it up.

People, please dont use desktop components in a critical server to save a buck. This is what happens.

If you want a safe reliable server use components on the HCL list and use server grade components.

Sorry Paul not a jab at you just felt it needed to be said.

 

As this fault is happening a couple times a day, the Microsoft memory diagnostic may still be worth running over an extended period of time when the server can be freed up. Overnight/weekend etc. The beauty of this programme is it can be set to run continuously for an extended test, which would be advisable in this situation. Not for 10 minutes, then rule out a RAM problem. I recently ran it for several hours with no problem. The system freeze was caused by an intermittent keyboard. I won't mention how many hours I spent tracking that one down. Granted, a RAM fault still cannot be ruled out 100% after a favourable test. But it's one more process in fault finding.

 

Unforunately enhancements like M.I.B and C.I.A are included at BIOS level so there may be a false sense of security in switching these little goodies on.

I've never really been able to understand the attraction of overclocking. Although I'm guilty as charged in "trying" some of these tweaks out.