BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

bsfinkel

New Member
I have had two recent Windows 7 Professional 32-bit 7E BSOD reboots:

09/17/2019 12:51
10/11/2019 19:32

I have full and mini dumps for both. Windbg points to volsnap.sys for both. I do not know enough about Windows internals to know what windbg commands to issue to determine what happened. Can anyone assist?

03/25/2016 01:39 PM 246,504 volsnap.sys File Version: 6.1.7601.23404

Thanks.
 

Attachments

  • W7F_12-10-2019.zip
    4.3 MB · Views: 57

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Can you open an admin command prompt and do a sfc /scannow, post any logs or output.
 

bsfinkel

New Member
I ran a "sfc /scannow", and I am not sure what I should see in the way of errors in the cbs.log file. I see (and have seen ever since I ran that command in 04/14/2014) errors in two files:

odfox32.dll
odpdx32.dll

I have attached the cbs.log file.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Are you using Paradox? If so reinstalling it should fix those errors.
 

bsfinkel

New Member
I have NEVER installed Paradox. And I am 100% sure that these two DLL errors are NOT involved in my 7E BSOD.
 

bsfinkel

New Member
I ran a "sfc /scannow", and I am not sure what I should see in the way of errors in the cbs.log file. I see (and have seen ever since I ran that command in 04/14/2014) errors in two files:

odfox32.dll
odpdx32.dll

I have attached the cbs.log file.
 

bsfinkel

New Member
I experienced another 7E BSOD today - pointing to volsnap.sys; am I to conclude that there is nothing I can do to fix whatever is the problem? Is analyziing a Windows 7 mini-dump a lost art? Or an art that only a handful of people have?
 
Top