The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.
OLD Computer BSOD every time a network computers connects to a shared folder
Hello All;
This started happening the other day.
And since I brought a new DC into the network, I reinstalled the old DC to use as a file server only.
I thought at that time, that since the system had been up and running for 3 years, that it was time for a reinstall any way.
However, the BSOD's continued to happen.
Every time that a network computer access a share, the server reboots.
However, it does not leave a paper trail every time it reboots.
So I F8 and made it not shut down after a BSOD, and this is what I got from it.
STOP: 0xD1
ftdisk.sys - Address F740F068 base at F73F5000
acpi.sys - Address F743E518 base at F7432000
The above BSOD caused a Dump file that pointed solely to the acpi.sys as being the issue.
I looked in on one of the earlier dump files, and it was pointing to
CLASSPNP.sys
--------
Things I have done.
chkdsk /f
All drives check out OK, with no known issues.
I have replaced the Network cards 4 times and it still reboots during network connection.
(I even tried the 4 NICS in each of the 3 open PCI slots, and still caused the same issue)
Example.
I am converting our music library to a smaller bitrate, and when I connect to the server
To update the MP3 Metadata
It reboots, and this is what I did to cause the above 2 Dump files.
I have removed all other PCI cards that were not being used.
And even swapped out the memory.
Anything else that anyone can think of?
Besides that, the motherboard could be going?
One last note.
As long as no network connections are made, it stays on for a long time.
The longest being about 3 hours before my son stopped by, and moved the mouse on my other computer, causing it to send a signal to the server and off she went to blackness again. (The program was opened that edits the MP3 Metadata)
Carrzkiss
This started happening the other day.
And since I brought a new DC into the network, I reinstalled the old DC to use as a file server only.
I thought at that time, that since the system had been up and running for 3 years, that it was time for a reinstall any way.
However, the BSOD's continued to happen.
Every time that a network computer access a share, the server reboots.
However, it does not leave a paper trail every time it reboots.
So I F8 and made it not shut down after a BSOD, and this is what I got from it.
STOP: 0xD1
ftdisk.sys - Address F740F068 base at F73F5000
acpi.sys - Address F743E518 base at F7432000
The above BSOD caused a Dump file that pointed solely to the acpi.sys as being the issue.
I looked in on one of the earlier dump files, and it was pointing to
CLASSPNP.sys
--------
Things I have done.
chkdsk /f
All drives check out OK, with no known issues.
I have replaced the Network cards 4 times and it still reboots during network connection.
(I even tried the 4 NICS in each of the 3 open PCI slots, and still caused the same issue)
Example.
I am converting our music library to a smaller bitrate, and when I connect to the server
To update the MP3 Metadata
It reboots, and this is what I did to cause the above 2 Dump files.
I have removed all other PCI cards that were not being used.
And even swapped out the memory.
Anything else that anyone can think of?
Besides that, the motherboard could be going?
One last note.
As long as no network connections are made, it stays on for a long time.
The longest being about 3 hours before my son stopped by, and moved the mouse on my other computer, causing it to send a signal to the server and off she went to blackness again. (The program was opened that edits the MP3 Metadata)
Carrzkiss
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Reinstalling the system right now, from the MS CD.
I downloaded the SP2 and IE8 for Win2k3.
I will post on rather I continue to have the BSOD.
I would like to mention.
During setup, I chose to join the Domain.
It joined without an issue, and did not crash.
So, we will see.
I downloaded the SP2 and IE8 for Win2k3.
I will post on rather I continue to have the BSOD.
I would like to mention.
During setup, I chose to join the Domain.
It joined without an issue, and did not crash.
So, we will see.
New install and still crashing after a new install.
Not sure.
Time to call it a night, and worry about it when I get up.
I did read somewhere during my research of this issue, that some of the windows updates will fix the issues of some of the BSOD's that I have had. If I can only get them to download and install I will be doing good.
Too bad Microsoft did not release a Rollup for post SP2 for Windows 2003 Server.
The only other thing that I can try, is installing XP on the machine.
As I stated, it is simply going to be nothing more than a file server.
So, if I cannot get the updates to do anything by tomorrow, then I will try XP and see what happens with the BSOD's.
Not sure.
Time to call it a night, and worry about it when I get up.
I did read somewhere during my research of this issue, that some of the windows updates will fix the issues of some of the BSOD's that I have had. If I can only get them to download and install I will be doing good.
Too bad Microsoft did not release a Rollup for post SP2 for Windows 2003 Server.
The only other thing that I can try, is installing XP on the machine.
As I stated, it is simply going to be nothing more than a file server.
So, if I cannot get the updates to do anything by tomorrow, then I will try XP and see what happens with the BSOD's.
And you're installing an OS that's been out of all support from MS for 2 years why?
You haven't mentioned since the reinstall what the BSOD is pointing to?
Blue Screen's are always hardware related, so either the hardware is coincidentally failing or bad drivers
You haven't mentioned since the reinstall what the BSOD is pointing to?
Blue Screen's are always hardware related, so either the hardware is coincidentally failing or bad drivers
You said this server is only going to be used as a file share. Have you thought about installing FreeNAS on it instead of Windows? It could reduce overhead and improve performance, and give you an up-to-date OS with security patches. Here's a basic guide:
http://www.tecmint.com/installation-of-freenas/
http://www.tecmint.com/installation-of-freenas/
Sounds like bad ram.
You could use this registry hack to make your server 2003 look like XP POS which is still being patched and supported.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
"Installed"=dword:00000001
Just save the above as a .reg file install.
USE AT YOUR OWN RISK!
I have tested it and it does work on server 2003.
You could use this registry hack to make your server 2003 look like XP POS which is still being patched and supported.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
"Installed"=dword:00000001
Just save the above as a .reg file install.
USE AT YOUR OWN RISK!
I have tested it and it does work on server 2003.
@pgm554 except he changed out the RAM.
It could be a bad RAM slot. I've had that happen once, but not on a server. Could also just check for dust in the slots, cleaning them with some compressed air, and making sure the sticks are securely slotted in.
It could be a bad RAM slot. I've had that happen once, but not on a server. Could also just check for dust in the slots, cleaning them with some compressed air, and making sure the sticks are securely slotted in.
OK, guys. (Just now come on here after figuring it out, was not expecting in comments. So they are welcomed, and here is what has happened since my last post on the re-install)
This is what is going on.
It got so it was taking forever to load windows on a new install. (About 10 minutes just to get to the desktop).
Then when it finally got to the desktop, it would reboot with no dump files and no entry in the EV
Right before I gave up, I tried to install the server once more, and it crashed about 1/2 way through the setup.
That was it.
I took another MB that I have under my desk for the last year, and swapped everything over and this is what I found out.
Possible issues.
Motherboard - one of more of the components are bad on it.
CPU
Memory - one of the sticks of the memory that I installed was bad.
I installed the memory on the other MB.
Would not boot up
Removed one stick, still did not boot, removed it and replaced the other and it booted. (1 is bad)
Added in the other 3 sticks, and it is installing the server right now.
It comes down to one or more of the following.
MB - Bad
Memory - Bad
@Cris
It is an old 32-bit box.
Win2k3 has been running on it for years, as my DC.
I have a 64-bit box that is now running the DC.
The Win2k3 box is going to be used now as the File Server.
I do not care if M$ has stopped support on it, as long as it does what I need it to do, then that is what counts.
@marsilies
FreeNas, will have to do some research on that one.
I heard of it, but never used it before.
About like Linux. Never messed with it, and now I have it installed in a VM on my laptop (linux Mint)
@pgm554
You are absolutely right on this one.
It turned out that it was bad ram and also bad MB.
This is what is going on.
It got so it was taking forever to load windows on a new install. (About 10 minutes just to get to the desktop).
Then when it finally got to the desktop, it would reboot with no dump files and no entry in the EV
Right before I gave up, I tried to install the server once more, and it crashed about 1/2 way through the setup.
That was it.
I took another MB that I have under my desk for the last year, and swapped everything over and this is what I found out.
Possible issues.
Motherboard - one of more of the components are bad on it.
CPU
Memory - one of the sticks of the memory that I installed was bad.
I installed the memory on the other MB.
Would not boot up
Removed one stick, still did not boot, removed it and replaced the other and it booted. (1 is bad)
Added in the other 3 sticks, and it is installing the server right now.
It comes down to one or more of the following.
MB - Bad
Memory - Bad
@Cris
It is an old 32-bit box.
Win2k3 has been running on it for years, as my DC.
I have a 64-bit box that is now running the DC.
The Win2k3 box is going to be used now as the File Server.
I do not care if M$ has stopped support on it, as long as it does what I need it to do, then that is what counts.
@marsilies
FreeNas, will have to do some research on that one.
I heard of it, but never used it before.
About like Linux. Never messed with it, and now I have it installed in a VM on my laptop (linux Mint)
@pgm554
You are absolutely right on this one.
It turned out that it was bad ram and also bad MB.
While I understand your comments about the box...let me ask you this? Is your network connected to the Internet? If so, do you have a business class firewall with limited port forwarding (no 3389, no telnet, etc) your 2003 box would be the weak link in the chain if they can get through the firewall. And 2003 is full now of unpatched holes
Glad you got it figured out
Glad you got it figured out
The win2k3 server is protected.
Right now I am just wanting to make sure that this new (old) build is going to do right.
If it does, then I might look in on the FreeNAS.
Just need to do some research on it, to make sure that is what I am wanting to have.
As I watch a squirrel playing in a hole in the yard.....
Right now I am just wanting to make sure that this new (old) build is going to do right.
If it does, then I might look in on the FreeNAS.
Just need to do some research on it, to make sure that is what I am wanting to have.
As I watch a squirrel playing in a hole in the yard.....
Been my experience that when you see a hardware driver calling out a memory location.it's pretty much either a ram or mobo issue.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial