BSOD only in VS2012 - by Rudolf du Toit

Status : 


Sign in
to vote
ID 759832 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 8/27/2012 12:25:35 PM
Access Restriction Public


Running VS2012 Premium on Win7 SP1 Ultimate 64 on Intel 520 SSD.

- No issues at all in Win 7, system running fine without problems.
- Get a BSOD randomly in VS2012 followed by automatic reboot.
- Crash dump file shows win7 driver issue in process devenv.exe

Here is the crash dump contents:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Administrator\Desktop\081812-23868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: srv*
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0ec58000 PsLoadedModuleList = 0xfffff800`0ee9c670
Debug session time: Sat Aug 18 11:13:38.143 2012 (UTC + 2:00)
System Uptime: 0 days 0:32:37.859
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1, {77a5148a, 0, 73, fffff88008ca0b60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arg1: 0000000077a5148a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000073, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff88008ca0b60, Call type (0 - system call, 1 - worker routine)

Debugging Details:

00000000`77a5148a ??              ???




PROCESS_NAME:  devenv.exe


LAST_CONTROL_TRANSFER:  from fffff8000ecd6769 to fffff8000ecd71c0

fffff880`08ca0928 fffff800`0ecd6769 : 00000000`00000001 00000000`77a5148a 00000000`00000000 00000000`00000073 : nt!KeBugCheckEx
fffff880`08ca0930 fffff800`0ecd66a0 : fffffa80`0a718820 00000000`001adcc8 00000000`00000002 00000000`000a36d0 : nt!KiBugCheckDispatch+0x69
fffff880`08ca0a70 00000000`77a5148a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`001adca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a5148a


fffff800`0ecd66a0 4883ec50        sub     rsp,50h


SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_14_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_14_nt!KiSystemServiceExit+245

Followup: MachineOwner

Sign in to post a comment.
Posted by Ala [MSFT] on 2/21/2013 at 10:52 PM
Thanks for your feedback. Using Visual Studio 2012 RTM and after following your instructions, we are unable to reproduce this issue internally, so we have no choice but to resolve this bug as Not Repro.

We however suspect that the problem might be graphics driver related. Please try to update the driver - if the problem persists, please reactivate or create a new Connect bug with the relevant steps.

Thank you,
Language Experience Team
Posted by Helen [MSFT] on 8/29/2012 at 12:57 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Rudolf du Toit on 8/28/2012 at 12:10 PM
I was able to reproduce the problem. Added the details in the feedback form.

Also, I uploaded the feedback zip file as you requested.
It contains:
- zipped the mini dump file
- 1001 log messages as you requested
- a WMV file of how I reproduce the BSOD. I can reproduce it EVERY time.

As you see I added the minidump. The memory.dmp is 700MB. Would you prefer that?
Posted by Helen [MSFT] on 8/27/2012 at 9:07 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.
It may help if you provide us with Bucket ID, a dump file and call stack.

Bucket ID:
1.    Open Event Viewer        
2.    Click on Windows Logs -> Application
3.    Search for a 1001 event that occurred soon after you encountered the crash
4.    The bucket ID should be available in the event details
(there may be multiple 1001 events for any given crash - only one will have the bucket ID)
Dump File and Callstack:
You can get detailed steps about how to get the dump file and call stack at

Please zip the file and use "FeedbackID-759832" as prefix of the file name.

You can use the following workspace to upload the file:
Password is zmlD2P*CSh!182

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team
Posted by Helen [MSFT] on 8/27/2012 at 12:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(