• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

Kudos1 Stats

PerfectDisk Build 64 fixes NIS 2009 conflict

Yesterday, Raxco issued Build 64 for PerfectDisk 2008.  It appears to have fixed the conflict for boot time defrag that NIS 2009 encountered, resulting in BSOD. 
1) Windows 10 x64 Pro on ASUS Maximus VIII Extreme motherboard, i7-6700k CPU, 64 gbyte RipJaws DDR4 3200 RAM, Samsung 970 Pro 512 gbyte SSD + Samsung 850 Pro 512 gbyte SSD, EVGA Nvidia GeForce 980 Ti graphics (Home Built System); 2) Windows 10 x64 Pro on Dell 8700 SE desktop, Intel i7 4770 CPU, 24 gbyte RAM, Dual Samsung 850 Pro 256 gbyte SSDs, EVGA Nvidia GeForce 750 Ti graphics; 3) Windows 10 x64 Pro on Dell XPS 15 2in1 laptop/tablet, Intel i7 Kasby Lake 3.0 ghertz, 16 gigabyte ram. ASUS RT-AC68r router, 8 tbyte WD My Cloud PR2100 NAS drive, 200 mbps cable Internet, Google Chrome, MS Office 2019 (Local), Casper 10, DisplayFusion (3 Flat Panel Displays per system) Norton Security Deluxe, Malwarebytes 3, SpywareBlaster, HostsMan, Quicken, Weather Watcher Live, ThumbsPlus and many more (all latest versions).

Replies

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Yesterday, Raxco issued Build 64 for PerfectDisk 2008.  It appears to have fixed the conflict for boot time defrag that NIS 2009 encountered, resulting in BSOD. 
1) Windows 10 x64 Pro on ASUS Maximus VIII Extreme motherboard, i7-6700k CPU, 64 gbyte RipJaws DDR4 3200 RAM, Samsung 970 Pro 512 gbyte SSD + Samsung 850 Pro 512 gbyte SSD, EVGA Nvidia GeForce 980 Ti graphics (Home Built System); 2) Windows 10 x64 Pro on Dell 8700 SE desktop, Intel i7 4770 CPU, 24 gbyte RAM, Dual Samsung 850 Pro 256 gbyte SSDs, EVGA Nvidia GeForce 750 Ti graphics; 3) Windows 10 x64 Pro on Dell XPS 15 2in1 laptop/tablet, Intel i7 Kasby Lake 3.0 ghertz, 16 gigabyte ram. ASUS RT-AC68r router, 8 tbyte WD My Cloud PR2100 NAS drive, 200 mbps cable Internet, Google Chrome, MS Office 2019 (Local), Casper 10, DisplayFusion (3 Flat Panel Displays per system) Norton Security Deluxe, Malwarebytes 3, SpywareBlaster, HostsMan, Quicken, Weather Watcher Live, ThumbsPlus and many more (all latest versions).
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Aesome I just updated my Pefectdisk tonight. I was wondering about this problem.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

On My computer it has fixed some problems... but not all with the latest PerfectDisk release.

I am now able to do a boot time defrag of my C drive.  The problem is that I have 2 harddrives in my computer, each with more than one partition. All of the other partitions get the error "driver conflict" and PerfectDisk is unable to 'open' the drives to defrag them.

I also used to be able to defrag the systems files on the different partitions (not the partion with the OS) while running windows, but now I can't do either.

I of course tried different things: turning off 'auto-protect' for NIS 2009, and some other things, but the only thing that 'cured' it was to uninstall NIS 2009 (not even disabling the NIS Service fixed it).  At least I no longer get a BSOD, and I can defrag my C drive.... but there are still some issues.

Mattehw

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Raxco has confirmed that the fix for this issue is in the update they posted last Thursday (9/11/08).  PerfectDisk 2008 build 9.00.64.

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Hi Scott:

To me it seems to be 'partially' fixed.  I have NIS 2009 on 3 different computers (x1 XP pro, x1 XP Media Edition, and x1 XP Home edition) and all three still have the same problem I mentioned above:

1. Yes, Perfect Disk will now do a boot time defrag of the c drive (all three computers  have their OS installed on the c drive).

2. PerfectDisk will NOT do a boot time defrag of any partitions other than the C drive (or on a second hard drive in one computer). 

Normally, a boot time defrag would only need to be done on the OS partition because normally you can open PerfectDisk , click on the partion you want to do a system files defrag on, and click 'systems files."  With NIS 09 running I get a pop up stating that its not able to close the handles and the computer must be restarted to do a boot defrag (which of course won't work).

Matthew Friend

- all systems (XP Pro, XP Media Edition, and XP Home) have sp3 and all microsoft updates applied.

- PerfectDisk (both PerfectDisk VMWare edition and Pro edtion) exhibit the same problem,and both are "fixed" and work correctly if NIS 2009 is uninstalled.

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Thanks for the info, Matthew.  We have also sent this info to Raxco so that they can look into the problem further.  I'll post again if I receive any updates.
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Thanks Scott.

I did a little further testing today:  I rolled one of my computers over to the original Vista SP1 image.  I have the same problems as stated earlier with the XP computers with partitions, etc.

Matthew

Test computer:

-Vista Home Premium SP1

-PerfectDisk VMWare lastest patch (64)

-All Windows updates applied.

-NIS 2009 with all updates

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Please contact Raxco support at http://www.raxco.com/support/nt_email.cfm and we'll see if we can figure out what is going on.

- Greg/Raxco Software
Microsoft MVP 2003-2007
Windows File Systems

Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department.

[edit: Replaced email address with link to support form on PerfectDisks domain in compliance with the Participation Guidelines and Terms of Service.]

Message Edited by Allen_K on 09-17-2008 02:57 PM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Hi Greg:

I finally remembered to submit info to support at Raxco.  

I had conducted one more test (along with the x4 versions/computers I tested on earlier).

I took one computer that has two hard drives. I  wiped and reformated both drives and rolled an XP image onto it. I did NOT partition the drives.  PerfectDisk will defrag the first (OS.. C Drive) but errors and will not defrag the 2nd drive.  I also attached the PDboot log file for support to look at.

Matthew

Since i can't attach files here, here is a little from the boot log as to the errors:

>Defrag32 File Log:**********************************
DefragFs: build16.  NT Version: Major=0x5, Minor=0x1, Build=0xa28, CSD=Service Pack 3 (free).
DefragFs: Built Aug 25 2008, 09:57:39.
DefragFs: BOOT start. Date: 9/25/2008, Time: 17:08:59.62 GMT.
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\EPERSIST.DAT'.
          DesiredAccess: 0x12019f.
          Disposition: 0x1.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\ERASERUTILREBOOTDRV.SYS'.
          DesiredAccess: 0x110180.
          Disposition: 0x1.
          Options: 0x20.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\EPERSIST.DAT'.
          DesiredAccess: 0x12019f.
          Disposition: 0x1.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\WINDOWS\system32\drivers\NIS\1000000.07D\Cat.DB'.
          DesiredAccess: 0x12019f.
          Disposition: 0x3.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
PDBoot: No active pagefile on drive.
PDBoot: Boot-time defrag status: Completed
PDBoot: Volume is not dirty
PDBoot: Failed to open volume using DefragFS (32,642).
PDBoot: \DosDevices\Volume{94fb01a6-85b8-11dd-b5b9-001e900ad516}
PDBoot:
PDBoot: Trying to open the volume again with force open handles to close.
PDBoot: Volume is not dirty
PDBoot: Failed to open volume using DefragFS (32,742).
PDBoot: \DosDevices\Volume{94fb01a6-85b8-11dd-b5b9-001e900ad516}
PDBoot:
PDBoot:      Could not gain exclusive access to drive D:\ (32).
     There is a possible driver conflict. (D:\)
PDBoot: Calling:    NtShutdownSystem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\VSM000.IDX'.
          DesiredAccess: 0x120116.
          Disposition: 0x3.
          Options: 0x8020.
          Origin is system process -- probably ExWorkerItem
DefragFs: build16.  NT Version: Major=0x5, Minor=0x1, Build=0xa28, CSD=Service Pack 3 (free).
DefragFs: Built Aug 25 2008, 09:57:39.
DefragFs: BOOT start. Date: 9/25/2008, Time: 17:10:47.78 GMT.


>Defrag32 File Log:**********************************
DefragFs: build16.  NT Version: Major=0x5, Minor=0x1, Build=0xa28, CSD=Service Pack 3 (free).
DefragFs: Built Aug 25 2008, 09:57:39.
DefragFs: BOOT start. Date: 9/25/2008, Time: 18:48:31.62 GMT.
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\WINDOWS\LastGood'.
          DesiredAccess: 0x110080.
          Disposition: 0x1.
          Options: 0x204022.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\SRTSP\SrtETmp'.
          DesiredAccess: 0x110001.
          Disposition: 0x1.
          Options: 0x1021.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\EPERSIST.DAT'.
          DesiredAccess: 0x12019f.
          Disposition: 0x1.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\ERASERUTILREBOOTDRV.SYS'.
          DesiredAccess: 0x110180.
          Disposition: 0x1.
          Options: 0x20.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\Program Files\Common Files\Symantec Shared\EENGINE\EPERSIST.DAT'.
          DesiredAccess: 0x12019f.
          Disposition: 0x1.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
DefragFs: Received Illegal Open, failing with error 0xc00000a2.
          Name: '\WINDOWS\system32\drivers\NIS\1000000.07D\Cat.DB'.
          DesiredAccess: 0x12019f.
          Disposition: 0x3.
          Options: 0x60.
          Origin is system process -- probably ExWorkerItem
PDBoot: No active pagefile on drive.
PDBoot: Boot-time defrag status: Completed
PDBoot: Volume is not dirty
PDBoot: Failed to open volume using DefragFS (32,642).
PDBoot: \DosDevices\Volume{94fb01a6-85b8-11dd-b5b9-001e900ad516}
PDBoot:
PDBoot: Trying to open the volume again with force open handles to close.
PDBoot: Volume is not dirty
PDBoot: Failed to open volume using DefragFS (1005,767).
PDBoot: \DosDevices\Volume{94fb01a6-85b8-11dd-b5b9-001e900ad516}
PDBoot:
PDBoot:      Could not gain exclusive access to drive D:\ (1005).
     There is a possible driver conflict. (D:\)
PDBoot: Calling:    NtShutdownSystem
DefragFs: build16.  NT Version: Major=0x5, Minor=0x1, Build=0xa28, CSD=Service Pack 3 (free).
DefragFs: Built Aug 25 2008, 09:57:39.
DefragFs: BOOT start. Date: 9/25/2008, Time: 18:49:56.62 GMT.
Kudos1 Stats

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

If anyone else is having the same issue with PerfectDisk not boot defragging a second harddrive or a second partition on a harddrive, Raxco has a fix available that appears to work.  I tried it on 3 different computers and it allowed the different harddrives/partitions to be successfully boot defragged.

If you contact support at Raxco, Susie Colon was very helpful in asking questions, sending me files to log boot errors, and finally sending me the file that has the fix in it.

Matthew

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Mat, anyway you can post how this was fixed without us having to contact texh support?  thanks
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Hi Dschachm:

They sent me a fixed/updated   DefragFS.sys (it goes in the windows > System32 > Drivers folder.

I can send it to you, but they might have a 'better' fix or update since then.

Matthew

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

If you could post it or email it to me that would be great, i would love to take a look at it.  Thanks in advance.

[edit: removed email address per the Participation Guidelines and Terms of Service. - Please contact dschachm through private message]

 

Message Edited by Tim_Lopez on 10-31-2008 05:37 PM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Hi Dschachm:

It can be downloaded from this link:  {removed}

If Symantec doesn't want me to put the link here, maybe they can contact Raxco so Raxco can provide a link here.

Matthew

[edit: Please link to the web page that the file can be downloaded from, and not to the file itself.]

Message Edited by Allen_K on 11-08-2008 01:12 AM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Thanks for that file.  Unfortunately, still getting blue screen crashes.  Extremely frustrating! 

System drive is C:

Program files are on D:

Archive storage are on E:

C: - E: on one physical drive

F:  Page File and temp

G:  Storage

F: & G on second physical drive

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Did you install the patch from Raxco? Worked for me.

Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

I installed the build 64 patch and then after that the patch supplied by the gentleman here in this thread.  I get a blue screen just before hitting 100% on "Analyze" of Drive C:  Happens all the time.

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

The patched worked for me on both my drives. Did you over write your old file when you replaced it with the one from Raxco? Have you tried running a CHK disc?
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Yes, I overwrote the original file and as a last resort after it failed many times, overwrote the same older version found in the Perfectdisk program files directory.  So, no chance the old file was used.

There's nothing the matter with my drive and this issue came only immediately after installing NIS 2009.  In fact, I defragged my hard drive just before installing NIS 2009.

There is an obvious incompatibility still.  BTW, blue screen crashes also when I run analyze on my D: partition.

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

The file doesn't go in your Perfectdisk directory it goes into System32 folder. I have PD 2008 build 64 on both my pc's with NIS 2009 and no errors.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Please read the info I posted more closely...I already did that.

Perfectdisk 2008 build 64 with NIS 2009 and blue-screens all over the place here

Message Edited by FinnEire on 11-08-2008 06:29 AM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Have you tried doing a complete uninstall of PD? There are 3 firewall entries that must be allowed for PD to run in NIS. Autoupdate,PD91Agent and PD91Engine.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

No I have not but worth a try.  Doubt it works though.  Also, I previously excluded the PD program directory from autoprotect and I do not need autoupdate service as I have that off in PD.  The engine file is not being blocked or hindered by NIS.  The agent file only comes into play for off-line defrag and my blue screens preced that kind of function.  Hence my almost 100% certainty of an incompatibility.  Likely because of the way I have things partitioned etc.

Message Edited by FinnEire on 11-08-2008 06:42 AM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Please do as I suggested. Add those things to NIS 2009. I have 2 pc's with the same set up and it works just fine. Also have you run a CHK disk? PD would crash with my "F" drive till I added the patch.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Dont really understand the need as Internet access should not be a prerequisit to defrag a system.  Also, your PC is not setup like mine.  Look at my partitioning, scratch disk etc.  Not the same.  Also, I doubt I need chkdsk as I ran PD just fine prior to NIS.

I'll try a reinstall but some of your suggestions really do not seem to directly apply.   The ONLY change to my system was install of NIS 2009.

Appreciate your concern and input though!

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

You are not adding those programs for just internet access. NIS 2009 gave me pop ups about them when I ran PD so I allowed them.I have Automatic Program Control turned off and Advanced Event Monitoring turned on.Message Edited by Dieselman743 on 11-08-2008 07:02 AM
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

...and just another note that PD has a history of these sorts of problems.  Had the exact same problem before, as did many other people, with Zonelabs suite.  After that I switched to Comodo and no problems at all.  PD has technotes about the zonelabs issue too.  Maybe fixed it by now.

I'll post again after uninstall and reinstall.  Also, what area specifically did you add the PD system files you listed as exclusions or having special permissions?

Thanks!

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

I have received no popups whatsoever.  I have automatic program control turned on and like that feature very much.

Where and exactly how did you add the program files in NIS?

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Its really a good idea to turn off Automatic Program Control and turn on Advanced Event Monitoring. This gives you more control over what NIS does. It also unlocks more features like keylogger and code injection blocking. Too add them simply click on "settings" next to Internet. Then click on Program Control under Smart firewall.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Ok, uninstalled, cleaned registry of old PD entries, reinstalled, patched to build 64 then patched the "fix" file into Windows\system32\drivers and added entries in NIS for files mentioned.  Result?  Same exact crashes....as I had suspected.

Also a note that I get blue screen crashes right off with an analyze operation.  Happens on ALL my drives and for some it happens near end of analysis and on my scratch/cache disk, it happens immediately.

Back to the drawing board for Norton and PD for getting this completely solved.  I doubt I am the only one experiencing this as my system, outside of hard drive partitioning is very clean, mainstream and fully patched.  I still say it is my partitioning that makes it happen on my machine.

Message Edited by FinnEire on 11-08-2008 07:38 AM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Did you try turning off automatic program control and turning on advanced event monitoring? Is there anything in your logs? I just installed PD and NIS 2009 on my test pc and it works like a charm. The patch addresses offline defraggs.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

I justed called my buddy and no crashes on his system either.Has to be something on your end cause the patch worked for even for mfriend.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Well, my issue is not offline defrags and yes, I turned off the automatic program control.  Crash crash crash.... just like Zonelabs and PD did for me months ago.
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Turn off Automatic Programs Control and turn on Advanced Event Monitoring. Also have you tried running a CHK disk like I mentioned? Well now we are getting somewhere. If ZA did the same as NIS then its neither program. Something different on your pc if your having the same results with 2 products. ZA came out with a fix for that BTW.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

What other security programs are you running? What other programs are running in the back round?
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

OK...I fixed it and it turned out to be something unrelated to NIS 2009.

Diesel, thanks and sorry for making you do all the typing!  Here's what I found:

1.  In PD I went to "product Resources" tab and clicked "support" and then the "start" button to have it scan my system for potential problems.  It identified a single file named windrvnt.sys

2.  I found this file in Windows\system32 and it did not have a company name or info associated.  Did a google search and found it was a file from a product called Folder Lock.

3.  I did not have folder lock installed but remembered accessing a folder lock created archive file that was on a CD I burned years ago.  I had put that CD in the drive yesterday and opened the archive.  It annoyed me that it allowed me to open the archive without a password or anythign as I believed folderlock would require.  "**bleep** software." I thought.

4.  Turns out that by merely accessing that folder lock archive file a change was made to my registry and that windrvnt.sys file was copied to my system.

5.  I checked and sure enough, this is how an older version of folder lock operates when you access an archive with a PC that does not already have it installed.  Bad, bad software and I beleive the developer has since addressed the problem with that file in later versions of their product.

6.  I deleted the file, removed a service entry in the registry that was calling it and afetr reboot, I am defragging without issue.

Apologies for overtaking this thread for a while!  Ashamed.

Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

Glad you fixed it. Told you it wasnt NIS causing your problem.
Real Time Protection = NIS 2009 + NATBehavior Analysis = ThreatfireOn Demand = MBAM
Kudos0

Re: PerfectDisk Build 64 fixes NIS 2009 conflict

The defragfs hotfix is planned to be included in the upcoming PerfectDisk 10.

Greg/Raxco Software

Message Edited by gshayes on 01-07-2009 05:23 AM

This thread is closed from further comment. Please visit the forum to start a new thread.