Advertisement

There's no such thing as a stupid question, but they're the easiest to answer.
Login
Search

Advertisement

Windows XP Windows XP
Search Search
Search for:
Tech Support Guy > > >

"Windows has been shut down to prevent further damage"


(!)

in need's Avatar
in need in need is offline
Computer Specs
Member with 36 posts.
THREAD STARTER
 
Join Date: Apr 2006
Experience: soft- fairly tech savvy hardware - newb
17-Aug-2006, 06:18 AM #1
Unhappy "Windows has been shut down to prevent further damage"
I got this blue screen when i started my sytem headed by the following line
"Windows has been shut down to prevent further damage"

And at the bottom there was sumthin called memory dumping

I rebooted n evrything was fine but Window washer detected a junk file, actually the ".dmp" file of around 500 MB

Can sum1 shed light on this incident n tell me the cause of this n methods of prevention?
psynaptic's Avatar
psynaptic psynaptic is offline
Member with 53 posts.
 
Join Date: Aug 2006
Experience: Advanced
17-Aug-2006, 06:23 AM #2
When there is an error like this Windows creates a copy of all data in memory at the time. This way users can see what was in use at the time of the crash and hopefully track down their problem. You can check here http://support.microsoft.com/?kbid=314084 if you really want to get your hands dirty. Although, If you have a working machine and you do not experience this again, why bother?

Last edited by psynaptic; 17-Aug-2006 at 06:29 AM..
Rollin' Rog's Avatar
Computer Specs
Member with 45,855 posts.
 
Join Date: Dec 2000
Location: North of Hollywoodland
Experience: I know when to fold em'
17-Aug-2006, 10:10 AM #3
The .dmp file should not have been that large if your options are configured correctly. Run sysdm.cpl and select > Advanced > Startup and recovery. Make sure "SMALL" memory dump (64 mb) is configured there and that the path location is %systemroot%\minidump


I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last 2 or 3 minidump files to that folder. They are numbered by date.
3 > close the folder and right click on it and select "Send to (folder name).zip"
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a 3rd party driver causing the error, if one exists for it.

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.

Beginners Guides: Diagnosing Bad Memory

Windows Memory Diagnostic
Memtest86 - A Stand-alone Memory Diagnostic
As Seen On

BBC, Reader's Digest, PC Magazine, Today Show, Money Magazine
WELCOME TO TECH SUPPORT GUY!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.


(clock)
THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Search Tech Support Guy

Find the solution to your
computer problem!




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools


WELCOME
You Are Using: Server ID
Trusted Website Back to the Top ↑

Content Relevant URLs by vBSEO 3.3.2