Beginning dump of physical memory NT 4

Usually, no. But try booting in Safe Mode or Last Known Good first.

--Aaron

Hi, it really depends if you can isolate the problem. For example, if the crash is likely due to the installation of a new device or new app., trying last known good may work (as long as you do not log onto the machine which will update the registry). Microsoft's technet and knowledge base will provide much information about decipering blue screens (a failing device can do it as well). You can download symbol files from ms website if you care to figure out debugging on your own. If you can findthe culprit, you at least could do a parallel install to correct problems with the original installation (a benefit, of course, if you have a complicated setup on the server). Again, microsoft has a lot of information on its website under key words such as: bsod, symbol files, debugging, crash dumps, etc. Hope this helps.

Hi,

the first thing we should do when such things happens, take a brake. The solution depends on you?re knowledge to read the information you find in the blue screen and in the dump. Have a look in the knowledgebase and technet for that, there are god articles about this theme.
For me it is very simple what NT means with the 0x000000A ( 0xefefe000c, 120012331, 0x000000, 0x0000000001)
Driver faild to read at mem 0xefe... etc.
The next step depends on how cirtical is the Server, the app..and so on. In most cases it helps when you make an second installation of NT on the machine. Somtimes it happens that someone, i saw never the person who did it, installs HW or new Software on a Server. Then the thing hangs with an blue screen. If you have an older Backup, the day before that all happend, then you could restore the Service and Software hive back from the second NT installation. ( Winbootdir\system32\Config)
When you have the second NT installation on the Machine, i could repair such things in minutes !!
Another Tip is to schedule fromt time to time RDISK /s-u , to make an copy of the whole Registry and SAM. The Files then are loacted under WINBootdir\repair and are compressed. All you need is to take an CMD-Window and Expand the files system._ to system and Software._ to software and copy the hive back in your Productivity NT.

Hope it helps you.
OK! It?s late now i must leave

Frobo

BSOD's are a pain, but usually are caused by one of 2 culprits. Software (bugs or conflicts), and hardware - aka 95% of the time its bad memory. A memory dump can help u isolate the issue, but only if you see them. Alot of times end users will BSOD and just hard reset, not allowing you to see the issue. First, see if the problem is recreatable, and if it can be created across machines. If so, its likely software. If not, then it is a DLL or something similiar locally or hardware of some sort. Check to see if its at various times in one app, or if its random across apps. If its random, then start looking for hardware cues... HD sounds, mem errors in event log, etc. One useful thing if possible is to switch machines and run a burn in/stress test on the HW.... usually u get some indication from that if its hardware related.

One note on software... if its random, before you start checking HW, make sure nobody downloaded some goofy app like webshots.... i mention webshots specifically b/c I have seen it BSOD many an NT workstation for no cause. But many other user toys like that would do the same.

Qapla!
Skkz

This question was auto closed due to inactivity