Dear all,
I have configured two windows server 2003 R2 servers in cluster mode. The cluster server gets authenticated by a domain controller. The Primary and seondary servers continue to run for some time and then either hang or crash with blue screen of death. BSOD is seen especially with only one server though.
I have put the event logs for reference. I must say that the problem started happening only after the RAM capacity was changed from 8GB to 32 GB. There was also some power supply (UPS) change done on the same day.
But the tools like memtest-86 have found no errors with the new RAMs.
The Primary server has seen BSOD while the secodary simply freezes after running for few hours. The taskbar is hung (although I can launch some applications from the task manager).. Launching a new explorer does not help as it also gets hung immediately.
Please help.
Below I have given event details when BSOD happened on Primary server.
Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1076
Date: 2/7/2012
Time: 4:05:55 PM
User: S-1-5-21-3433499848-1543794289-3939903927-500
Computer: DRSECSVR
Description:
The reason supplied by user DRDOMAIN\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d1 (0x00000000, 0xd0000002, 0x00000000, 0xb3c64a6c)
Comment: 0x000000d1 (0x00000000, 0xd0000002, 0x00000000, 0xb3c64a6c)
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.
Data:
0000: 0f 00 05 08 ....
The winDBG analysis (with my limited knowledge) gives following ersult
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b3c64a6c, address which referenced memory
Thank you very much in advance.......
I have configured two windows server 2003 R2 servers in cluster mode. The cluster server gets authenticated by a domain controller. The Primary and seondary servers continue to run for some time and then either hang or crash with blue screen of death. BSOD is seen especially with only one server though.
I have put the event logs for reference. I must say that the problem started happening only after the RAM capacity was changed from 8GB to 32 GB. There was also some power supply (UPS) change done on the same day.
But the tools like memtest-86 have found no errors with the new RAMs.
The Primary server has seen BSOD while the secodary simply freezes after running for few hours. The taskbar is hung (although I can launch some applications from the task manager).. Launching a new explorer does not help as it also gets hung immediately.
Please help.
Below I have given event details when BSOD happened on Primary server.
Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1076
Date: 2/7/2012
Time: 4:05:55 PM
User: S-1-5-21-3433499848-1543794289-3939903927-500
Computer: DRSECSVR
Description:
The reason supplied by user DRDOMAIN\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d1 (0x00000000, 0xd0000002, 0x00000000, 0xb3c64a6c)
Comment: 0x000000d1 (0x00000000, 0xd0000002, 0x00000000, 0xb3c64a6c)
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.
Data:
0000: 0f 00 05 08 ....
The winDBG analysis (with my limited knowledge) gives following ersult
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b3c64a6c, address which referenced memory
Thank you very much in advance.......
