New
#1
Persistent Stop Error 1000007e
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.