Recent content by bsfinkel

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?

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.

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

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.

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...

I had another similar BSOD Friday night while MSE was doing a full scan. Is there any more information that can be gathered from the mini-dump I submitted to help me determine what is happening? I believe that there is a bug in ntfs.sys, but I do not have enough knowledge of the internals of...

In the windbg - mindump 071319-63109-01.dmp - I did !analyze -f -v d esp-1000 esp+1000 And the display begins at address b2c01f38. In the windbg - full dump memory.190713.0211.dmp (which I renamed from memory.dmp) - I did !analyze -f -v d esp-1000 esp+1000 The display...

Is there any command I have to run before the "d esp-1000 esp+1000 " command? I ran that command in windbg on both the minidump and full dump from last weekend, and I do not get the text above. Your output begins at a5803e68 , mine starts at b2c01fe8. And I get different output in the...

I did an "sfc /scannow", and I am not sure what are the error lines. What I see now (and what I have seen ssince my first run of this command years ago) is "Cannot repair member file [l:22{11}]"odfox32.dll of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ODBC-Jet ...", and the same...

Here is more detail on my NTFS BSODs. I have a SATA disk as my C-drive, andI get lots of EventID 55 (NTFS) in the System Log. That EventId says that the C-drive is corrupt and needs a chkdsk. Windows schedules and runs a 12-minute "chkdsk c:" at reboot, and it always says "no problems found"...

I am seeing multiple NTFS BSOD (24) occurrences on my Windows 7 Professional 32-bit system. I have many mini-dumps and full dumps. Is there anyone on this forum who has experience with these and can assist in determining what is happening? What documentation do you need? Thanks.