• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Server 2003 BSOD

sdilley14

Junior Member
We are having a problem with one of our servers at work and rather than explaining it, I'll post a link to this site that outlines the problem and describes the cause of the problem. We are running WIndows Server 2003 on brand new Dell PowerEdge servers. We have 7 servers and only one of them (load balance server) is encountering this problem.

http://www.osronline.com/ddkx/ddtools/bccodes_11nr.htm

And a couple more links to some other boards and pages with people encountering the same problem . . .

http://www.itnewsgroups.net/group/m.../topic4166.aspx

http://www.windowsbbs.com/showthread.php?t=44667

From what I understand, there is no real fix for this problem yet. Luckily, we don't have it that bad and it only happens once in a while. However it is a pain and we'd like to take care of it. I'll try uninstalling SP1 maybe and see if that doesn't work, and also go through the other common steps to fixing STOP errors.

I guess I'm just wondering if anyone else here has had any similar issues like this and if they found any fixes for it. I'm relatively new to working with servers (I'm being trained right now and was offered a nice bonus if I could come up with a solution for this as our IT manager is also unsure of how to fix this.) Basically, it happens once every week or two and it kicks off all users who are logged onto that server and any information they had unsaved at the time is lost. So you can see how this could be an issue. It seems to happen when someone logs off the network, but there is no consistecy with which user logs off...it's pretty random. So far I've been suggested to roll back the print driver for our W5300 printer, because this all started happening right around the time that we updated our print drivers.

Any feedback would be appreciated. Thanks!

*Here's another link to the same thread I started on another message board that shows some feedback I've gotten.

http://www.hardforum.com/showthread.php?t=955000
 
Originally posted by: sdilley14
We are having a problem with one of our servers at work and rather than explaining it, I'll post a link to this site that outlines the problem and describes the cause of the problem. We are running WIndows Server 2003 on brand new Dell PowerEdge servers. We have 7 servers and only one of them (load balance server) is encountering this problem.

http://www.osronline.com/ddkx/ddtools/bccodes_11nr.htm

And a couple more links to some other boards and pages with people encountering the same problem . . .

http://www.itnewsgroups.net/group/m.../topic4166.aspx

http://www.windowsbbs.com/showthread.php?t=44667

From what I understand, there is no real fix for this problem yet. Luckily, we don't have it that bad and it only happens once in a while. However it is a pain and we'd like to take care of it. I'll try uninstalling SP1 maybe and see if that doesn't work, and also go through the other common steps to fixing STOP errors.

I guess I'm just wondering if anyone else here has had any similar issues like this and if they found any fixes for it. I'm relatively new to working with servers (I'm being trained right now and was offered a nice bonus if I could come up with a solution for this as our IT manager is also unsure of how to fix this.) Basically, it happens once every week or two and it kicks off all users who are logged onto that server and any information they had unsaved at the time is lost. So you can see how this could be an issue. It seems to happen when someone logs off the network, but there is no consistecy with which user logs off...it's pretty random. So far I've been suggested to roll back the print driver for our W5300 printer, because this all started happening right around the time that we updated our print drivers.

Any feedback would be appreciated. Thanks!

*Here's another link to the same thread I started on another message board that shows some feedback I've gotten.

http://www.hardforum.com/showthread.php?t=955000

Send me the minidumps found in c:\windows\minidump
Run MPS Reports and send me the resulting .cab file
Follow the info/directions in my .sig.

The dumps will tell us what went wrong.
 
Back
Top