Click here to Skip to main content
15,894,825 members
Please Sign up or sign in to vote.
1.50/5 (2 votes)
See more:
I have an application I created in VB, I have over 40 revisions used at our facility and in the field.
All of a sudden in the past month or so, it has started to blue screen windows xp machines when you exit the application.
It seems that it only happens when you have used the application for more than 1 operation on USB, but that could just be a red herring.
I am not sure how to proceed with debugging, since it is happening in our facility and outside, I believe it has something to do with a microsoft update.
Any ideas?
Martin
Posted
Comments
Sergey Alexandrovich Kryukov 12-Nov-13 16:43pm    
That sounds scary. Not only that application is bad, but it looks like the OS has a security hole, at least one. :-)
Anyway, it does not provide enough information to get to this problem, not even close.
—SA
Maciej Los 12-Nov-13 17:01pm    
Agree!
Member 10282815 12-Nov-13 17:11pm    
how can I provide more info??? This has been working fine for a long time, I pulled code out of CVS that has been in the field for a long time in hopes that it was a change I made but it does the same thing. Any ideas?
Sergey Alexandrovich Kryukov 12-Nov-13 17:17pm    
If even you don't know how to provide more information, how anyone else could know better? People never saw you system. Try to get a new system and follow the advice of Solution 1, maybe you eventually can spot something...
—SA

Best advice I can give is to set up an XP virtual machine and start applying updates one at a time (or apply all of them and start un-applying in order of date, but this is much more difficult). After each update, run your application through a test that makes it blue screen on your machines, when you find the update that makes it crash, you have your culprit.

After that, you will have to dig into the MSDN and see what changed, that can help you narrow down a resolution.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 12-Nov-13 17:18pm    
Pretty good idea, my 5. However, it may or may not work. Besides, I feel that OP may not have enough qualification for that, looking at the last comment to the question...
—SA
Ron Beyer 12-Nov-13 20:09pm    
Thanks Sergey.
I understand how this can be frustrating to read, but this is suddenly happening on lots of PC's in my building not in my building, at customer sites......
I can look at a the event viewer and can see that the events are

CSS
BCCode : 1000007e     BCP1 : C0000005     BCP2 : 00500000     BCP3 : BA507A38
BCP4 : BA507734     OSVer : 5_1_2600     SP : 3_0     Product : 256_1

Error code 1000007e, parameter1 c0000005, parameter2 00500000, parameter3 ba507a38, parameter4 ba507734.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Maybe this will provide some insight
 
Share this answer
 
I went through the code putting in exit sub lines until I got to the problem it seems that for some reason if I now call unload form on the same form twice, xp blue screens.
I can see why it my cause an error but to blue screen is pretty interesting.
 
Share this answer
 
Comments
CHill60 14-Nov-13 16:18pm    
Please stop posting comments as solutions to your own post. Use the Improve question link to add details to the question or use the Reply link next to the solution posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900