Tag Info

Hot answers tagged

18

When the computer bluescreens it'll most likely create a dump of the memory. The content from memory is written to the Pagefile as the system is going down. It uses the Pagefile as placeholder for the data since it is too dangerous to try to create a new file on disk. When the machine starts up again it'll detect the dump, and move the data into a separate ...


7

Mark Russinovich (of SysInternals fame) has an excellent blog entry where he describes how one can use the debugging tools to track down the module name and even the stack frame (i.e. function call) during which the blue screen occurred. It's illustrated, well written, and has helped me get my feet under me when I started learning how to debug Blue Screen ...


6

The Debugging Tools for Windows has STOP codes in its help file. Simply search for bug check and the error code, e.g. "bug check 0xf4". (Thanks Windows Internals) Doesn't seem like the best option if you don't have it already installed.


6

The configuration is held in the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\AutoReboot With a setting of either 1 (AutoReboot on) or 0 (AutoReboot off) The following command should enable it: reg add HKLM\System\CurrentControlSet\Control\CrashControl\ /v AutoReboot /t REG_DWORD /d 1


6

The DRAC is your friend usually the logs are obvious. If you still have warranty open a Dell Chat, ask for the DSET link, run it, and tell them to ship you parts. The diagnostic process will be: Complain to Dell, run a DSET (Diag tool), have them ship you parts Replace parts If !satisfied go to step 1, else continue Be happy. Don't waste your effort ...


5

The error code in the top left. By googling that, you can often narrow it down to whether it's a hardware or software issue. Proceed from there (the Google results).


4

I would run memtest to test your RAM fully for hardware issues.


4

Don't just copy the machine. Use the VMware Converter Standalone to convert it. Besides that, I had a similar problem when using the Converter - after converting the virtual disk adapter changed from IDE to SCSI in a WinXP machine, so I had to do a repair installation with injected VMware SCSI drivers. You should also have a look at the VMware ...


4

Remove all but one of the RAM modules then run Memtest. If it tests good then swap it for another RAM module and memtest again. Do this until you find the RAM module that's causing trouble. Then RMA the memory or just leave it out. If the notebook is new it might come with a warranty and you may consider calling the OEM to have them replace the bad memory ...


4

Net.exe is the program used to map drives, mess with users, and do other network related tasks. It's usually run in logon scripts to map drives. Check your login scripts on the server that are run through startup, logon registry key, user logon script in AD, and local and domain group policies. You'll likely find something in there that's running amock at ...


3

Hmmm, since you did not mention it ... do actually have 8GB free space on c: ?


3

Do they have the same onboard video card? It looks like the Optiplex 760 can come with 7 different possible video cards. If they are different and using the wrong driver it will cause the 0xDA BSOD, which relates to virtual memory being too heavily used (unlikely) or a bad system driver (more likely).


3

Well, it turned out to be the video drivers. The old system had an ATI 1600 in it, and the new system does not. Once I uninstalled all of the ATI tools, things went back to normal.


3

I think the first thing to do is to look up the reason for the bluescreens - I swear by whocrashed and bluescreen view - these either interpret or look up the precise errors easily. I'd look at each system seperately - It might be a co-incidence that these systems crashed together. If its a one off incident it may not be worth following up on - else, well ...


3

You call the company that sold you the box and ask for warranty. They should replace the RAM.


3

I had a similar issue to this (though; not a PFN under hyper-v) that was caused by a southgate that would send currupt bits when the chipset overheated. Are you running this on a quality server, or a cheap whitebox. Try running a memory test while doing heavy IO to try and heat up the board.


3

You are correct in looking at the RAID drivers, this is usually the cause of the bluescreen at this point. Are you sure the drivers you are getting from the Dell website are correct, and that when using the F6 option you are selecting the correct one, often at this point you are presented with a number of drivers to choose from.


2

There is the chance that if you enter BIOS and move AHCI to ATA (I usually poke around until i find it, as all BIOS are different) that it will allow you to install the OS. After this, you can look for drivers from your motherboard's chipset manufacturer that will allow you to change it back after you have loaded your OS. Hope this helps, Good Luck.


2

This is probably going to be an unpopular answer, but here goes... What you're doing may seem trivial, but it's not. Disk imaging software makes it easy to do things that the operating system can't cope with easily. Micorsoft doesn't officially "support" moving installs of Windows between different makes or models of computers or motherboards (see ...


2

If they have the Bluescreen still open: The Actual Message near the top (i.e. IRQL_DRIVER_LESS_OR_EQUAL) and the Error Code at the Bottom (0x.......) with the module that crashed (i.e. nvdisp4.dll). There are some common approaches here, but in my example, it's a Bluescreen caused by the nVidia Graphics Driver. If you analyze a few bluescreens, there are ...


2

Despite being in German, this list is quite a nice cross-reference of BSOD codes to KB articles. Just remove the trailing /de from the KB URLs to change the language to English. You can also search support.microsoft.com for 'stop' and the code. The values in brackets are parameters and their meaning differs depending on the STOP code. Frequently they don't ...


2

I'm not sure what the source of your errors are but here's a place to start looking: 10036 Error: http://eventid.net/display.asp?eventid=10036&source= 7888 Error: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/63eaca58-7e89-4083-8411-5e92ec6eec30 NOTE*-If this first link is right, check service enabled in your MOSS setup and ...


2

See Kazna3's answer at http://www.d-a-l.com/archive/index.php/t-49205.html He/she writes: But first, the BSOD is pretty old. The 0x9C BUGCHECK is hardware related, well known. The rest of it concerns the processor, it's a processor fault or just the processor driver. :( Have a look here for the explanation: 0x9C: MACHINE_CHECK_EXCEPTION ...


2

You want to turn your X4 into a X3... There is an Advanced Clock Calibration/Control option in the BIOS. Depending on your motherboard/BIOS, it may allow you to select a "per core" control. Which may let you stop the core you want out.


2

This can be caused by faulty memory sticks, motherboard faults, and driver issues. Let us know the make & model of your hardware and we may be able to offer specific tools and methods for you to troubleshoot. First off I would verify your drivers are all in order. If your server is an HP, and you build it from the smartstart CD, the drivers should be ...


2

when you upgrade the raid controller firmware, you must make certain you have updated the storage driver first. Otherwise there's a chance that the older driver will not recognise the controller after the update, which always leads to a BSOD. You can try to boot from a liveCD (RHEL or CentOS preferrably, since Dell have linux update packages for RHEL, which ...


2

This MS support article may be of assistance.


2

You ask what you do? You replace the RAM. Still got the error? Make sure you're within specs (don't use cheap-ass RAM. Sometimes, manufacturers impose certain requirements on their OEM parts. Make sure the RAM is made for that particular machine. A prominent example is Apple, putting cheap ram in those, even when matching the OEM clocks/timings guarantees a ...


2

We had a similar issue on an older version of citrix (PS4) that was down to HP Print drivers. I had to clear the whole lot off before re-installing the appropriate ones and it seemed to clear the blue scdreen issue. Also Curious about "automated deletion of non-approved drivers every night". If you clear non-approved ones down each night, why do you allow ...


2

This system should have been virtualized long ago. This could have been due to hardware failure or due to some virus activity. hopefully you have backups, which you should try to restore first. If that doesn't work, the only thing it seen you could do is reinstall NT 4 on one of the systems, restore the image to a second drive in the system, re-install ...



Only top voted, non community-wiki answers of a minimum length are eligible