> BSOD on Windows Server 2008

[jorwex]

I thought I'd give Server 2008 a try since it was on Dreamspark for free, and I've read all these great things about it--how people have been using it as a workstation OS.

I've been getting D1 and A stop errors pretty consistently. At first I thought it had to do with when I was writing to any kind of disk, but it wouldn't die until some time into each writing. I've saved the kernel dump files from c:\windows\memory.dmp and have 4 or so saved up, so I think I'll stop that now cuz they're pretty large

Here's some photos:

Stop A Pic
Stop D1 Pic
seems that when there's a D1 error, it mentions NDIS.SYS, but when i get a A error, it won't mention any file.

Here's some screenshots of the event viewer system logs for the first 3 times it's crashed (I believe I'm up to 6 since I installed the OS yesterday).

Event Viewer after 1st BSOD
Event Viewer after 2nd BSOD
Event Viewer after 3rd BSOD

If you look at the activity before the crash (I highlighted the line that says it recovered from an unexpected shutdown) on the 2nd and 3rd one, it says there's a Warning for storFit and the description reads "The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives." In fact, the entries between that warning and the Eventlog Error line indicating the unexpected shutdown are pretty consistent on all of the crashes since that 1st one. So it sounds network related mayhaps? I guess it does talk about NDIS.SYS for the D1 stops...

I'm downloading "Debugging Tools for x86" from Microsoft right now, as well as the Server 2008 retails symbols files...hopefully they'll fiinish uninterrupted this time (the symbols file is 240 MB and it's died once already since the start). I realized that I hadn't gotten my chipset driver installed so that might account for the hard drive writing thing (AHCI/sata related?), but I installed that a half hour ago and it's died twice since.

When I'm idle it seems to be fine (I left it on overnight), which makes me think its a disk thing. I really have never known how to diagnose these stop errors. Is there a place other than the event viewer than might give a more detailed description? It seems to do the D1 and A errors randomly, so I'm not sure if they're related and caused by the same thing, or if they're for two different errors that are unrelated (man I hope not...).

I started disabling devices in the BIOS to see if they might be the cause, and discovered that if I disable the two built in gigabit NICs, I stop getting the D1 and A errors, and then only get (less frequent) 8E errors. Did a memory check, and all is good.

I'd really appreciate any info. Thanks!

 

[mcmilljb]

I would post this in the Operating Systems Forum. No one in here is going to use Server 2008 as a workstation.

 

[jorwex]

The moderator moved it to this forum actually.

http://www.google.com/search?q...&rls=org.mozilla:en-USfficial&client=firefox-a

A lot of people are using it as a workstation OS. There are a lot of guides explaining how to change the services to that end.

 

[mcmilljb]

Originally posted by: jorwex
The moderator moved it to this forum actually.

http://www.google.com/search?q...&rls=org.mozilla:en-USfficial&client=firefox-a

A lot of people are using it as a workstation OS. There are a lot of guides explaining how to change the services to that end.

Well I wouldn't say a lot, and "power users" should turn off what they don't want on Vista Ultimate or Basic.

Your NDIS.SYS problem is definitely nic related. Link - you can look there for some related information about the problem. Might have to find some driver's or use a more compatible nic.

Can you get a shot of the 8E error?

 

[RebateMonger]

I doubt it's an OS drive or drive controller problem because you are getting memory dumps to disk. When a drive controller bombs, you don't get a memory dump because the drive quits working.

Did you say what your hardware was? I see a hardware list at the bottom of your posts, but those mention Ubuntu and Vista. Server 2008, 32-bit or 64-bit?

As you are finding, it looks like part of the problem is NIC/driver related. I'd first leave those NICs disabled and concentrate on the 8E error. You can always get other NICs.

Don't know why this Topic got moved to the Networking Forum.....

 

[mcmilljb]

Information About Stop 0xA

Info about Stop Code 0xD1

List of XP Stop Errors. It might be able to help you determine what is causing the problem. I'm trying to find a Vista/2008 list.

These should help you glean some information about the problem. They're not Server 2008, but you see what can cause these types of problems. If you had a retail version, you could probably just call them up and get some better answers.

 

[JackMDS]

Did you install Windows 2008 on its computer, or it is added to other partiton on the same drive?

Is this behavior is native to your Windows 2008 original installation, or it started after the conversion to Work Station?

 

[jorwex]

Hi All,

Let me see if I can answer some of those important questions.

@RebateMonger: "Did you say what your hardware was? I see a hardware list at the bottom of your posts, but those mention Ubuntu and Vista. Server 2008, 32-bit or 64-bit? "
The hardware I have in my sig is up to date. Are there any other specs that might be relevant? All of the OSs are of the 32bit variety. I boot to the 640 disk (has xp & ubuntu) and it goes to the Grub menu installed with Ubuntu. There's an option to go to the Windows boot loader, which then displays options for xp and server 2k8.

@McMillJb: "Can you get a shot of the 8E error? "
I've been trying to get a pic of that. I'll try and do it again (I have my camera in hand in case it appears), but unlike the other errors where it freezes on the STOP screen until I hit the power button, when the memory dump value hits 100 %, the PC restarts. So I've been unable to get a clean pic. I'll try again and post back ASAP.

@JackMDS: "Did you install Windows 2008 on its computer, or it is added to other partiton on the same drive? Is this behavior is native to your Windows 2008 original installation, or it started after the conversion to Work Station?"
I have 3 OSs installed. Ubuntu & XP are on the 640GB disk, and a 320GB disk with server 2k8 on it. So I installed it onto my previously blank 320gb disk. Is that what you wanted to know? I was a bit confused by your wording. Also, I "converted" it to a workstation OS almost immediately. That involved installing the Desktop Experience and enabling the Aero Theme, as well as disabling a few options such as the Shutdown Tracker (asks you why the "Server" is being shut down so it can keep a log). So no major, kernel level type mumbo jumbo was altered. Seemed like very benign changes from what I could tell. The only option that I didn't know too much about that I was told would be a good change was to enable SuperFetch (http://www.win2008workstation..../enabling-superfetch/)

Hope that gives some perspective. I've posted this issue on some other forums. I tried to on the official Universal Abit forums, but (I think as a side affect of them leaving the motherboard biz) they disabled new users to make posts, and have referred them to an unofficial abit haven at The Raptor Pit (http://www.theraptorpit.com/fo...ex.php?showtopic=2693). They seem to be convinced that it's a memory issue, although that seems doubtful as I'm at stock/sticker stated timings & voltages, have been running XP & ubuntu for a month+ solid w/o problems, and have run both Memtest & the built in boot-time windows memory checker error-free. Thought that was worth mentioning.

Thanks for all of the activity! Keep it coming!

 

[mcmilljb]

When booting, press F8 to get to the advanced boot options screen. See if using "Disable automatic restart on system failure" is available. That should keep it from rebooting when you get the error. Also, do you notice any actions/activities that you're doing when you get the 8E stop code? That might help narrow it down.

 

[jorwex]

Noted. Will reboot now as a precaution with camera ready

 

[jorwex]

8E Stop Error

Got a hit! Finally. Took about 30 minutes of clicking and wandering around folders till i got the error. Happened when I was using Calculator...sounds more and more like a memory thing. Weird tho..I don't understand how I could use Ubuntu & XP so flawlessly if it were a memory issue.

Oh and before anyone asks, I did verify the SHA1 hash of the image I got.

Hope that yields a bit more insight to the problem/solution. Thanks everyone!

 

[jorwex]

Just noticed some differences in the voltages/timing reported by CPUz with my current BIOS setup (everything set to default).
CPU-Z Screens

If G.Skill says to go to 2.0-2.1v (the only glaring difference in the #s that I currently have), what should I start at? 2.0V and see if the problem reoccurs?

Oh, and I noticed that the Core Speed and Multiplier change from 2004.3 MHz and 6x to 2667 MHz and 8x respectively depending on the load (it's 6x at idle). I thought Speedstep only affected notebooks due to power changes. No?

 

[mcmilljb]

Originally posted by: jorwex
Just noticed some differences in the voltages/timing reported by CPUz with my current BIOS setup (everything set to default).
CPU-Z Screens

If G.Skill says to go to 2.0-2.1v (the only glaring difference in the #s that I currently have), what should I start at? 2.0V and see if the problem reoccurs?

Oh, and I noticed that the Core Speed and Multiplier change from 2004.3 MHz and 6x to 2667 MHz and 8x respectively depending on the load (it's 6x at idle). I thought Speedstep only affected notebooks due to power changes. No?

Speedstep is on desktops too. You can change the setting in the bios.

Are you giving the ram at least 2.0V? I would think it would run fine at 1.8-1.9V since it's being underclocked to DDR2-667. According to MSDN, the 0xC0000005 parameter means you're having a memory access violation. It has recommendations for debugging. You can also read this forum post which has a situation similar to yours.

 

[RebateMonger]

A detailed discussion (second post) about 8E errors in XP.

 

[jorwex]

Thanks for the reading. Didn't quite resolve em

I just got it again and after this time, I got a "Windows Recovered From a Serious Error" for the first time. If I click details, I get this:

-------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.272.7
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 81A2FB2A
BCP3: 9B30F598
BCP4: 00000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 272_3

Files that help describe the problem:
C:\Windows\Minidump\Mini110708-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-58203-0.sysdata.xml
C:\Users\Administrator\AppData\Local\Temp\WER1DB4.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink...kid=50163&clcid=0x0409
---------------------------

Of course if you click "Check if Windows can find a solution," nothing ever happens. Also, the xml & text file they list don't exist. Does this provide any extra info that might help? On the plus side, I updated my realtek driver and now I no longer get d1 and a errors (so far)!

Thanks for your continued help everyone!