Persistent Stop Error 1000007e

chris1981l · 11 Jan 2010

Hello! Usually I get all the help I need reading others' posts, but this one has me baffled.

I have a persistent stop error on a new (1 month old) laptop that occurs:

running "graphics intensive" programs (COD4, Warcraft 3)
running firefox on an external monitor via HDMI
when randomly running the furmark graphics utility

It is not generally immediately repeatable, and happens anywhere from 3 minutes to 3 hours into any of the above operations. It has been happening since I received the computer.

I have tried the following solutions:

isolating the memory/processor by running stress tests
isolating the graphics card by running benchmarking software
isolating the hard disk using a disk check utility for SSD
run preboot diagnostics
spent 17 hours (I started the tally after the first call of 3 hours) on the phone with dell tech support
reinstalled the operating system/reformatted the hard disk (twice)
on one reinstall used the drivers from the device manufacturers, on the other, used the drivers from support.dell.com (both yielded the same result)
flashed bios

I am running:
Windows 7 Ultimate 64 bit
Intel Core 2 Extreme Q9300 @ 2.53
8 GB RAM
NVIDIA Board
Dual ATI Mobility Radeon HD 4870 cards
256 GB SSD Hard Disk (Samsung)
Dell/Alienware M17x

All drivers are now up to date from support.dell.com

Here's the bluescreen:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002F17E89
BCP3: FFFFF880009A9998
BCP4: FFFFF880009A91F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I have attached the latest minidump file. Any assistance would be greatly appreciated! Dell seems convinced it's a video card problem (and wants to replace both). I am not sure - the random-ness of it makes me think RAM or even bad sectors in the hard drive (both of which were "disproven" by the check disk utility and the RAM/CPU stress test.

I saw an article from microsoft support (after following a link from aumha.org/a/stop saying my stop error was related to a "timing issue" in XP and that a patch was issued. Could there be another timing issue with windows 7? Unfortunately I have not found a comparable guide to stop messages for windows 7.

Again, thanks very much for bearing with me, I appreciate any feedback.

zigzag3143 · 11 Jan 2010

chris1981l said:

Hello! Usually I get all the help I need reading others' posts, but this one has me baffled.

I have a persistent stop error on a new (1 month old) laptop that occurs:

running "graphics intensive" programs (COD4, Warcraft 3)
running firefox on an external monitor via HDMI
when randomly running the furmark graphics utility

It is not generally immediately repeatable, and happens anywhere from 3 minutes to 3 hours into any of the above operations. It has been happening since I received the computer.

I have tried the following solutions:

isolating the memory/processor by running stress tests
isolating the graphics card by running benchmarking software
isolating the hard disk using a disk check utility for SSD
run preboot diagnostics
spent 17 hours (I started the tally after the first call of 3 hours) on the phone with dell tech support
reinstalled the operating system/reformatted the hard disk (twice)
on one reinstall used the drivers from the device manufacturers, on the other, used the drivers from support.dell.com (both yielded the same result)
flashed bios

I am running:
Windows 7 Ultimate 64 bit
Intel Core 2 Extreme Q9300 @ 2.53
8 GB RAM
NVIDIA Board
Dual ATI Mobility Radeon HD 4870 cards
256 GB SSD Hard Disk (Samsung)
Dell/Alienware M17x

All drivers are now up to date from support.dell.com

Here's the bluescreen:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002F17E89
BCP3: FFFFF880009A9998
BCP4: FFFFF880009A91F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I have attached the latest minidump file. Any assistance would be greatly appreciated! Dell seems convinced it's a video card problem (and wants to replace both). I am not sure - the random-ness of it makes me think RAM or even bad sectors in the hard drive (both of which were "disproven" by the check disk utility and the RAM/CPU stress test.

I saw an article from microsoft support (after following a link from aumha.org/a/stop saying my stop error was related to a "timing issue" in XP and that a patch was issued. Could there be another timing issue with windows 7? Unfortunately I have not found a comparable guide to stop messages for windows 7.

Again, thanks very much for bearing with me, I appreciate any feedback.

Hi chris and welcome

You nailed it. this crash was caused by memory corruption

I would download memtestx86 and run it for 5 passes to see if it is the memory or maybe a heat issue

Also run a system file check
type cmd in search>right click and run as admin>sfc /scannow

Let us know the resuts

Ken J+

Code:

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


Loading Dump File [C:\Users\K\Desktop\011010-13993-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`0309ce50
Debug session time: Sun Jan 10 19:39:49.954 2010 (GMT-5)
System Uptime: 0 days 0:08:49.640
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002f17e89, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f17e89, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MmZeroPageThread+3d4
fffff800`02f17e89 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002f17e89 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=000000000000000c rbx=ffffefffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8007200be0 rdi=000000000000000c
rip=fffff80002f17e89 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000000 r13=fffcfa7fffffffd0
r14=0000000000000040 r15=fffff80002e5f000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!MmZeroPageThread+0x3d4:
fffff800`02f17e89 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:fffcfa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031070e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`02f17e89 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003174166 to fffff80002f17e89

STACK_TEXT:  
fffff880`009a9bd0 fffff800`03174166 : fffffa80`073255b0 00000000`00000080 fffffa80`07325b30 fffff800`02eaf479 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`02eaf486 : fffff800`03049e80 fffffa80`073255b0 fffff800`03057c40 2a032a4f`201fca94 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

chris1981l · 11 Jan 2010

thanks Ken!

When I get home tonight with the system I will run those tests and post results. I appreciate you taking time to look at the dump - dell tech support wanted to ignore the dump and focus on the stop error (which they said was video related).

chris1981l · 11 Jan 2010

Ken,

You are a prince among men. I ran memtest86, and about an hour and change in on the second pass, came up with two errors. It's still taken about an hour with the dell representative to get them to send two new sticks...but it seems they are about there (if anyone else ends up dealing with dell, take a picture of the errors so you can document...fortunately I did as a second thought before rebooting).

It looks like they are still going to replace the video cards - I'm not complaining.

Thanks again, I wish I could do more than click on the scales.