YvesDaoust

New Member
Joined
Feb 7, 2014
Messages
2
Sine a few days I experience annoying BSOD while compiling with Visual Studio 2003. My system and compiler have been running fine for 2 years or so and I made no recent changes (other than a few auto-updates of different software's). The crash occurs immediately after I press the Build Solution button (so far it occurred 3 times in the same conditions, so I don't believe in a coincidence; the event is rare as I am doing tenths of compilations a day).

My question is: how can I troubleshoot this most effectively, without trying random repairs (disk check, VS reinstallation, Windows restore, painful crash dump analysis...) and spend 3 frustrating days on the issue ?
 


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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a004f1f8c0, fffff8a004f1f940, 5080217}

*** WARNING: Unable to verify timestamp for PROCEXP152.SYS
*** ERROR: Module load completed but symbols could not be loaded for PROCEXP152.SYS
Probably caused by : PROCEXP152.SYS ( PROCEXP152+17e3 )

Followup: MachineOwner...
Hi,
Ill certainly have a look at your dump file but as to making this an easier process why not try forums to do with Visual Studio 2003? Anyhoo if you would like me to have a look please read this thread and post the results
Link Removed

Edit:
I just did a little googling and perhaps this might give you some ideas:
Link Removed
 


Thank you for the proposal. I have now uploaded the W7F files.

I read in the post you mention that interference with antivirus programs is possible. I indeed have two of them running, shame on me (Windows Defender + AVG). Is it possible to confirm this hypothesis from the dump ? How can such an interference cause a blue screen ?

By the way, it makes sense that the crash occurs when pressing the compile button: the first action on that moment is the flushing of modified files to disk. And I assume that these file modifications are monitored by the anti-virus programs, possibly creating some deadly race condition.
 


Attachments

Last edited:
Hi,
AVG is known to cause issues on occasion and I would suggest using Defender and Malwarebytes as these do not conflict. I'll post again once I've debugged the file (shortly).
 


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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a004f1f8c0, fffff8a004f1f940, 5080217}

*** WARNING: Unable to verify timestamp for PROCEXP152.SYS
*** ERROR: Module load completed but symbols could not be loaded for PROCEXP152.SYS
Probably caused by : PROCEXP152.SYS ( PROCEXP152+17e3 )

Followup: MachineOwner

Hi,
all the dump files sent were of the same issue and Process Explorer is cited as the culprit. Either try uninstalling or updating:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

I found your AVG files in the driver stack and as above please remove and install either Defender/MSE:
Link Removed

I checked through your drivers and whilst most are re 2013 your manufacturer hasn't any later updates:
Link Removed

Try making the changes outlined and we'll go from there. Please post any further dmp files.
 


Solution
Back
Top