jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore May 19, 2012 #1 The _95-dbug.txt file will ultimately be used to update John Carrona's DRT. He & I do currently use the 95 file to update the DRT, but DRT Admin perms are required at this time. The _95-dbug.txt is populated with driver name, your user name and the thread URL, like this - Code: abc123.sys}}jcgriff2}http://www.sevenforums.com/crashes-debugging/230618-regular-bsod-bccode-124-after-playing-diablo-3-a.html def234.Sys}}jcgriff2}http://www.sevenforums.com/crashes-debugging/230618-regular-bsod-bccode-124-after-playing-diablo-3-a.html That is the reason you were asked for your username during the 1st run & are asked for a thread URL each time the BSOD App runs. If all 3rd party drivers in the dump run are found in the DRT, then this message appears in _95-dbug.txt - Code: 2012-05-19 06:55:12 2012-05-19 06:55:12 2012-05-19 06:55:12 ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE You can help us by pasting the _95-dbug.txt contents into this thread (create a new post) & if you have a driver description and update link, please include them as well. Please see - - _95-dbug.txt files - driver updates for DRT We plan to have an interface so you can upload the _95-dbug.txt file to a temp area for the DRT in the near future. Thanks... John Last edited: May 19, 2012
The _95-dbug.txt file will ultimately be used to update John Carrona's DRT. He & I do currently use the 95 file to update the DRT, but DRT Admin perms are required at this time. The _95-dbug.txt is populated with driver name, your user name and the thread URL, like this - Code: abc123.sys}}jcgriff2}http://www.sevenforums.com/crashes-debugging/230618-regular-bsod-bccode-124-after-playing-diablo-3-a.html def234.Sys}}jcgriff2}http://www.sevenforums.com/crashes-debugging/230618-regular-bsod-bccode-124-after-playing-diablo-3-a.html That is the reason you were asked for your username during the 1st run & are asked for a thread URL each time the BSOD App runs. If all 3rd party drivers in the dump run are found in the DRT, then this message appears in _95-dbug.txt - Code: 2012-05-19 06:55:12 2012-05-19 06:55:12 2012-05-19 06:55:12 ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE ALL 3rd PARTY DRIVERS WERE FOUND IN THE TABLE You can help us by pasting the _95-dbug.txt contents into this thread (create a new post) & if you have a driver description and update link, please include them as well. Please see - - _95-dbug.txt files - driver updates for DRT We plan to have an interface so you can upload the _95-dbug.txt file to a temp area for the DRT in the near future. Thanks... John
zigzag3143 Contributor, Sysnative Staff Emeritus Joined Mar 27, 2012 Posts 3,741 May 19, 2012 #2 Thanks for the explanation
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore May 19, 2012 #3 My pleasure, Ken. We're trying to get the functionality explanations out as questions come up & as time permits!
My pleasure, Ken. We're trying to get the functionality explanations out as questions come up & as time permits!
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore May 19, 2012 #4 The thread for 95 driver updates - Please see - - _95-dbug.txt files - driver updates for DRT