Memory Dump Blue Screen Problem!!

[MelloJ 0]

I have Win 2000 Ver 5. Build 2195

Every so often i get a blue screen that says there was a memory Dump.

 

In the events viewer the following message is displayed:

 

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a

(0xc104027e, 0x00000002, 0x00000000, 0x8049f771). Microsoft Windows 2000

[v15.2195]. A dump was saved in: C:\WINDOWS\Minidump\Mini020800-01.dmp.

 

Hardware as follows:

P3 600

128 sdRam

Abit BE6

QPS 8.4.32 cdr

Matshu****a 32X cd-rom

Riva tntn2 ultra (latest driver)

Open 56k modem

Awe 64 SB

Fujitsu 8.4 gig

and WD 3.2 Gig

 

BTW this never happened to me in windows 98

thanks

After this i have to reboot...

any ideas?

thanks

 

 

 

[This message has been edited by MelloJ (edited 10 February 2000).]

[Super Fly 0]

That is the infamous blue screen of death you are looking at and you must have memory dumping enabled. What win2k does (and I believe this setting is in my comp/properties/advanced/startup-recovery/)is dump the contents of memory to file for analysis in the event of a nasty system failure. You might want to turn it off unless you really want to find out what is in all 128mb of your ram as it is just taking up space on the hard-drive every time your computer blue screens.

 

Good luck,

SuperFly

[MelloJ 0]

thanks,

 

but thats not actually what causes it is it ?

 

Is there anything wrong with a setting that could be triggering that blue screen?

 

or is it just something that has to be addressed in a upgrade (ahem service release)?

[DosFreak 2]

I noticed you said Riva Tnt2 (Latest Driver). Which driver would that be? Install the 3.66 drivers for W2K....some people like those better or try out the latest 3.76 drivers.

 

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

C:\Dos

C:\Dos\Run

\Run\Dos\Run

[peterro 0]

Sounds like a driverproblem to me. Get the latest drivers, or try to use Microsofts own drivers if possible. I know of a server that got bluescreen pretty often. I was the printerdrivers. Changed to Microsofts own, and not a bluescreen after that!

 

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