Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e49730
Debug session time: Mon Dec 21 13:45:52.664 2015 (UTC - 5:00)
System Uptime: 0 days 10:44:53.850
* Bugcheck Analysis *
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
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004020e2f, The address that the exception occurred at
Arg3: fffff880029be568, Exception Record Address
Arg4: fffff880029bddc0, Context Record Address
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
fffff880`04020e2f 0fba63540d bt dword ptr [rbx+54h],0Dh
EXCEPTION_RECORD: fffff880029be568 -- (.exr 0xfffff880029be568)
ExceptionAddress: fffff88004020e2f (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
ExceptionCode: c0000005 (Access violation)
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880029bddc0 -- (.cxr 0xfffff880029bddc0)
rax=fffff8a008a735e0 rbx=ddfff8a017157900 rcx=fffffa8012108000
rdx=fffffa80101ada60 rsi=fffffa8012108000 rdi=fffffa8012108000
rip=fffff88004020e2f rsp=fffff880029be7a0 rbp=fffffa800d4f9e30
r8=fffffa8013dded01 r9=0000000000000000 r10=0000000000000000
r11=00000000000000d5 r12=fffffa80101ada60 r13=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
fffff880`04020e2f 0fba63540d bt dword ptr [rbx+54h],0Dh ds:002b:ddfff8a0`17157954=????????
Resetting default scope
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb3100
GetUlongFromAddress: unable to read from fffff80002eb31c0
fffff880`04020e2f 0fba63540d bt dword ptr [rbx+54h],0Dh
LAST_CONTROL_TRANSFER: from fffff8800401dff7 to fffff88004020e2f
fffff880`029be7a0 fffff880`0401dff7 : 00000000`00000000 fffffa80`0d0a84b8 00000000`0000003e 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`029be7d0 fffff880`040387d9 : 00000000`00000000 fffff8a0`00ae0010 fffffa80`00000000 fffffa80`13ddedb0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`029be9a0 fffff880`04038514 : fffff880`03346f40 fffff880`04037f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`029beb90 fffff880`04038012 : 00000000`00000000 fffffa80`131e7d50 00000000`00000080 fffffa80`120e4410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`029bebc0 fffff800`02f0fb86 : 00000000`01d5c848 fffffa80`120aca00 fffffa80`0cd5f040 fffffa80`120aca00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`029bec00 fffff800`02c670e6 : fffff880`03342180 fffffa80`120aca00 fffff880`0334cfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`029bec40 00000000`00000000 : fffff880`029bf000 fffff880`029b9000 fffff880`029be540 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .cxr 0xfffff880029bddc0 ; kb
Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN
For more information.
Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2
(the exception address) should identify the driver or function that caused this problem.
If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
was started with the /NODEBUG
switch. This problem should rarely occur. If it occurs repeatedly,
make sure that a kernel debugger is connected and the system is started with the /DEBUG
If exception code 0x80000002 occurs, the trap frame supplies additional information.
If you do not know the specific cause of the exception, consider the following issues:
Hardware incompatibility. Make sure that any new hardware that is installed is listed in the
Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. A faulty device driver or system service might be
responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts,
and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable
or remove any drivers or services that were recently added. If the error occurs during the startup
sequence and the system partition is formatted with NTFS file system, you might be able to use Safe
Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process
in Safe Mode, you must start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote
control program. If such software is installed, you can remove the service by starting the computer
by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the
device or driver that is causing bug check 0x7E.
You can also disable memory caching of the BIOS might to try to resolve the error. You should also
run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies.
For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or
after Setup is finished. A possible cause of the error is lack of disk space for installation and system
BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk
space, reduce the number of files on the target hard disk drive. Check for and delete any temporary
files that you do not have to have, Internet cache files, application backup files, and.chkfiles that
contain saved file fragments from disk scans. You can also use another hard disk drive with more
free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.
** Memtest86+ V5.01 (27/09/2013)** CLICK HERE
< Direct Download.
Disk Check From Command Prompt.
Open up an administrator mode command prompt by searching in the Start menu or screen for “cmd” and then right-clicking on the item and choosing “Run as Administrator”. Type in the following command, substituting the drive letter if necessary.
How to Tell if an Automatic Disk Check is Scheduled