windows 2003 blue screen of death -- please help

[Francesca]

Hi,

I have recently experienced increasingly frequent occurrences of BSOD under Windows 2003 server and I was hoping someone here could help.

I have been running Windows 2003 Server as my desktop OS, after optimizing it for such purpose following the instructions I found in a magazine, and everything has worked fine so far, in fact it's much more stable, and faster than XP was.

I know that's not the "official" use for this OS, but it has largely been worth it for me and I have gotten enough put-downs from naysayers, so please only respond to help if you can, and not just to tell me I'm not supposed to be doing this in the first place.

Nevertheless, I expected problems at some point and here they are. The problem manifests usually when I plug in my earphones and Windows automatically switches sound settings from speakers to earphones, however most recently I have also had an occurrence of the error when loading Windows Media Player.

The error shows up as a sudden Blue Screen of Death and physical memory dump, with the code: IRQL_NOT_SAME_OR_EQUAL

At the bottom of the BSOD, some errorcodes appear. The last time they were as follows:
STOP: 0x000000A (0x80FFFFE8, 0x00000002, 0x00000001, 0x804F1978)

When Windows finally recovers, it produces a critical error log with more codes and details. The last time these were:

BCCode : a BCP1 : 80FFFFE8 BCP2 : 00000002 BCP3 : 00000001
BCP4 : 804F1978 OSVer : 5_2_3790 SP : 0_0 Product : 274_3

C:\WINDOWS\Minidump\Mini112603-01.dmp
C:\DOCUME~1\Francesca\LOCALS~1\Temp\WER1.tmp.dir00 \sysdata.xml

I am running Windows 2003 Server on a Pentium 4 3.06Ghz machine
512MB RAM,
Dell motherboard.

At the time of the last crash I had Tiny Personal Firewall and Symantec Antivirus, along with the control panel app for my ATI videocard running (minimized in taskbar).

Perhaps somebody here has run into this problem or a similar one before? Or maybe you have any suggestions or leads to follow? I'd be very grateful for any help.

Thank you.
--
Francesca

[BlueIce]

I have been running Windows 2003 Server as my desktop OS, after optimizing it for such purpose following the instructions I found in a magazine, and everything has worked fine so far, in fact it's much more stable, and faster than XP was.

Retrace and make sure as to above, you have changed was correct, if so maybe ditch the changes in the mag or adopt a different style of change on the opp system
I have been runing 2k for over 2 years now and had minorr probs, Doh mistake I made

User error = 80% And if the changes made where in the reg make sure you know what they do don't just follow a guide line from a mag.

[SKYLINEGTR33MWJ]

read the whole article on PERMANENT SWAP and found it quite interesting.... although i do have one question

i did not know.. but i have my system currently setup this way

C: 512-1024mb swap
D: 512-1024mb swap

anything wrong with that...... besides the fact that i need to change it to a more permanent file size.....

C:1024-1024mb swap

but can there be two swaps?

[Soheils91]

Originally posted by Francesca

Dell motherboard.

Theres your problem right there. No im serious i hate dell with a passion, i would give my soul to see them all burn.

[Ace McGirk]

Personally, I think you are SOL on this.You have an unreleased OS with programs that have not been designed to run on it.As you keep adding new programs,you are bound to run into these problems.

in fact it's much more stable,

Now you know why they release BETA versions.

[[Neo770]]

err Windows Server 2003 is released

[Marvinator]

I beleive your problem may lie in the Tiny Personal Firewall program. The URL_ portion of that error says that it's a problem dealing with connectivity and the one thing sitting in the way is your TPF. Reconfigure your MS2003Server or utilize a different firewall for a while and see if this reduces the problem of the BSOD

[goodole1]

IMHO and my firends (IT Geek) they had to remove all Symantec prodcuts on the machines that he takes care of in his place of work; as they were causing register corruption.