Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Playing Warframe, error 1000007e

08 Jun 2013   #1
MrGrae

Windows 7 Home Premium x64
 
 
BSOD Playing Warframe, error 1000007e

I keep bluescreening while playing Warframe, nothing else at all, just Warframe.
I have in the last 24 hours rebuilt and reinstalled EVERYTHING from the ground up, still happens.

Windows automatic details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88002DCEE26
BCP3: FFFFF880057E1568
BCP4: FFFFF880057E0DC0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

EDIT My mistake, the folder was saved to the other hard drive, reuploaded the correct one.


My System SpecsSystem Spec
.
08 Jun 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Re-execute the SF Diag tool and post it following the Blue Screen of Death (BSOD) Posting Instructions. The zip you uploaded contains a desktop.ini file only.
My System SpecsSystem Spec
13 Jun 2013   #3
MrGrae

Windows 7 Home Premium x64
 
 

There you go Arc, that should be it.
My System SpecsSystem Spec
.

13 Jun 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Display is problematic here, as it is failing.
Code:
fffff880`05dde848  fffff880`044cfacbUnable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x42acb
And you are using a BETA of display driver.
Code:
fffff880`0448d000 fffff880`04527000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri May 24 01:25:28 2013 (519E7430)
    CheckSum:         0009C5C2
    ImageSize:        0009A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
You need to install the latest WHQL only, not a BETA.

Uninstall the display driver using AMD Catalyst Un-install Utility .

Update your ATI/AMD display driver to the latest WHQL, Release Date: April 24th 2013, Version: 13.4.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Let us know the results.
My System SpecsSystem Spec
14 Jun 2013   #5
MrGrae

Windows 7 Home Premium x64
 
 

Thanks Arc, never had problems with the beta drivers before but I've reset it and will let you know what happens.
My System SpecsSystem Spec
14 Jun 2013   #6
MrGrae

Windows 7 Home Premium x64
 
 

After resetting my drivers to the 13.4 version, I BSOD'd after about 20 minutes, here is the Kernel dump.
My System SpecsSystem Spec
15 Jun 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

A very little free space left there in C drive.

ITEMVALUE
Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 59.40 GB (63,782,776,832 bytes)
Free Space 7.53 GB (8,079,966,208 bytes)

Follow it: Hard Disk Space - Free Up and Recover

Make it sure that the the Crucial M4-CT064M4SSD2 is running with the latest firmware.
Crucial.com Product Downloads - Firmware Updates

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
_____________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800456012b, fffff88005b95558, fffff88005b94db0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )

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: fffff8800456012b, The address that the exception occurred at
Arg3: fffff88005b95558, Exception Record Address
Arg4: fffff88005b94db0, 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: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0456012b 48894108        mov     qword ptr [rcx+8],rax

EXCEPTION_RECORD:  fffff88005b95558 -- (.exr 0xfffff88005b95558)
ExceptionAddress: fffff8800456012b (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88005b94db0 -- (.cxr 0xfffff88005b94db0)
rax=fffffa800da07e90 rbx=fffff8a00ff57c90 rcx=ff00fa800ff9c510
rdx=fffff8a00c0032d0 rsi=fffffa800fff4010 rdi=fffffa800edef000
rip=fffff8800456012b rsp=fffff88005b95790 rbp=0000000000000000
 r8=fffffa800fff4060  r9=0000000000000001 r10=0000000000000000
r11=fffffa800edf03f0 r12=0000000000000066 r13=0000000000000000
r14=fffffa800dfa2910 r15=00000000000000ef
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`0456012b 48894108        mov     qword ptr [rcx+8],rax ds:002b:ff00fa80`0ff9c518=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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 fffff80003508100
GetUlongFromAddress: unable to read from fffff800035081c0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0456012b 48894108        mov     qword ptr [rcx+8],rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800455d9d3 to fffff8800456012b

STACK_TEXT:  
fffff880`05b95790 fffff880`0455d9d3 : 00000000`00000000 fffffa80`11f60330 00000000`000000ed fffffa80`11f65998 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`05b957d0 fffff880`045777d9 : 00000000`00000000 fffff8a0`0c85ea40 fffffa80`00000000 fffffa80`0dfa2910 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`05b959a0 fffff880`04577514 : fffff880`030a9fc0 fffff880`04576f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05b95b90 fffff880`04577012 : 00000000`00000000 fffffa80`10b5cac0 00000000`00000080 fffffa80`0ed25410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05b95bc0 fffff800`0356eede : 00000000`033e399b fffffa80`0e9ddb50 fffffa80`0d2f5890 fffffa80`0e9ddb50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05b95c00 fffff800`032c1906 : fffff880`030a5180 fffffa80`0e9ddb50 fffff880`030b0040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05b95c40 00000000`00000000 : fffff880`05b96000 fffff880`05b90000 fffff880`05b95540 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff88005b94db0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

Followup: MachineOwner
---------
My System SpecsSystem Spec
15 Jun 2013   #8
MrGrae

Windows 7 Home Premium x64
 
 

I know the SSD is low on space, believe it or not half of the used space is just Windows 7 crap. The rest is systems software, drivers, etc.

Updated the firmware as you said though.

Ran the stress test, 35 minutes running, no artifacts and temperature peaked at 93 degrees Celsius for the last 10 minutes. Abismal 8FPS, GPU usage 99%, fan usage 88% and that's all the information the burn test provided thus far.
My System SpecsSystem Spec
15 Jun 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

A 7E BSOD and its varients are mostly caused for the low disc space. See the first cause listed here: BSOD Index

93 degrees are kinda high. You need to plan for additional cooling. Is the computer running hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
My System SpecsSystem Spec
15 Jun 2013   #10
MrGrae

Windows 7 Home Premium x64
 
 

Is it? Though it's just the OS and system software on the SSD, I can't do anything to shrink it, installing windows took nearly 30GB alone.

Yes, I know it gets a bit hot, it's sitting in the enclosed footwell of my desk at the moment, I plan to adjust my setup and introduce another case fan to promote a through-draft. At the moment, after gaming for a few hours the average GPU tempurature is about 53-56 degrees, it rarely gets any higher than that.

My System SpecsSystem Spec
Reply

 BSOD Playing Warframe, error 1000007e




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD playing Neverwinter, Warframe, etc. BCCode: 1000007e
So basically to say I've been rebooted alot while playing Neverwinter and Warframe and I recieve this message every time. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 1000007e ...
BSOD Help and Support
BSOD Playing LoL and while just using Chrome, error 1000007e
Hey, I have been getting BSOD for a few months now. I have tried making sure my drivers are all up to date and that windows is updated. I have used the ESET Online scanner and it didnt find any viruses. The BSOD happen most often while playing League of Legends, but they have happened while just...
BSOD Help and Support
BSOD playing wow/skyping, error 1000007e.
Recently built a new computer passed 24 hours of prime 95 however today I got this BSOD. Requested files attached below. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional information about the problem: BCCode: 1000007e ...
BSOD Help and Support
BSOD playing Guild Wars 2, error 1000007e
Hello here, I've been playing GW2 for 15 days and some crashes occured (1 or 2 in a day) I paste the error message: Signature du problème : Nom d’événement de problème: BlueScreen Version du système: 6.1.7601.2.1.0.256.1 Identificateur de paramètres régionaux: 1036
BSOD Help and Support
BSOD playing Vindictus, error 1000007e
I was playing Vindictus when my screen tore apart and made a BSOD. When I turned my pc back on I got these additional info. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode:...
BSOD Help and Support
BSOD playing Assassins,error 1000007e
Hi, can anyone help me please? this is the error I get everyday one or two times a day for the past week now. I have a HP Pavilion dv9000 with Windows 7 on it for about one year with no problems until now. I have know idea what the problem could be, does anyone know what it could be? thanks in...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 06:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App