Windows Server 2003 Stop Screen (Blue Screen)

How do I go about determining the cause of a windows stop screen (blue screen) in Windows Server 2003? I noticed several people on this site talking about solving the problem but they seem several steps into the process. I preserved the memory dump and have peeked at it enough to know I don't know what I'm looking for. It looks to me like ks.sys is the problem but I may be reading the dump completely wrong. If anyone can point me in the right directly I'd appreciate it. I've included the top level of detail from the memory dump.

Thanks,
Tom

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: f77352b0
Arg3: a2000000
Arg4: 8c010400

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for nnotes.dll
*** ERROR: Module load completed but symbols could not be loaded for nnotes.dll
*** WARNING: Unable to verify checksum for NINOTES.dll
*** ERROR: Module load completed but symbols could not be loaded for NINOTES.dll

BUGCHECK_STR: 0x9C_IA32_GenuineIntel

DEFAULT_BUCKET_ID: DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 80a7ebd8 to 8087b6be

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:
f7735280 80a7ebd8 0000009c 00000000 f77352b0 nt!KeBugCheckEx+0x1b
f77353b4 80a7686f f772ffe0 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
f77353b4 600595f1 f772ffe0 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
WARNING: Stack unwind information not available. Following frames may be wrong.
0f9444e0 6005966b 15610fc8 2093b590 0f94450c nnotes+0x595f1
0f9444f0 6005da45 15610fc8 2093b59e 00000001 nnotes+0x5966b
0f94450c 600ee54f 2096e730 0f944506 2096e730 nnotes+0x5da45
0f944524 6002120e 6098b3f0 0f944519 00000001 nnotes+0xee54f
0f944570 60023256 2096e730 00000000 15918bbc nnotes+0x2120e
0f9445e0 600b49da 2096e730 0f9445fc 6095fa2d nnotes+0x23256
0f9445ec 6095fa2d 15610fc8 15918bbc 0f944628 nnotes+0xb49da
0f9445fc 6095fac1 15918bbc 00000000 00000001 nnotes+0x95fa2d
0f944628 6095fd38 0f940002 00000000 20960000 nnotes+0x95fac1
0f944658 6095afd0 15918bbc 00000000 00000001 nnotes+0x95fd38
0f944758 605beb61 15903ebc 00000024 00000001 nnotes+0x95afd0
0f9447cc 605bb2c6 00000000 159037bc 0000004f nnotes+0x5beb61
0f9448f4 605bae83 00000000 1590ce3c 0000004f nnotes+0x5bb2c6
0f944924 605b7bc6 1590d7fc 00001bf4 0f945100 nnotes+0x5bae83
0f944934 605b78f4 15918e3c 1590ce3c 00000000 nnotes+0x5b7bc6
0f945100 605cc1ea 00000000 0f9455a8 00000001 nnotes+0x5b78f4
0f9455e4 004919a0 0ffa1388 159037bc 00000000 nnotes+0x5cc1ea
0f9456bc 004bd2ce 00000000 00000002 0f94992c NINOTES+0x819a0
0f9456d8 6000110d 6000114a 6000110d 6000114a NINOTES+0xad2ce
0f9456dc 6000114a 6000110d 6000114a 01a1a7c2 nnotes+0x110d
6000110d ff09e856 8366ffff 7c000c7e 852c7f1b nnotes+0x114a
60001111 8366ffff 7c000c7e 852c7f1b 562874ff 0xff09e856
60001115 7c000c7e 852c7f1b 562874ff ffff76e8 0x8366ffff
8366ffff 00000000 00000000 00000000 e9900000 0x7c000c7e


STACK_COMMAND: dds @$csp ; kb

FOLLOWUP_IP:
ks!CKsQueue:eleteStreamPointer+a4
f7008b72 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ks!CKsQueue:eleteStreamPointer+a4

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42435e1f

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_ks!CKsQueue:eleteStreamPointer+a4

BUCKET_ID: 0x9C_IA32_GenuineIntel_ks!CKsQueue:eleteStreamPointer+a4

Followup: MachineOwner
---------

 

Does this apply to Xeon processors

Does this apply to Xeon processors? Will downloading the memtest.exe type program sufficiently test the memory?

 

Is Service Pac 1 installed?

 

Yes, Service Pack 1 is installed.

 

Maybe. Software testers for hardware issues are not super reliable.

If memtest finds a problem, you do have a problem.

If memtest (or any of it's software cousins) does not find a problem, it simply didn't find a problem and you may or may not have bad memory.

You need to either buy a hardware tester or else start swapping out memory modules and see if any single one of them makes the system go nuts.

 

Call your hardware vendor. A machine check is thrown by the system, and has deliberate meaning based on the specifics of your machine. Only your hardware vendor can decrypt this goo for you.