can someone help me out with this Win2k BSOD?

[xyyz]

This happens to me about a few times week... and then it'll be fine for a bit then it will start up again.

I get a BSOD that names ntoskrnl.exe (I think that's the name...) as the culprit.

I've tried swapping the cards... I tried removing the cards... but I still get the crap.

I have the following:

2xP3-1gig
Iwill DVD-266R
4x256mb Crucial PC2100 DDR SDRAM
Matrox G450
Onboard Sound
Intel 8255x NIC (5th PCI slot)
Adaptec 2940UW (2nd PCI slot from the top - the AGP slot being the top)
Maxtor 30gb ATA100 HD
Yamaha 8424s CDRW
Lite-on 48x CDROM
External 100MB SCSI Zip
350W PS

This is the output from the event viewer:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 12/24/2001
Time: 5:19:26 PM
User: N/A
Computer: FROGGIE2
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000047, 0x8042d638, 0x8046986c, 0x01000808). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini122401-01.dmp.



This is the output from the minidump file:


C:\Utilities\Debugging Tools>dumpchk c:\winnt\minidump\Mini122401-01.dmp
Loading dump file c:\winnt\minidump\Mini122401-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000893
DirectoryTableBase 0d5ae000
PfnDataBase 85ead000
PsLoadedModuleList 804836e0
PsActiveProcessHead 80484e28
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 0000001e
BugCheckParameter1 c0000047
BugCheckParameter2 8042d638
BugCheckParameter3 8046986c
BugCheckParameter4 01000808
PaeEnabled 00000000
KdDebuggerDataBlock 8046f3f0
MiniDumpFields 45474150

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001050
UnloadedDriversOffset 00001088
PrcbOffset 00001860
ProcessOffset 00002250
ThreadOffset 000024d8
CallStackOffset 00002720
SizeOfCallStack 000013f8
DriverListOffset 00003b18
DriverCount 0000006d
StringPoolOffset 00005b78
StringPoolSize 00001eb8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba5e1c08


Windows 2000 Kernel Version 2195 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x804836e0
Debug session time: Mon Dec 24 17:17:10 2001
System Uptime: not available
start end module name
80400000 8059b5c0 nt Checksum: 0019C6F1 Timestamp: Fri Apr 13 15:06:33 2001 (3AD77869)

Unloaded modules:
b9a67000 b9a8b000 kmixer.sys Timestamp: unavailable (00000000)
b9a67000 b9a8b000 kmixer.sys Timestamp: unavailable (00000000)
ba3af000 ba3d3000 kmixer.sys Timestamp: unavailable (00000000)
f1d60000 f1d6d000 DMusic.sys Timestamp: unavailable (00000000)
f1d50000 f1d5e000 swmidi.sys Timestamp: unavailable (00000000)
f2154000 f2156000 mgabg.sys Timestamp: unavailable (00000000)
f2152000 f2154000 mgabg.sys Timestamp: unavailable (00000000)
f2144000 f2146000 mgabg.sys Timestamp: unavailable (00000000)
ba5db000 ba5df000 hidusb.sys Timestamp: unavailable (00000000)
bd874000 bd889000 VGA.dll Timestamp: unavailable (00000000)
bd637000 bd889000 G400DHD.dll Timestamp: unavailable (00000000)
f1d50000 f1d59000 redbook.sys Timestamp: unavailable (00000000)
f1fd8000 f1fdd000 Cdaudio.SYS Timestamp: unavailable (00000000)
f20d8000 f20db000 Sfloppy.SYS Timestamp: unavailable (00000000)

The debuggee is ready to run
Finished dump check

 

[xyyz]

bump

 

[xyyz]

bump

 

[Entity]

When did the BSOD start popping up?

Rob

 

[Flatline]

If NTOSKRNL.exe is the file that's showing up (which is the Win2K kernel, incidentally), then you will probably have to boot from the Win2K installation CD, select Repair, go to the Console, and attempt to replace the file with a fresh copy from the CD.

 

[xyyz]

so it's a file corruption?

the thing is that I've had the same problem in my previous install... it's like I can't escape it....

 

[xyyz]

<< When did the BSOD start popping up?

Rob >>



ummm.. ever since i installed Win2k on this setup.... after the first time I reformatted again and reinstalled hoping that the new install would solve the problem... but nothing...

do I need a beefier PS?

 

[Elledan]

Try running a barebones system for a while first, and see whether the problem remains. Reinstall after you've 'stripped' the system if possible. Then start adding components until you notice the error again.

Try replacing system critical components which components of which you know that they work (RAM, PSU etc.).

 

[Flatline]

All good suggestions...but, with that error message, his kernel is corrupt. He's going to have to fix that first or completely reinstall.

 

[WarpSpeed]

It the kernel is corrupt, you would think that you'd get a BSOD every boot. That error message is very common with a lot of problems. I agree with the plan to dumb down the machine and add one peripheral device at a time. Because the problem comes up infrequently, it might take a long time to figure it out. Quality of power source may also be a problem.

 

[xyyz]

man this is gonna be ugly... :/

this machine is used heavily... there's no other way? something card is causing this problem for sure?

 

[xyyz]

guess what... I did another fresh reinstall... and the problem is still there...

 

[KGB]

Have you checked this MSKB article?

 

[xyyz]

yes... but that only tells you what to do after you get a BSOD... whice i've done.

i'm totally sunk here... i feel really bad cause I got my mom to pay for this dual 1gig rig... and I told her it would be a great system for her graphics and video editing... and it barely works.

i'm almost sure that this lame-ass MB is the problem.

 

[killmeplease]

Are you running RAID? If so, slow down your drive mode and or swap out the IDE cables.

 

[xyyz]

<< Are you running RAID? If so, slow down your drive mode and or swap out the IDE cables. >>



ummm no... this is being run on one of the standard ata100 ports.

 

[RolandG]

Have you tried running the Maxtor diagnostic utilities on your hard drive? Recently I was facing a similar problem with a machine that I built for someone. In my case I the machine was not getting BSOD's but was bus locking very intermittently under Win2k Pro (we?re talking every few days of uptime it would bus lock). I tried just about everything to troubleshoot the problem when the machine finally failed to reboot & the IBM Deskstar 60GXP HD started making an ominous clicking sound. I ran IBM?s HD utilities & confirmed that the drive was dead. I installed a new HD & re-installed everything & the machine is now rock solid stable. The whole time I was troubleshooting the machine the damn IBM HD was causing the bus locking. Your problems may well be unrelated to the HD but it?s worth checking out the HD with the manufacturer?s utilities before you go to all the trouble of removing each component one piece at a time.

Good luck!

 

[killmeplease]

<<

<< Are you running RAID? If so, slow down your drive mode and or swap out the IDE cables. >>



ummm no... this is being run on one of the standard ata100 ports. >>



ummm no....Sorry. I will know better than to try to help you next time, ummm smart-ass.

 

[xyyz]

<<

<<

<< Are you running RAID? If so, slow down your drive mode and or swap out the IDE cables. >>



ummm no... this is being run on one of the standard ata100 ports. >>



ummm no....Sorry. I will know better than to try to help you next time, ummm smart-ass. >>



you know... it's true... you can't tell a person's tone here. i didn't mean this in a condescneding or offensive manner... it was a straightforward answer to your question. i wasn't at all being sarcastic.

seriously... I really appreciate the help you're offering me with this problem.

great... you don't even have PM enabled... so I can't replicate this in a personal message.

 

[sasa]

I also had similar problems, also BSOD, also in ntoskrnl.

My suggestions:

1. Try memtest86
2. Next time you reinstall windows don't install 3rd party drivers, try to use only drivers which come with Windows

 

[xyyz]

hmmm... memtest...

where do I get that from?

 

[killmeplease]

<<

<<

<<

<< Are you running RAID? If so, slow down your drive mode and or swap out the IDE cables. >>



ummm no... this is being run on one of the standard ata100 ports. >>



ummm no....Sorry. I will know better than to try to help you next time, ummm smart-ass. >>



you know... it's true... you can't tell a person's tone here. i didn't mean this in a condescneding or offensive manner... it was a straightforward answer to your question. i wasn't at all being sarcastic.

seriously... I really appreciate the help you're offering me with this problem.

great... you don't even have PM enabled... so I can't replicate this in a personal message. >>



If I took it wrong, I'm sorry for snapping. That's just how it read.