Install with W2k3 SP1 seems to help. One of the remote offices in my company was trying to install Windows Server onto a Dell Optiplex but kept getting a BSOD at around 36 minutes into the install. As I googled "server bsod" I came upon this thread. I read through your fixes and the last one, "Turn on only one core for multi-core processors in BIOS. Server OS's are far more barebones than Desktop OS's and tend to be far more choosy on what Hardware that they are installed on.
If you are unable to find a driver for any single device that is installed under XP then that Particular Device Will Not work under The really important things here are the Chip Set Drivers as if these are not present the OS Can Not install and the process will fall over. If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.
Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended. Please note: Do not post advertisements, offensive material, profanity, or personal attacks. Please remember to be considerate of other members. All submitted content is subject to our Terms Of Use. I didn't need those, so removed them, but the problem persists.
I suspected memory. There are 2 x MB simms in 2 slots. I removed each one from either slot, and booted with only half the memory. I also swapped the slots for both sims, and also tried one at a time. In all cases the BSOD continued to occur mostly at boot. I did however run memtest , and it reported bad memory -- could it be the memory controller module on the mainboard? No new drivers or applications have been added to the system prior to this problem starting. The machine has been running for 5 years without much incident.
I have done a complete system cleanup, scandisk full , reg-check, checked CMOS settings, and removed a lot of old apps and junk in the hope of tuning it all up.
I've also removed CD-ROM drive not used much , reinserted the hard-drive in it's IDE slot, unplugged and plugged everything back in several times and physically cleaned it's innards.
Checked fans are all working. Try this Microsoft Article on troubleshooting stop errors. Boot it in Safe Mode and see if you can get it to crash. Also, how did you uninstall the Bluetooth driver?
It's possible that an application or driver uninstaller actually left the driver running. SYS file s were included in the Bluetooth driver. You may also be able to extract but not install the original driver to see which. SYS files it includes. Once you know the name of the driver file s , try to see if it still exists on the server. You may be able to disable the driver from Device Manager, but I have had to go as far as renaming the. SYS driver file in Safe Mode to prevent a driver from loading.
The next thing I would check is the CPU. An overheating CPU can cause all kinds of strange errors. If you have another box with the same CPU, swap them out. Also, you might want to replace the CPU fan and the heat sink compound. I know you said the fans were all spinning, but the heat sink might not be making good contact with the CPU.
On topic with the CPU, i've seen a dust layer build up between the top of the fins on the heatsink and the fan, taking the fan off and removing the dust has been the fix of many servers that are spontaneously rebooting and crashing.
Sure enough without the network card plugged in it ran fine. Furthermore after I upgraded the Network Card drivers the the latest version the problem has gone away.
So it was software related all along. I suspect the old drivers had been corrupted in a minor way or the network environment had changed in someway causing a bug in the old drivers to manifest. Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? We have installed Server on a server, it worked perfectly for 2 weeks or so, then it started BSODing with the following error: A problem has been detected and Windows has been shut down to prevent damage to your computer. Technical Information Stop: 0xA 0x, 0x, 0xx 0xEA Beginning dump of physical memory.
Physical memory dump complete. When we reboot the server, an event is immediately logged with Event ID Many thanks! Link to comment Share on other sites More sharing options Posted July 20, These are very tricky to diagnose so best practice is to do the following imop: update all hardware drivers to latest versions remove or disable AV software disable any other low level software drive imaging, hw dongles etc Is the server an out of the box one or is it home grown?
Tech Freak Posted July 23, Posted July 23, Like hell they are! This is what they mentioned: "Compare the memory address in the fourth parameter of the stop message with the base addresses of the drivers in the driver table on the STOP screen to find the driver that is the problem". This topic is now closed to further replies.
Go to topic listing. Recently Browsing 0 members No registered users viewing this page.
0コメント