Win7pro 64bit shutdown issue

Found a bug in "Everything"? report it here
Post Reply
JohnGaltJr
Posts: 2
Joined: Wed Mar 20, 2013 12:03 pm

Win7pro 64bit shutdown issue

Post by JohnGaltJr » Wed Mar 20, 2013 1:30 pm

I have a new pc with Windows7 pro 64bit.
The antivirus is Kaspersky Endpoint Security 10 for Windows 10.1.0.867

I've installed Everything-1.3.1.636b.exe and it worked fine for some days.

Then I've started getting problem at the shutdown: bsod with error 0x76. As suggested by Microsft
http://support.microsoft.com/kb/256010/en-us I set the TrackLockedPages value to 1.
So I discovered that the driver involved is NTFS.SYS

I'm pretty sure that the problem was caused by Everything because if Everything is closed I don't get the bosd.
And I get the same bluescreen (most of the times) when I close Everything manually (right mouse over the traybar icon > exit).

I uninstalled Everything beta and that errors stopped.


Now I've tried installing Everything-1.2.1.371.exe and I still get the bsod at shutdown

Errorlog.txt only contains:

Code: Select all

19/03/2013 15:31:00: Everything 1.2.1.371: .\src\db.cpp(4411): db::_load(): if (40566824 + 41468869 + 4 > 42663976): Invalid folder offset.

Code: Select all

Problem signature:
 Problem Event Name: BlueScreen
 OS Version:	6.1.7601.2.1.0.256.48
 Locale ID: 	1040

  BCCode:	cb
  BCP1:	FFFFF88001E20583
  BCP2:	0000000000000000
  BCP3:	FFFFFA8006AE6180
  BCP4:	000000000000021C
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Code: Select all

 On Wed 20/03/2013 12:09:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF88001E20583) 
Bugcheck code: 0xCB (0xFFFFF88001E20583, 0x0, 0xFFFFFA8006AE6180, 0x21C)
Error: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT

On Wed 20/03/2013 09:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032013-24804-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x13583) 
Bugcheck code: 0xCB (0xFFFFF88001E5E583, 0x0, 0xFFFFFA800667D2B0, 0x3760)
Error: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT

On Tue 19/03/2013 20:18:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-29374-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x13583) 
Bugcheck code: 0xCB (0xFFFFF88001E5F583, 0x0, 0xFFFFFA80066A0A70, 0x18C0)
Error: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT

The antivirus is Kaspersky Endpoint Security 10 for Windows 10.1.0.867

Any advice?

Thanks

void
Site Admin
Posts: 4968
Joined: Fri Oct 16, 2009 11:31 pm

Re: Win7pro 64bit shutdown issue

Post by void » Thu Mar 21, 2013 4:52 am

Thanks for the bug report.

Does the problem occur if you disable monitoring on all drives?

To disable monitoring on all drives:
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab.
  • For each volume:
  • Uncheck Monitor changes.
  • Click OK.

JohnGaltJr
Posts: 2
Joined: Wed Mar 20, 2013 12:03 pm

Re: Win7pro 64bit shutdown issue

Post by JohnGaltJr » Thu Mar 21, 2013 11:34 pm

void wrote: Does the problem occur if you disable monitoring on all drives?
Thanks for the quick response (and for your great application, of course)!

Disabling monitoring the problem doesn't occur anymore. Is it possible to force the database update manually?

Thanks again

void
Site Admin
Posts: 4968
Joined: Fri Oct 16, 2009 11:31 pm

Re: Win7pro 64bit shutdown issue

Post by void » Thu Mar 21, 2013 11:38 pm

To force Everything to rebuild it's database:
  • Exit Everything.
  • Delete your Everything.db file in your Everything installation folder.
  • Restart Everything.

Post Reply