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: maximus hero 6 bsod

18 Jun 2014   #1
exaflare

Windows 7 Ultimate x64
 
 
maximus hero 6 bsod

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 7a
BCP1: FFFFF6FC4000C798
BCP2: FFFFFFFFC000000E
BCP3: 00000001424F2860
BCP4: FFFFF880018F3CA8
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\061814-26551-01.dmp
C:\Users\Paul\AppData\Local\Temp\WER-71105-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Please help me I don't know what to do.


My System SpecsSystem Spec
.
18 Jun 2014   #2
PeregrineX

Windows 7 Ultimate X64
 
 

Hello and welcome to SevenForums!

Your BSOD seems to be caused by your DirectX Graphics MMS driver:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00bb80570
Arg3: 0000000000000001
Arg4: 0000000000002abf

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


BUGCHECK_STR:  0x10e_1f

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800704022f to fffff800032d7bc0

STACK_TEXT:  
fffff880`04446738 fffff880`0704022f : 00000000`0000010e 00000000`0000001f fffff8a0`0bb80570 00000000`00000001 : nt!KeBugCheckEx
fffff880`04446740 fffff880`105bc1d0 : fffff8a0`0bb80570 fffff8a0`0bb80570 00000000`00002abf 00000000`00000001 : watchdog!WdLogEvent5+0x11b
fffff880`04446790 fffff880`105b99d3 : 00000000`00000000 fffffa80`0927c088 00000000`00000c3a fffffa80`0927e1a0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
fffff880`044467d0 fffff880`105d37d9 : 00000000`00000000 fffff8a0`03012950 fffffa80`00000001 fffffa80`09244f10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`044469a0 fffff880`105d3514 : fffff880`037dbf40 fffff880`105d2f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04446b90 fffff880`105d3012 : 00000000`00000000 fffffa80`09272d50 00000000`00000080 fffffa80`08c0b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04446bc0 fffff800`0357373a : 00000000`099697cc fffffa80`08892a00 fffffa80`066d5230 fffffa80`08892a00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04446c00 fffff800`032c88e6 : fffff880`037d7180 fffffa80`08892a00 fffff880`037e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04446c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`105bc1d0 c7442450c5f3ffff mov     dword ptr [rsp+50h],0FFFFF3C5h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

Followup: MachineOwner
---------
Try reinstalling DirectX via the Microsoft Website, and inform us of the results.

Best of luck,

PeregrineX
My System SpecsSystem Spec
19 Jun 2014   #3
exaflare

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by PeregrineX View Post
Hello and welcome to SevenForums!

Your BSOD seems to be caused by your DirectX Graphics MMS driver:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00bb80570
Arg3: 0000000000000001
Arg4: 0000000000002abf

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


BUGCHECK_STR:  0x10e_1f

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800704022f to fffff800032d7bc0

STACK_TEXT:  
fffff880`04446738 fffff880`0704022f : 00000000`0000010e 00000000`0000001f fffff8a0`0bb80570 00000000`00000001 : nt!KeBugCheckEx
fffff880`04446740 fffff880`105bc1d0 : fffff8a0`0bb80570 fffff8a0`0bb80570 00000000`00002abf 00000000`00000001 : watchdog!WdLogEvent5+0x11b
fffff880`04446790 fffff880`105b99d3 : 00000000`00000000 fffffa80`0927c088 00000000`00000c3a fffffa80`0927e1a0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
fffff880`044467d0 fffff880`105d37d9 : 00000000`00000000 fffff8a0`03012950 fffffa80`00000001 fffffa80`09244f10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`044469a0 fffff880`105d3514 : fffff880`037dbf40 fffff880`105d2f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04446b90 fffff880`105d3012 : 00000000`00000000 fffffa80`09272d50 00000000`00000080 fffffa80`08c0b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04446bc0 fffff800`0357373a : 00000000`099697cc fffffa80`08892a00 fffffa80`066d5230 fffffa80`08892a00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04446c00 fffff800`032c88e6 : fffff880`037d7180 fffffa80`08892a00 fffff880`037e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04446c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`105bc1d0 c7442450c5f3ffff mov     dword ptr [rsp+50h],0FFFFF3C5h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

Followup: MachineOwner
---------
Try reinstalling DirectX via the Microsoft Website, and inform us of the results.

Best of luck,

PeregrineX
when i try to re-intall the installer said directx setup has determined that a newer or equivalent version of directx has been installed already.
My System SpecsSystem Spec
.

19 Jun 2014   #4
exaflare

Windows 7 Ultimate x64
 
 

i think it's happend when i sync my iphone to my pc
My System SpecsSystem Spec
19 Jun 2014   #5
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4000c798, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000001424f2860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880018f3ca8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run chkdsk. Disk Check

Uninstall DaemonTools, a known cause of BSODs.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.
My System SpecsSystem Spec
Reply

 maximus hero 6 bsod




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Maximus VI Hero or Maximus VI Formula
Maximus VI Hero or Maximus VI Formula What motherboard has more features and is most worth it I will be using 2 GPUS and overclocking the haswell i7 4770K
Hardware & Devices
Do anyone own this Motherboard MAXIMUS VI HERO
So okay in my last thread i was told this board is good.... Now be for i buy the motherboard i want people who have this board to tell me what its like in terms of quality/overclocking/gaming...... If what i have read is true about the MAXIMUS VI HERO....I'm 100% buying the MSI GD65
Hardware & Devices
Power Problem ASUS MAXIMUS FORMULA V
Just bought all new hardware for a gaming PC, The problem is when i switch my power supply on, the computer starts up and runs for about 3 seconds then shuts off. also if i reset the cmos in the back the computer will do the same thing again. note this is without me even pressing the power...
Hardware & Devices
Icy Box (IB-865) on a ASUS Maximus v Gene Board USB 3 incompatible?
Hi Everyone, I have a new motherboard (Maximus v Gene) and I've brought a Icy Box (IB-865) card reader to make use of the USB 3 connector on the motherboard. However the unit works well for a dozen reboots and then it malfunctions. After a dozen reboots the Icy Box power light no longer powers...
Hardware & Devices
Maximus Gene Motherboard Identified Component
I've got two 4 pin plugs just under the PCI Slot on my new motherboard (see attached picture) and can't find any info on what they do? Manual and online manual have no mention of these pins. Any ideas?
Hardware & Devices


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 13:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App