bsfinkel

New Member
Joined
Jul 16, 2019
Messages
11
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

nmsuk

Essential Member
Joined
Sep 7, 2009
Messages
4,329
Can you open an admin command prompt and do a sfc /scannow, post any logs or output.
 

Solution

bsfinkel

New Member
Joined
Jul 16, 2019
Messages
11
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

Essential Member
Joined
Sep 7, 2009
Messages
4,329
Are you using Paradox? If so reinstalling it should fix those errors.
 

bsfinkel

New Member
Joined
Jul 16, 2019
Messages
11
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
Joined
Jul 16, 2019
Messages
11
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
Joined
Jul 16, 2019
Messages
11
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?