Several BSOD's on brand new PC, any help appreciated!

Palenque · 29 Mar 2010

Hi everyone,

Since one week I own a brand new PC with Windows 7, bought it from Dell so everything was 'pre-made'. (Studio XPS) Unfortunately, there have been some BSOD's on various moments with different kinds of programs. I don't know what causes this, could anyone take a look at the dump files?

Many thanks in advance....!

Jonathan_King · 29 Mar 2010

Welcome!

I wonder if you have bad RAM in that machine. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

In addition, you may want to do a system files check. Open an elevated command prompt and enter sfc /scannow.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\032210-15366-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Mon Mar 22 04:41:11.847 2010 (GMT-4)
System Uptime: 0 days 0:00:08.971
Loading Kernel Symbols
...............................................................
...........
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002ae3be6}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ae3be6

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ac9469 to fffff80002ac9f00

STACK_TEXT:  
fffff880`009f6de8 fffff800`02ac9469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f6df0 fffff800`02ac7932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f6f30 fffff800`02ae3be6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03941000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x6


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80002ac9d03-fffff80002ac9d3b)
fffff80002ac9d00  01  00  00 *b7  8b  ac  24  90  01  00  00 *21  8b  b4  24  98 ......$....!..$.
fffff80002ac9d10  01  00  00 *00  83  c4  68  e9  a4  f9  ff *6b  fb  48  8b  44 ......h....k.H.D
fffff80002ac9d20  24  40  0f *00  08  e8  c6  ec  0b  00  65 *bb  ae  14  25  80 $@........e...%.
fffff80002ac9d30  01  00  00 *5c  8d  44  24  70  49  8b  08 *bc  8b  50  08  4c ...\.D$pI....P.L

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Franck · 29 Mar 2010

if it indeed is the RAM-memory try switching places on the memory sticks, somehow Win 7 doesn't really like the dual channeling on some motherboards. I had a similar problem a while back and that solved it for me.