good msft troubleshooting newsgroups/sites?

xyyz

Diamond Member
Sep 3, 2000
4,331
0
0

i'm having the same BSOD problem with this system.

i've reinstalled win2k pro about 5 times (and this is a LEGIT COPY) and i've virtually swapped out all the hardware this system had in it.

the problem doesn't seem to go away.... F- the ntoskrnl.exe

anyways... does anyone know of a good MSFT site where people will actually email you back and help you solve your problem?

i've already posted some messages on the MSFT newsgroups but so far nothing.

 

xyyz

Diamond Member
Sep 3, 2000
4,331
0
0

hmmm.... okay... you are talking about the actualy STOP message on the blue screen?

i don't have that.... but I do have output from the memory.dmp file when I used dumpchk to read it.

I can post that... if you can tell me how to get more info from the dump file... i'll post that too.

I really appreciate your help here btw.


Event Viewer

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffffffc, 0x000000ff, 0x00000001, 0x8046605e). Microsoft Windows 2000 [v15.2195]. A dump was saved in: G:\WINNT\MEMORY.DMP.


MEMORY.DMP

----- 32 bit Kernel Summary Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000893
DirectoryTableBase 1d861000
PfnDataBase 85ead000
PsLoadedModuleList 804836e0
PsActiveProcessHead 80484e28
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 0000000a
BugCheckParameter1 fffffffc
BugCheckParameter2 000000ff
BugCheckParameter3 00000001
BugCheckParameter4 8046605e
PaeEnabled 00000000
KdDebuggerDataBlock 8046f3f0

SUMMARY_DUMP32:
DumpOptions 504d4453
HeaderSize 0000a000
BitmapSize 0003fff0
Pages 00008a4a
Bitmap.SizeOfBitMap 0003fff0

KiProcessorBlock at 80482780
2 KiProcessorBlock entries:
ffdff120 85e7a120


Windows 2000 Kernel Version 2195 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x804836e0
Debug session time: Thu Feb 07 22:30:50 2002
System Uptime: 0 days 7:41:52
start end module name
80400000 8059b5c0 nt Checksum: 0019C6F1 Timestamp: Fri Apr 13 15:06:33 2001 (3AD77869)

Unloaded modules:
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 22:28:14 2002 (3C636FFE)
b9cfd000 b9d12000 VGA.dll Timestamp: Thu Feb 07 22:00:00 2002 (3C636960)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 21:44:15 2002 (3C6365AF)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 20:37:06 2002 (3C6355F2)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 20:21:57 2002 (3C635265)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 19:32:01 2002 (3C6346B1)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 18:24:11 2002 (3C6336CB)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 17:55:15 2002 (3C633003)
b9d32000 b9d56000 kmixer.sys Timestamp: Thu Feb 07 17:42:59 2002 (3C632D23)
b9d9d000 b9dc1000 kmixer.sys Timestamp: Thu Feb 07 17:23:36 2002 (3C632898)
b9d9d000 b9dc1000 kmixer.sys Timestamp: Thu Feb 07 16:37:44 2002 (3C631DD8)
b9e61000 b9e85000 kmixer.sys Timestamp: Thu Feb 07 15:59:13 2002 (3C6314D1)
b9fed000 ba011000 kmixer.sys Timestamp: Thu Feb 07 15:56:56 2002 (3C631448)
ba570000 ba594000 kmixer.sys Timestamp: Thu Feb 07 14:51:45 2002 (3C630501)
f1d60000 f1d6d000 DMusic.sys Timestamp: Thu Feb 07 14:51:42 2002 (3C6304FE)
bdbca000 bdbd8000 swmidi.sys Timestamp: Thu Feb 07 14:51:39 2002 (3C6304FB)
f2134000 f2136000 mgabg.sys Timestamp: Thu Feb 07 14:51:05 2002 (3C6304D9)
f2132000 f2134000 mgabg.sys Timestamp: Thu Feb 07 14:51:04 2002 (3C6304D8)
f2112000 f2114000 mgabg.sys Timestamp: Thu Feb 07 14:51:04 2002 (3C6304D8)
bda22000 bda37000 VGA.dll Timestamp: Thu Feb 07 14:50:36 2002 (3C6304BC)
bd7e4000 bda37000 G400DHD.dll Timestamp: Thu Feb 07 14:50:36 2002 (3C6304BC)
f1d60000 f1d69000 redbook.sys Timestamp: Thu Feb 07 14:50:21 2002 (3C6304AD)
f1eb0000 f1eb5000 Cdaudio.SYS Timestamp: Thu Feb 07 14:50:20 2002 (3C6304AC)
f20dc000 f20df000 Sfloppy.SYS Timestamp: Thu Feb 07 14:50:20 2002 (3C6304AC)

The debuggee is ready to run
Finished dump check
 

Slikkster

Diamond Member
Apr 29, 2000
3,141
0
0
The actual stop error (blue screen) contents would be more useful in determining what's going on here.

What I can see so far is basic stuff...you have a multiprocessor pc (2 cpu's), and a bunch of unloaded modules; most of which having to do with your sound card and directx. That doesn't mean it's the issue, though. So, please post the contents of the actual blue screen error.

by the way, I found one of your posts in the newsgroups (Sameer), and I can see your system specs there.

In the meantime, check this page from Microsoft:

KB article on troubleshooting this issue

I'd be inclined to try the first method; copying the I386 folder to a hard drive and installing from there, for starters.

When does this error happen? After installation? After SP2 installed? Again, post the actual Stop error message.
 

xyyz

Diamond Member
Sep 3, 2000
4,331
0
0
Thanks for the help with this one.



<< The actual stop error (blue screen) contents would be more useful in determining what's going on here.

What I can see so far is basic stuff...you have a multiprocessor pc (2 cpu's), and a bunch of unloaded modules; most of which having to do with your sound card and directx. That doesn't mean it's the issue, though. So, please post the contents of the actual blue screen error.
>>



How can I get a that blue screen information? I was looking at the memory.dmp file and I didn't see it there. Is there another log that Windows keeps... or should I just wait until it happens again and then hand write the message?



<< by the way, I found one of your posts in the newsgroups (Sameer), and I can see your system specs there. >>



Yeps... that's me.



<< I'd be inclined to try the first method; copying the I386 folder to a hard drive and installing from there, for starters.

When does this error happen? After installation? After SP2 installed? Again, post the actual Stop error message.
>>



So you want me to do another full reinstall?

This problem has been ongoing... but there's no pattern to the problem... well one that's been discernable by me at least...

This problem was happening before SP2, after SP2... when photoshop was running... when word was running... hell when wordpad was running.