SystemDump Again

Aecdesign

Member
Apr 3, 2001
46
0
0
OK,all

I really need your help. I've done all the sugestions that were givento me here, on the situation of the 0x0000001e bugcheck dump, to the point of not only did I reformat the HD, but I bought a new one. I have very minimal software on the system and it is still doing it:(

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/24/2001
Time: 12:01:37 AM
User: N/A
Computer: AEC-DESIGN
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000047, 0x8042edb1, 0xb9281944, 0xbfd939ee). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini072401-01.dmp.

I can't pay $245.00 to MICROSOFT to get help, so I'm really relying on you good folks to help me out.
I thought that I might have a bad ram module, so I replaced themwith other that were good. This didn't work either. Please, please help. What are the codes in the ( )? HELP PLEASE!!!!

I'm on NetMeeting at meetnow.autodesk.com just in case someone wanted to talk instead of writting.

********************
* System Summary *
********************

Processor: GenuineIntel Family 6 Model 7 598 MHz Stepping 3
Math Support: Present
BIOS: PhoenixBIOS 4.0 Release 6.0, 08/17/00
Bus Type: PCI, ISA, USB
Ports: 1 Parallel, 3 Serial
Memory: 256 MB (34% Utilized)
Floppy Disks: 1.44 MB
Hard Disks: 37.27 GB, 37.27 GB
Multimedia: Sound, CD-ROM
Video: 1280 x 1024 in 32-Bit Color, Diamond Stealth III S540 Ver. 5.12

< Operating System >
Windows: 5.0 (Build 2195)
Net Clients:
Microsoft Windows Network

 

Serpent77

Member
Jul 17, 2001
91
0
0
The &quot;codes&quot; in brackets are memory addresses. Win2K uses a 32 bit flat memory model, and those address are the locations in RAM, or swap drive space that the problem is believed to be coming from by the OS. I'd start by building up a clean system. Start with an HD, Mobo, Processor, RAM, Video, Monitor, Mouse, and KB, get rid of all extra stuff like USB devices. Start adding them in one at a time afterwards until the machine blows up. You've likely got a bad or incorrect driver, or incompatible hardware. These are only guesses since I have no detailed info of what all your machine really has onboard. I'd also need to know more about how/when its crashing on you.

--Serp
 

Skooter

Member
Jan 31, 2000
96
0
61
Judging from the components you've replaced thus far that could be causing the problem, as well as the things you've done, I'd have to say it looks like the problem resides in your motherboard.