Win2kpro rebooting problems

[Hellsbellboy]

I set up my Duron 650MZH a dual boot WinME and Win2kpro.. Win2kpro starts up fine. but at different times when in Win2k it will just suddenly reboot.. out of the blue so to speak.. doesn't happen on any one program.. sometimes when I'm just surfing the net.. sometimes when I'm just running different programs. Anyone else have this problem? I have a
650MHZ Duron
MK33 Aopen mobo
20GB Seagate Ultra 66 HD
64MB Evil Kryo Video Card
256MB PC133 RAM
SB LIVE MP3+

All the lastest drivers, service pack 2, Explorer 5.5, newest 4 in 1 drivers, new video card drivers, (even does it on a 16MB TNT2 vanta)

Thanks for anyhelp.

 

[Guest]

You can check the System log in the Event Viewer and see if you can find any error messages. Description of stop messages in Windows 2000 here:

<A HREF="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/reskit/serverop/part4/sopch16.asp" target="_new">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/reskit/serverop/part4/sopch16.asp</A>

Check especially the chapter on Generic Troubleshooting Procedures.

<A HREF="mailto:jostber@frisurf.no">jostber@frisurf.no</A>

 

[Hellsbellboy]

this is what I find in the System log:
the computer was rebooted from a bugcheck:
bugcheck was 0x0000000a (0x00000000, 0x00000002, 0x00000001, 0x80069582)
MS Windows 2000 (v15.2195)
what does that mean? couldn't find it on that webpage.

 

[Guest]

This error is most likely caused by some hardware in your computer that Windows 2000 is not entirely happy with, or it could be a power management issue(APM/ACPI).

This is what those references mean:
0x0000000A = the STOP error code itself
0x00000002 = identifies the IRQL required to access the memory
0x00000001 = identifies the access type as 'write' (read=0)
0x80069582= the instruction address attempting to access the memory referenced.

Windows 2000 records the errors to a file in C:\winnt\memory.dmp. More info here:

<A HREF="http://support.microsoft.com/support/kb/articles/Q192/4/63.ASP?LN=EN-US&SD=gn&FR=0&qry=Bugcheck&rnk=5&src=DHCS_MSPSS_gn_SRCH&SPR=WIN2000" target="_new">http://support.microsoft.com/support/kb/articles/Q192/4/63.ASP?LN=EN-US&SD=gn&FR=0&qry=Bugcheck&rnk=5&src=DHCS_MSPSS_gn_SRCH&SPR=WIN2000</A>

You can try to run pstat.exe to determine possible driver problems. You can also run dmpchk.exe to get a more detailed dump log. Instructions here:

<A HREF="http://www.jsiinc.com/SUBB/tip0700/rh0726.htm" target="_new">http://www.jsiinc.com/SUBB/tip0700/rh0726.htm</A>

The error messages could be related to your APM BIOS. You can check if your machine or BIOS is on the Windows 2000 "Disable APM" list. Then the errors is often caused by hal.dll. Try to run Apmstat.exe to check it:

<A HREF="http://support.microsoft.com/support/kb/articles/Q242/4/95.ASP" target="_new">http://support.microsoft.com/support/kb/articles/Q242/4/95.ASP</A>

ACPI is strongly recommended for Windows 2000. Info:

<A HREF="http://www.microsoft.com/hwdev/onnow/w2apm.htm" target="_new">http://www.microsoft.com/hwdev/onnow/w2apm.htm</A>

and

<A HREF="http://www.microsoft.com/hwdev/onnow/apm.htm" target="_new">http://www.microsoft.com/hwdev/onnow/apm.htm</A>


<A HREF="mailto:jostber@frisurf.no">jostber@frisurf.no</A>

 

[Ganache]

Try putting the amd patch for win2000


www.amd.com

support, its largepageminimum something..