My install ended up in BSOD screen. I reverted back to Win2003 SP2 and here
is dump analysis below. Interesting that after revering back Windows 2008
installer informed that I need to run upgrade advisor to make sure everything
is good. I don't think there is upgrade advisor available for Windows 2008.

Anyway, what is my next step? I did not find any details about superbmc.sys
driver. Computer I'm installing this on is dual CPU XEON 2.0 GHZ on
SuperMicro motherboard and runs Windows 2003 SP2 just fine.

What do I do?





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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: cc8133be, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 818e2455, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000002, (reserved)

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




READ_ADDRESS: GetPointerFromAddress: unable to read from 819726d8
Unable to read MiSystemVaType memory at 819532e0
cc8133be

FAULTING_IP:
nt!RtlInitUnicodeStringEx+1f
818e2455 668b10 mov dx,word ptr [eax]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 806998ec -- (.trap 0xffffffff806998ec)
ErrCode = 00000000
eax=cc8133be ebx=00000000 ecx=8069997c edx=00000096 esi=cc8133c0 edi=83eaf446
eip=818e2455 esp=80699960 ebp=80699964 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210286
nt!RtlInitUnicodeStringEx+0x1f:
818e2455 668b10 mov dx,word ptr [eax]
ds:0023:cc8133be=????
Resetting default scope

LAST_CONTROL_TRANSFER: from 818a0ae4 to 818b6b4e

STACK_TEXT:
806998d4 818a0ae4 00000000 cc8133be 00000000 nt!MmAccessFault+0x158
806998d4 818e2455 00000000 cc8133be 00000000 nt!KiTrap0E+0xdc
80699964 818e300b 8069997c cc8133be 83eaf446 nt!RtlInitUnicodeStringEx+0x1f
80699984 8c9d340d 806999c8 cc8133be 83eaf478 nt!RtlAppendUnicodeToString+0x1b
WARNING: Stack unwind information not available. Following frames may be
wrong.
806999e4 8c9d570c 83eaf478 00000000 819a9aeb superbmc+0x40d
80699bd4 81b9323e 00000001 00000000 80699c20 superbmc+0x270c
80699c38 81b93935 8080d7b4 00000000 00000000
nt!IopInitializeSystemDrivers+0x1af
80699c94 81b9744d 8080f590 8335fe10 8335fae8 nt!IoInitSystem+0x62c
80699d74 81998034 80699dc0 819ee6ad 8080f590
nt!Phase1InitializationDiscard+0xb86
80699d7c 819ee6ad 8080f590 cd61f536 00000000 nt!Phase1Initialization+0xd
80699dc0 818d5686 81998027 8080f590 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
superbmc+40d
8c9d340d ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: superbmc+40d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: superbmc

IMAGE_NAME: superbmc.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4328c0f7

FAILURE_BUCKET_ID: 0x50_superbmc+40d

BUCKET_ID: 0x50_superbmc+40d

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

Hello ChanKaiShi,

Maybe this can you:
http://technet.microsoft.com/en-us/l.../bb977556.aspx

http://www.windowsservercatalog.com/

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> My install ended up in BSOD screen. I reverted back to Win2003 SP2 and
> here is dump analysis below. Interesting that after revering back
> Windows 2008 installer informed that I need to run upgrade advisor to
> make sure everything is good. I don't think there is upgrade advisor
> available for Windows 2008.
>
> Anyway, what is my next step? I did not find any details about
> superbmc.sys driver. Computer I'm installing this on is dual CPU XEON
> 2.0 GHZ on SuperMicro motherboard and runs Windows 2003 SP2 just fine.
>
> What do I do?
>
> 0: kd> !analyze -v
> ************************************************** ********************
> *********
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** ********************
> *********
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> Invalid system memory was referenced. This cannot be protected by
> try-except,
> it must be protected by a Probe. Typically the address is just plain
> bad or
> it
> is pointing at freed memory.
> Arguments:
> Arg1: cc8133be, memory referenced.
> Arg2: 00000000, value 0 = read operation, 1 = write operation.
> Arg3: 818e2455, If non-zero, the instruction address which referenced
> the
> bad memory
> address.
> Arg4: 00000002, (reserved)
> Debugging Details:
> ------------------
> READ_ADDRESS: GetPointerFromAddress: unable to read from 819726d8
> Unable to read MiSystemVaType memory at 819532e0
> cc8133be
> FAULTING_IP:
> nt!RtlInitUnicodeStringEx+1f
> 818e2455 668b10 mov dx,word ptr [eax]
> MM_INTERNAL_CODE: 2
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
>
> BUGCHECK_STR: 0x50
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 0
>
> TRAP_FRAME: 806998ec -- (.trap 0xffffffff806998ec)
> ErrCode = 00000000
> eax=cc8133be ebx=00000000 ecx=8069997c edx=00000096 esi=cc8133c0
> edi=83eaf446
> eip=818e2455 esp=80699960 ebp=80699964 iopl=0 nv up ei ng nz
> na pe nc
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> efl=00210286
> nt!RtlInitUnicodeStringEx+0x1f:
> 818e2455 668b10 mov dx,word ptr [eax]
> ds:0023:cc8133be=????
> Resetting default scope
> LAST_CONTROL_TRANSFER: from 818a0ae4 to 818b6b4e
>
> STACK_TEXT:
> 806998d4 818a0ae4 00000000 cc8133be 00000000 nt!MmAccessFault+0x158
> 806998d4 818e2455 00000000 cc8133be 00000000 nt!KiTrap0E+0xdc
> 80699964 818e300b 8069997c cc8133be 83eaf446
> nt!RtlInitUnicodeStringEx+0x1f
> 80699984 8c9d340d 806999c8 cc8133be 83eaf478
> nt!RtlAppendUnicodeToString+0x1b
> WARNING: Stack unwind information not available. Following frames may
> be
> wrong.
> 806999e4 8c9d570c 83eaf478 00000000 819a9aeb superbmc+0x40d
> 80699bd4 81b9323e 00000001 00000000 80699c20 superbmc+0x270c
> 80699c38 81b93935 8080d7b4 00000000 00000000
> nt!IopInitializeSystemDrivers+0x1af
> 80699c94 81b9744d 8080f590 8335fe10 8335fae8 nt!IoInitSystem+0x62c
> 80699d74 81998034 80699dc0 819ee6ad 8080f590
> nt!Phase1InitializationDiscard+0xb86
> 80699d7c 819ee6ad 8080f590 cd61f536 00000000
> nt!Phase1Initialization+0xd
> 80699dc0 818d5686 81998027 8080f590 00000000
> nt!PspSystemThreadStartup+0x9d
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> superbmc+40d
> 8c9d340d ?? ???
> SYMBOL_STACK_INDEX: 4
>
> SYMBOL_NAME: superbmc+40d
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: superbmc
>
> IMAGE_NAME: superbmc.SYS
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 4328c0f7
>
> FAILURE_BUCKET_ID: 0x50_superbmc+40d
>
> BUCKET_ID: 0x50_superbmc+40d
>
> Followup: MachineOwner
> ---------