Question
Applies to
1921 views

BSOD: BCCode: 1000007e

mike_krantz asked on
Hello, my computer i built earlier this year has been having the BSOD now for quite awhile, and I can't seem to find the fix. 
First off, here are my specs:
OS: windows 7
PSU: SeaSonic M12II 620 Bronze 620W ATX12V
CPU Intel Core i5-4670K 3.4GHz Quad-Core
Motherboard Asus Z87-PRO ATX LGA1150
Storage Samsung 840 Series 120GB 2.5" SSD
Western Digital Caviar Black 1TB 3.5" 7200RPM
Video Card Gigabyte Radeon HD 7970 3GB
Memory          G.SKILL Ripjaws X Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600

I usually get the bsod while playing video games, however, often times instead of the bsod the game will crash and a bubble pops up saying "Display driver stopped responding and has recovered". this problem started after I caught my niece playing with the power button and the reset button on my case.

Troubleshooting I have done so far:
Update drivers
tested my harddrives
memtest 86 over two nights, no errors found
restored computer
uninstalled/reinstall windows.
swap gpus
monitor temperatures(everything normal)

Not sure what else the problem could be, any ideas are greatly appreciated as this is really starting to frustrate me.

Minidump link: http://sdrv.ms/1ctKlMw

2 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi,

The attached DMP file is of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bug check.

This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff88005542b3f, fffff88002eb5258, fffff88002eb4ab0}

The 1st parameter of the bug check is 0xc0000005 which indicates that an access violation occurred, let's see what caused it:

1: kd> .exr 0xfffff88002eb5258
ExceptionAddress: fffff88005542b3f (dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0x000000000000002f)
ExceptionCode: c0000005 (Access violation)


It was caused by a Direct X MMS function call.

If we take a look at the call stack:

1: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff880`0553e8c7 : 00000000`00180101 00000000`00000000 00000000`00000000 fffff8a0`207f4ae0 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0x2f
fffff880`0553e85e : fffff8a0`1e563e50 fffff8a0`00180101 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x37
fffff880`05530568 : fffff8a0`1e563e50 fffff880`0553d469 fffffa80`10921000 fffff8a0`1e563e50 : dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0x216
fffff8a0`1e563e50 : fffff880`0553d469 fffffa80`10921000 fffff8a0`1e563e50 00000000`00000000 : dxgmms1!gVidMmPolicyTable+0x108
fffff880`0553d469 : fffffa80`10921000 fffff8a0`1e563e50 00000000`00000000 00000000`00000000 : 0xfffff8a0`1e563e50
fffff880`0553a3a0 : 00000000`0000009b 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x215
fffff880`055547d9 : 00000000`00000000 fffff8a0`1d251db0 fffffa80`00000000 fffffa80`0cceb630 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x7e8
fffff880`05554514 : fffff880`009c4f40 fffff880`05553f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05554012 : 00000000`00000000 fffffa80`179fd2d0 00000000`00000080 fffffa80`0f17a010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff800`037702ea : 00000000`020c1480 fffffa80`0f17bb50 fffffa80`0c74f990 fffffa80`0f17bb50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff800`034c48e6 : fffff880`009c0180 fffffa80`0f17bb50 fffff880`009cafc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`02eb6000 fffff880`02eb0000 fffff880`02eb5540 00000000`00000000 : nt!KiStartSystemThread+0x16


We can see we have many Direct X MMS calls.

-------------------------------------------------------

1. I can see in your loaded modules list you have various problematic Asus bloatware installed (Charger driver, etc). It's all bundled into the AI Suite. Please uninstall the Asus AI Suite ASAP.

2. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes as Norton may be causing corruption:

Norton removal tool - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

3. Do you have Asus Smartdoctor installed?

IOMap64.sys - Thu Feb 04 20:55:34 2010

^^ This is usually a driver associated with Smartdoctor. If you DO have it installed, remove it ASAP as it's very likely causing the Direct X MMS conflicts we are seeing. If you are using it, what were you using it for? Monitoring temps, voltages? I hope not overclocking.

4. Ensure your SSD's firmware is 100% up to date via the manufacturers website.

---------------------------------------------

If you're still crashing after all of my above recommendations, please enable Driver Verifier to see if we're dealing with any further device driver corruption:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617

Regards,

Patrick
Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress