Hello All,
I have a brand new Alienware M17x-R2, and have been experiencing issues with the machine, most notably BSOD's. I have suffered about 8 or so in the first 3 weeks, and have had to reinstall my OS 3 times already due to my OS disappearing the first time, and the second time after alienware thought to replace my graphics cards, and the third time after updating my BIOS.
Unfortunately, I have only captured one of the BSOD Minidump files with the most recent installation. I would like to narrow down what may be the source of my problems.
I have run the the Windows Memory Diagnostic Extended Memory test twice and everything turned out okay, and I have run the alienware diagnostic utility and everything passed there as well. So not sure where to begin. I have not run the driver verifier.exe yet though.
Here is the Minidump output:
Notice the:
which seems to be related to a 3d software program I use, and the
I have never analyzed these files before, so i am wondering if the 3d program caused a memory corruption, or if the memory hardware is bad. If anyone can please help me make an informed decision, as the tech support at Alienware is horrible.
I also should mention that when viewing the event viewer, I have a critical error entry listed as the following:
I also have the following error entries in the event viewer around the same few minutes as the Minidump file creation:
and another error:
Here are my system specs for those interested:
Thanks to anyone who may be able to provide any insight into these issues I am experiencing!
I have a brand new Alienware M17x-R2, and have been experiencing issues with the machine, most notably BSOD's. I have suffered about 8 or so in the first 3 weeks, and have had to reinstall my OS 3 times already due to my OS disappearing the first time, and the second time after alienware thought to replace my graphics cards, and the third time after updating my BIOS.
Unfortunately, I have only captured one of the BSOD Minidump files with the most recent installation. I would like to narrow down what may be the source of my problems.
I have run the the Windows Memory Diagnostic Extended Memory test twice and everything turned out okay, and I have run the alienware diagnostic utility and everything passed there as well. So not sure where to begin. I have not run the driver verifier.exe yet though.
Here is the Minidump output:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051610-22245-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
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`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sun May 16 02:35:49.389 2010 (UTC - 7:00)
System Uptime: 0 days 0:10:44.388
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa80c0000170, 0, fffff80002e9ce1e, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCheckAging+5e )
Followup: MachineOwner
---------
2: 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: fffffa80c0000170, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e9ce1e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0
fffffa80c0000170
FAULTING_IP:
nt!MiCheckAging+5e
fffff800`02e9ce1e 8b4748 mov eax,dword ptr [rdi+48h]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: tdlmake.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800cb066d0 -- (.trap 0xfffff8800cb066d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000077610000 rbx=0000000000000000 rcx=0000000000005a4d
rdx=0000000077610000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e606d7 rsp=fffff8800cb06868 rbp=fffff8800cb06ca0
r8=0000000000000000 r9=fffff8800cb068a8 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!RtlImageNtHeaderEx+0x3f:
fffff800`02e606d7 66390a cmp word ptr [rdx],cx ds:00000000`77610000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002eff801 to fffff80002e80600
STACK_TEXT:
fffff880`0cb06218 fffff800`02eff801 : 00000000`00000050 fffffa80`c0000170 00000000`00000000 fffff880`0cb06380 : nt!KeBugCheckEx
fffff880`0cb06220 fffff800`02e7e6ee : 00000000`00000000 00000000`00000000 ffffffff`ffffff00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`0cb06380 fffff800`02e9ce1e : 00000000`77610000 fffff800`02e33b99 00000000`00000010 00000000`00000286 : nt!KiPageFault+0x16e
fffff880`0cb06510 fffff800`02e9a6a0 : 00000000`00000000 00000000`77610000 00000000`00000000 00000000`00000000 : nt!MiCheckAging+0x5e
fffff880`0cb06570 fffff800`02e7e6ee : 00000000`00000000 00000000`00000000 00000200`00001000 00000000`00020005 : nt!MmAccessFault+0x3c0
fffff880`0cb066d0 fffff800`02e606d7 : fffff800`02e60762 fffffa80`074bdb60 fffffa80`07094b30 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`0cb06868 fffff800`02e60762 : fffffa80`074bdb60 fffffa80`07094b30 00000000`00000001 fffff880`0cb06ca0 : nt!RtlImageNtHeaderEx+0x3f
fffff880`0cb06870 fffff800`0314dfb7 : fffff880`0cb06ca0 00000000`00000000 00000000`00000001 fffffa80`07094b30 : nt!RtlImageNtHeader+0x1e
fffff880`0cb068a0 fffff800`0314f10c : fffffa80`074bdb60 fffffa80`00000000 00000000`14050800 00000000`00000000 : nt!DbgkCreateThread+0x1b7
fffff880`0cb06a80 fffff800`02e5ec35 : fffff880`009b2180 00000000`00000000 fffff800`0314f034 fffffa80`074bdb60 : nt!PspUserThreadStartup+0xd8
fffff880`0cb06ae0 fffff800`02e5ebb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`0cb06c20 00000000`77643260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0012ffd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77643260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCheckAging+5e
fffff800`02e9ce1e 8b4748 mov eax,dword ptr [rdi+48h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiCheckAging+5e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiCheckAging+5e
BUCKET_ID: X64_0x50_nt!MiCheckAging+5e
Followup: MachineOwner
---------
2: kd> lmvm nt
start end module name
fffff800`02e10000 fffff800`033ec000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Fri Feb 26 23:55:23 2010 (4B88CFEB)
CheckSum: 00545094
ImageSize: 005DC000
File version: 6.1.7600.16539
Product version: 6.1.7600.16539
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16539
FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Notice the:
PROCESS_NAME: tdlmake.exe
which seems to be related to a 3d software program I use, and the
IMAGE_NAME: memory_corruption
I have never analyzed these files before, so i am wondering if the 3d program caused a memory corruption, or if the memory hardware is bad. If anyone can please help me make an informed decision, as the tech support at Alienware is horrible.
I also should mention that when viewing the event viewer, I have a critical error entry listed as the following:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 5/16/2010 2:36:56 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: my-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-05-16T09:36:56.393613900Z" />
<EventRecordID>7135</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>my-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">80</Data>
<Data Name="BugcheckParameter1">0xfffffa80c0000170</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0xfffff80002e9ce1e</Data>
<Data Name="BugcheckParameter4">0x5</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
I also have the following error entries in the event viewer around the same few minutes as the Minidump file creation:
Log Name: Application
Source: VSS
Date: 5/16/2010 2:37:47 AM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: my-PC
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {9dd9e623-d196-4350-95a6-59860a376908}
Event Xml:
<Event xmlns="">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-05-16T09:37:47.000000000Z" />
<EventRecordID>2082</EventRecordID>
<Channel>Application</Channel>
<Computer>my-PC</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005, Access is denied.
</Data>
<Data>
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {9dd9e623-d196-4350-95a6-59860a376908}</Data>
<Binary>2D20436F64653A20575254575254494330303030313235312D2043616C6C3A20575254575254494330303030313230352D205049443A202030303030313633322D205449443A202030303030313638302D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>
and another error:
Log Name: System
Source: EventLog
Date: 5/16/2010 2:37:09 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: my-PC
Description:
The previous system shutdown at 2:35:29 AM on 5/16/2010 was unexpected.
Event Xml:
<Event xmlns="">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-05-16T09:37:09.000000000Z" />
<EventRecordID>7131</EventRecordID>
<Channel>System</Channel>
<Computer>my-PC</Computer>
<Security />
</System>
<EventData>
<Data>2:35:29 AM</Data>
<Data>5/16/2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>623</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA07050000001000020023001D00AB00DA07050000001000090023001D00AB00600900003C000000010000006009000000000000B00400000100000000000000</Binary>
</EventData>
</Event>
Here are my system specs for those interested:
Alienware M17x-R2
Intel Core i7 920XM 2.0GHz (3.2GHz Turbo Mode, 8MB Cache)
8GB Dual Channel DDR3 at 1333MHz
Alienware M17x 240W A/C Adapter
17-inch WideUXGA 1920 x 1200 RGB LED (1200p)
Dual 1GB ATI Radeon Mobility HD 4870 in CrossfireX
500GB Raid 1 (2x 500GB 7,200RPM HDDs)
Genuine Windows 7 Ultimate, 64bit, English
Slot-Loading Dual Layer Blu-ray Burner (BR-R, DVD+-RW, CD-RW)
5.1 Channel Audio
Intel Ultimate N WiFi Link 6300 a/g/n 3x3 MIMO Technology
Bluetooth 2.1 with EDR
Thanks to anyone who may be able to provide any insight into these issues I am experiencing!
