wxlmalanis
Contributor
Contributor

Windows Server 2003 Entrprise R2 random BSoD

Hello:

 

I am currently on Workstation 17.5 (host Windows 11 Pro x64) with 32 GB RAM.  I installed Windows Server 2003 R2 Enterprise 23 bit in a fresh install and am receiving a BSoD with error 0x0000007F at random.  I search through the error logs and get no results as to what it could possibly be.  As the result thereof, I looked at my previous VMs that have been running like a champ with zero crashes and replicated their setups (hardware version, processor count, etc.) still no dice and random BSoD; so now I am asking here the following:

it is important to note that this error does not occur while in safe mode or if vmware tools is not installed.

1) What is this error as I can find no trace of it in the event viewer

2) what are the minimum virtual hardware settings that need to be set up to make sure Windows Server 2003 R2 runs as expected without crashing

3) Why do some VMs run and not complain while this articular project goes up in smoke no matter what I do

all I can say is after playing wit this in a lab for about 3 days with now answer is What the actual fries is going on here? is my project an example of "cursed" computing?"

If anyone could answer this question, that would be wonderful!

 

Thanks for any help given

 

Reply
0 Kudos
CarltonR
Hot Shot
Hot Shot


@wxlmalanis wrote: . . . I installed Windows Server 2003 R2 Enterprise 23 bit . . .

Running a '23 bit' operating system might be a issue !

On a more serious note:

- is the Win Svr 2003 Ent x32 source image legitimate and verifiable, i.e. checksum validated

- how much memory resources have you allocated to the VM

- have you tried to install the x64 version ?

As a  starting point may I suggest searching this forum for the 0x0000007F error, as there is plethora of invaluable information regards this . . . starting with Windows 2003 bluescreen

 

Note: On a cautionary note, as this operating system is unsupported, It may be unwise to present it to an 'open' network.

Reply
0 Kudos
wxlmalanis
Contributor
Contributor

First off, thanks for the links!  Also, thanks for pointing out my typo :-). I will look at the cited links to see what I can come up with and report back

Reply
0 Kudos
wxlmalanis
Contributor
Contributor

Hi Everyone:

 

I did get a chance to do something not listed and revert back to Workstation 17.0 and that officially fixed it for my case :slightly_smiling_face: so as such, I know it's not a solution outright but it gets the job done to get me back up and running in the shortest amount of time. I will see if I can investigate the other solutions in the future but for now given my specific configuration and my specific apps; it gets the job done.  The old maxim of "just undo the last change that happened before things started acting screwy..." and that fixed it.

 

Thanks again for the help :slightly_smiling_face: issue closed

View solution in original post

Reply
0 Kudos