VMware Communities
mbmast
Enthusiast
Enthusiast

Win 7 x64 Host OS Occasionally Blue Screens when Workstation 7 is Started

Host machine is SuperMicro X8SAX, (Tylersburg-DT) BOARD / Socket 1366, Intel X58 Express Chipset, blah blah blah. Motherboard has ICH10R RAID controller and Intel Matrix Storage Manager is installed. 8GB RAM installed.

Host OS is Windows 7 Professional x64.

The machine boots up fine. About half the time I start Workstation 7, the machine (i.e. the host OS) Blue Screens. Whenever this happens, the process name (from the dump) is always vmware-vmx.exe. Here's the dump:

WARNING: Whitespace at end of path element

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File

Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element

Symbol search path is: SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols

;C:\Windows 7 RTM x86 Retail Symbols

Executable search path is:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909

Machine Name:

Kernel base = 0xfffff800`0284b000 PsLoadedModuleList = 0xfffff800`02a88e50

Debug session time: Tue Apr 27 09:15:42.373 2010 (UTC - 7:00)

System Uptime: 0 days 0:03:23.466

Loading Kernel Symbols

...............................................................

................................................................

...................

Loading User Symbols

Loading unloaded module list

...

*******************************************************************************

  • *

  • Bugcheck Analysis *

  • *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004042920, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

Followup: MachineOwner

-


2: kd> !analyze -v

*******************************************************************************

  • *

  • Bugcheck Analysis *

  • *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

  1. Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041790, The subtype of the bugcheck.

Arg2: fffffa8004042920

Arg3: 000000000000ffff

Arg4: 0000000000000000

Debugging Details:

-


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: vmware-vmx.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000292eede to fffff800028bb600

STACK_TEXT:

fffff880`082de828 fffff800`0292eede : 00000000`0000001a 00000000`00041790 fffffa80`04042920 00000000`0000ffff : nt!KeBugCheckEx

fffff880`082de830 fffff800`028eecc9 : 00000000`00000000 00000000`08214fff 00000000`00000001 00000000`0000001e : nt! ?? ::FNODOBFM::`string'+0x33946

fffff880`082de9f0 fffff800`02bd5170 : fffffa80`06d83db0 0007ffff`00000000 fffffa80`093c1380 fffffa80`093c1380 : nt!MiRemoveMappedView+0xd9

fffff880`082deb10 fffff800`02bd557b : 00000000`00000000 00000000`08200000 fffffa80`00000001 00000000`08200001 : nt!MiUnmapViewOfSection+0x1b0

fffff880`082debd0 fffff800`028ba853 : 00000000`00000000 00000000`00000000 fffffa80`06e2f680 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f

fffff880`082dec20 00000000`774f015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`067be098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774f015a

STACK_COMMAND: kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+33946

fffff800`0292eede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

Followup: MachineOwner

-


0 Kudos
1 Reply
mbmast
Enthusiast
Enthusiast

Resolved. Bad memory. All 4 DIMMs required replacing.

0 Kudos