> [9/27/2013 8:25:44 PM] PHYLOCK: Check Point - SFN:E:\PHYLOCK.SWP
engineerguy3809,
What is the E: drive? A NTFS partition or other?
IFW 2.83 Stalls while Gathering Information
-
TeraByte Support
- Posts: 3628
- Joined: Thu May 05, 2011 10:37 pm
Re: IFW 2.83 Stalls while Gathering Information
it all seems to go hand-in-hand - something is slowing down access to the
drive (does event log have messages that would indicate something running
about the same time) or somehow the file priority got set to low?
"engineerguy3809" wrote in message news:6426@public.image...
Thanks for the reply. EVENTUALLY, PHYLock was satisfied and TBW
successfully created an image. However, it took more than 90 minutes before
it started; and THEN it took an unusually long time to complete (about 3.5
hours instead of the 30 minutes or so it usually takes).
Before starting TBW, I disabled everything I could without crashing the
computer. I disabled all AV, all email & all non-critical tray apps. Task
Manager "Applications" tab listed only TBW and Task Manager "Services" tab
did not indicate any obvious strange/new/unusual services were running. The
Drive activity light occasionally would flicker while waiting, but only
about once every 30 seconds or so. Obviously, SOMETHNG is still "active"
that needs to finish or quit before PHYLock gets its lock.
As a test, I've even manually stopped a few select services that I thought
might be conflicting (expecting I might also crash the PC, but at least
possibly identify the cause).
So far, no luck.
I've uninstalled/reinstalled both TBW and PHYLock, both together and
separately.
I've also verified the Registry string mentioned in another posting is
correct. I'm out of ideas.
I guess I can default to my Win-PE build as my primary imaging method.
drive (does event log have messages that would indicate something running
about the same time) or somehow the file priority got set to low?
"engineerguy3809" wrote in message news:6426@public.image...
Thanks for the reply. EVENTUALLY, PHYLock was satisfied and TBW
successfully created an image. However, it took more than 90 minutes before
it started; and THEN it took an unusually long time to complete (about 3.5
hours instead of the 30 minutes or so it usually takes).
Before starting TBW, I disabled everything I could without crashing the
computer. I disabled all AV, all email & all non-critical tray apps. Task
Manager "Applications" tab listed only TBW and Task Manager "Services" tab
did not indicate any obvious strange/new/unusual services were running. The
Drive activity light occasionally would flicker while waiting, but only
about once every 30 seconds or so. Obviously, SOMETHNG is still "active"
that needs to finish or quit before PHYLock gets its lock.
As a test, I've even manually stopped a few select services that I thought
might be conflicting (expecting I might also crash the PC, but at least
possibly identify the cause).
So far, no luck.
I've uninstalled/reinstalled both TBW and PHYLock, both together and
separately.
I've also verified the Registry string mentioned in another posting is
correct. I'm out of ideas.
I guess I can default to my Win-PE build as my primary imaging method.
-
engineerguy3809
- Posts: 57
- Joined: Tue Jul 24, 2012 10:17 pm
Re: IFW 2.83 Stalls while Gathering Information
I apologize for dragging this thread on for so long, but it has me stumped.
Brian K: I have a 1.5TB physical Drive with 3 partitions, C (Active OS partition) is approx 300 GB, D is approx 600 GB and E is approx 600 GB. The D and E partitions are strictly data. All are NTFS. No other OS on drive(s), no non-Microsoft/Windows partitioning software has been used, no non-Windows drivers. I save my images to a second physical internal HD. All internal HD's are SATA. System is fairly "vanilla". I have run CHKDSK/F from Safe-Mode on all drives. No errors. I have run both SuperAnti Spyware and MalwareBytes from both Windows and from Safe-Mode. Nothing found using either application.
Terabyte Support: My events log does have some strange things around the time IFW was last launched.
The first event following the entry that IFW starting was an ERROR that was time stamped 14 minutes after IFW was started. Contents are pasted below.
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The event following the ERROR was a WARNING that occurred about a minute and a half later. Contents are pasted below.
Windows saved user JERRY\Default registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Although I know how to display these logs, I am almost clueless how to interpret most of the log contents.
Does any of this help any further?
I'm very grateful for the help. I've been an IFW user for 5+ years and really like the TeraByte software products. It is far less "bloated" than most of your competitors products.
Brian K: I have a 1.5TB physical Drive with 3 partitions, C (Active OS partition) is approx 300 GB, D is approx 600 GB and E is approx 600 GB. The D and E partitions are strictly data. All are NTFS. No other OS on drive(s), no non-Microsoft/Windows partitioning software has been used, no non-Windows drivers. I save my images to a second physical internal HD. All internal HD's are SATA. System is fairly "vanilla". I have run CHKDSK/F from Safe-Mode on all drives. No errors. I have run both SuperAnti Spyware and MalwareBytes from both Windows and from Safe-Mode. Nothing found using either application.
Terabyte Support: My events log does have some strange things around the time IFW was last launched.
The first event following the entry that IFW starting was an ERROR that was time stamped 14 minutes after IFW was started. Contents are pasted below.
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The event following the ERROR was a WARNING that occurred about a minute and a half later. Contents are pasted below.
Windows saved user JERRY\Default registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Although I know how to display these logs, I am almost clueless how to interpret most of the log contents.
Does any of this help any further?
I'm very grateful for the help. I've been an IFW user for 5+ years and really like the TeraByte software products. It is far less "bloated" than most of your competitors products.
-
TeraByte Support
- Posts: 3628
- Joined: Thu May 05, 2011 10:37 pm
Re: IFW 2.83 Stalls while Gathering Information
For one of those:
http://support.microsoft.com/kb/909444
another:
http://support.microsoft.com/default.aspx?kbid=837115
You probably also want to scan using:
https://support.kaspersky.com/viruses/rescuedisk#downloads
burn the iso, do all the updates, then scan.
Is there any slowness using VSS or if you disable phylock and ignore the
can't lock message and it starts running (just for speed testing - 3 hr or
30 min).
"engineerguy3809" wrote in message news:6439@public.image...
I apologize for dragging this thread on for so long, but it has me stumped.
Brian K: I have a 1.5TB physical Drive with 3 partitions, C (Active OS
partition) is approx 300 GB, D is approx 600 GB and E is approx 600 GB. The
D and E partitions are strictly data. All are NTFS. No other OS on
drive(s), no non-Microsoft/Windows partitioning software has been used, no
non-Windows drivers. I save my images to a second physical internal HD.
All internal HD's are SATA. System is fairly "vanilla". I have run
CHKDSK/F from Safe-Mode on all drives. No errors. I have run both
SuperAnti Spyware and MalwareBytes from both Windows and from Safe-Mode.
Nothing found using either application.
Terabyte Support: My events log does have some strange things around the
time IFW was last launched.
The first event following the entry that IFW starting was an ERROR that was
time stamped 14 minutes after IFW was started. Contents are pasted below.
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.
For more information, see Help and Support Center at
[
http://go.microsoft.com/fwlink/events.asp
](http://go.microsoft.com/fwlink/events.asp)
..
The event following the ERROR was a WARNING that occurred about a minute and
a half later. Contents are pasted below.
Windows saved user JERRY\Default registry while an application or service
was still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use.
This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at
[
http://go.microsoft.com/fwlink/events.asp
](http://go.microsoft.com/fwlink/events.asp)
..
Although I know how to display these logs, I am almost clueless how to
interpret most of the log contents.
Does any of this help any further?
I'm very grateful for the help. I've been an IFW user for 5+ years and
really like the TeraByte software products. It is far less "bloated" than
most of your competitors products.
http://support.microsoft.com/kb/909444
another:
http://support.microsoft.com/default.aspx?kbid=837115
You probably also want to scan using:
https://support.kaspersky.com/viruses/rescuedisk#downloads
burn the iso, do all the updates, then scan.
Is there any slowness using VSS or if you disable phylock and ignore the
can't lock message and it starts running (just for speed testing - 3 hr or
30 min).
"engineerguy3809" wrote in message news:6439@public.image...
I apologize for dragging this thread on for so long, but it has me stumped.
Brian K: I have a 1.5TB physical Drive with 3 partitions, C (Active OS
partition) is approx 300 GB, D is approx 600 GB and E is approx 600 GB. The
D and E partitions are strictly data. All are NTFS. No other OS on
drive(s), no non-Microsoft/Windows partitioning software has been used, no
non-Windows drivers. I save my images to a second physical internal HD.
All internal HD's are SATA. System is fairly "vanilla". I have run
CHKDSK/F from Safe-Mode on all drives. No errors. I have run both
SuperAnti Spyware and MalwareBytes from both Windows and from Safe-Mode.
Nothing found using either application.
Terabyte Support: My events log does have some strange things around the
time IFW was last launched.
The first event following the entry that IFW starting was an ERROR that was
time stamped 14 minutes after IFW was started. Contents are pasted below.
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.
For more information, see Help and Support Center at
[
http://go.microsoft.com/fwlink/events.asp
](http://go.microsoft.com/fwlink/events.asp)
..
The event following the ERROR was a WARNING that occurred about a minute and
a half later. Contents are pasted below.
Windows saved user JERRY\Default registry while an application or service
was still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use.
This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at
[
http://go.microsoft.com/fwlink/events.asp
](http://go.microsoft.com/fwlink/events.asp)
..
Although I know how to display these logs, I am almost clueless how to
interpret most of the log contents.
Does any of this help any further?
I'm very grateful for the help. I've been an IFW user for 5+ years and
really like the TeraByte software products. It is far less "bloated" than
most of your competitors products.