Further Diagnosis of BSOD 124

0

We are experiencing spurious BSOD's (about once in 1..2 days, time varies) on a Hyper-V Server. I've come as far as this:

Bug Check code 124

e.g. 0x00000124 (0x0000000000000000, 0xfffffa800a3bf558, 0x0000000000000000, 0x0000000000000000).

Parameter 1, 3 and 4 are all zero. Parameter 2 (some struct's address) varies.

(a) Memory Check Tool
Windows Memory Diagnostic only checks the first 4GB (the machine has 12GB) - can anyone recommend a memory check tool?

(b) Further Diagnosis
I don't understand how to go on with the error information. I've read a handful of articles & PDF's, but still don't know how to go on. Bug Check

System: Intel i7-920, SuperMicro X8SAX, 12GB RAM, 5 SATA drives, running Hyper-V Server.

The system was running fine for over a month with just one virtual machine on it, crashes started after migrating another physical machine (W2K3 Server) to it. Windows Updates are applied.

bsod
asked on Server Fault Feb 2, 2010 by peterchen • edited Feb 2, 2010 by peterchen

1 Answer

1

More often than not BSOD are caused by driver issues, I would probably make sure that all the drivers on your server are signed and WHQL approved.

To track down the root cause of your problem would be to open the crash dump in WinDBG and find the exact process/command that caused the fault, even then this isnt always as clear cut as you would think.

answered on Server Fault Feb 3, 2010 by commandbreak

User contributions licensed under CC BY-SA 3.0