Surface Errors

I ran TechTools Deluxe last night and it told me I had Surface Errors. I am wondering how I can repair the Surface Errors?

I am wondering if it will spread and corrupt my hard drive, or if it's okay to have one or two bad sectors?
No, this is not ok. Even one bad block will cause problems (I was not able to clone my drive due to 2 bad blocks). If you followed the directions listed at http://www.thexlab.com/faqs/repairprocess.html#Anchor-Bad-11481 and you still get reports of bad sectors, then the table in the drive is full (which means that your drive really has more than a few bad blocks. The blocks are only marked as bad, they cannot be fixed).
Looks like you need a new drive.

Similar Messages

[VIA] So where's this error message from? KT4V or Windows 98se

Hi,
Reference KT4V Series and using windows 98 se.
My system has been running fine for a couple of years then one day the following happened.
Slow boot up and when I tried to open/close windows applications it was very slow.
e.g. click on 'My Computer' took 5 minutes to open then no drives displayed for a further
5 minutes.
Virus scans etc found nothing.
Then the dreaded tasks had to be done.
I fully formatted the drive and checked for surface errors (took 10 hours).
Drive has no errors - I re-loaded windows 98 se - still the same problem.
Infact when trying to delete a file it actually went into freeze mode.
I have a 60gb drive, 256mb but in the past I would get the following error:
'the system is dangeroulsy low in resources and will be shut down' even though very little was
running.
I would re-start okay.
now i get the error:
' the system is either busy or has become unstable'
any ideas on these errors?
thanks for reading this.
Thanks to those that replied - I have now solved the problem.
The Bios settings have some how got set to the default settings as a result my FSB was set to 107mhz
I have now set this to 266mhz and wow behold the windows applications are opening and closing
as quick as before.
As a default the boot sector virus protection is set to off - when I know I set this to on.
Maybe the 'system is unstable messages and low on resources messages' somehow reset the bios to safe default values - especially as the system was closing itself down after these messages.
The KT4V will support a processor speed of 1.3 ghz only the Processor I was sold with the board is 1800+
As a result of resetting the FSB in the bios the processor speed is now running at 1.55 ghz
The system now boots up and closes down at speed and as said above the applications open and close ok as well.
The reset to default settings also meant that scan disk when checking the reformatted disk for surface errors ended up taking 11.5 hours to run on a 60gb hdd when the program itself estimated
only 3-4 hours.
Lot of time wasted - so check your FSB bios settings along with your boards capability - to ensure you are getting the Processor speed you paid for.

have you cleaned your PC recently if at all?
open up your case, if it is very dusty your system may be overheating. remove the heatsink and fan, and clean all old thermal paste from cpu die and heatsink. clean dust from heatsink fins and from fan blades. reapply fresh thermal paste to cpu die surface. only a very thin layer is needed. arctic silver is good stuff.
use a can of compressed air ("air duster") to blow any surface dust of motherboard and other cards. remove memory sticks and blow into slots.
remove your PSU and remove the top cover. again use air duster to blow any dust buildup from PCB and components
Quote
I fear a hardware issue
possible. but if you don't tell us your hardware it is difficult to guess

No backup possible, even after a clean re-install

I - NEED - HELP!!!
This is what happens before I encountered my problems with backing up my hard drive:
I'm using a MacBook Pro 17" Unibody. The hard drive was partitioned into two partitions. The first one was the bootcamp partition, 50 GBytes in size, running Windows 7 Ultimate. The second partition was the Mac OS X partition, 450 GBytes in size and running Mac OS X 10.6.4.
I had to change the size of the bootcamp partition due to a Windows game installation. For this I bought an used "CampTune 8.0" from Paragon Software. The repartitioning using "CampTune" didn't report any errors so I assumed everything was fine. But then I saw the slow dying of a Mac:
Trying to boot into Windows lead to the error message the the installation was damaged and I should repair it using the repair option of the Windows install DVD. I did as I told but was always caught in the startup loop:
"1. Insert install DVD
2. Restart your computer
3. Choose the repair option"
Trying to boot into Mac OS X shows a strange behaviour ranging from getting stuck in file system checking up to not being able to log in as normal user. Instead I was only able to log in as administrator. And when I was able to log in, there where more and more kernel panics during access to all kinds of volumes (internal hard drive, external USB hard drives, USB sticks...)
Fortunately I was able to save (NOT backup) my users home folder by hand.
And now the strange things started...
I decided to do a clean install of my Mac OS X 10.6.4 and all of my applications. For that I repartitioned the internal hard drive to one partition, chose the GUID-patition table, then formatted the drive using the option "overwrite with zeros".
Then I installed my Mac OS X and the applications and tried to do a bootable backup to an external USB hard drive. This drive I had partitioned with one partition, GUID-partition table and formatted it also using the option "overwrite with zeros".
I used the software "Data Backup 3" from ProSoft Engineering. But during backup there was a kernel panic and after that the B-tree of my internal drive was corrupted. I couldn't be repaired by Mac OS X. But the internal drive was still readable.
I tried again and again with "Data Backup 3", always ending in a kernel panic. But the active thread always was different (sometimes it was launchd, CleanApp deamon, Kasperskys kav deamon) without a repeating pattern.
I was able to make a backup using "Carbon Copy Clone 3.3", fortunately, and started from the backup. After that I used "TechToolPro 5.0.7" to find out if there were surface errors or problems in the directory structure. But even "TechToolPro" caused a kernel panic when accessing the hard drive...
To restore the contents of my external drive to the internal one I used "SmartBackup 3" from Solesignal Ltd. because I thought "Data Backup 3" caused the kernal panics. But it was the same with "SmartBackup 3": accessing the hard drives during backup causes kernel panics...
My last idea then was to use the restore function of Apples disk utility. And it worked. But when I copied the contents of my saved user home folder, I caused a kernel panic when the size of data copied exceeds more then approximately 80 GBytes. And after that the B-tree of my backup drive was corrupted.
This all is strange to me, because I installed a fresh system.
Does anyone encountered similar problems using backup software? And is there a solution for this?
Regards
Ansgar

whatever I tried I couldn't get the camera to work. So took it into local apple store and they swapped immediately with a new iphone 5.
loads of chatter on the internet about it.
This discussion has had 19000+ views
https://discussions.apple.com/thread/5327076?start=90&tstart=0

Builtin Cisco VPN not connecting - solution (albeit a very crappy one)

So I've been trying for a day to get Snow Leopard to connect to the Cisco VPN concentrator at work (dunno which model).
Today I was able to get a bit more detail by editing /etc/syslog.conf to enable debug logging to system.log and edit /etc/racoon/racoon.conf to uncomment the debug log line (racoon is the Cisco client).
This is the error that surfaced:
ERROR: failed to get subjectAltName
With racoon's debug2 logging on I was able to see the problem when the server's cert was displayed: the Subject Alternative Name field is blank. Now there's no way for me to get this fixed on the server side - I work for a 250,000 person organization and a change like that would take me being an executive and months of bureaucracy to get through. So here's what I did incase anyone else needs this and doesn't mine extreme kludgery:
First I needed to capture the configuration file that was generated at connect time:
sudo su -
while true; do cp /var/run/racoon/*.conf /tmp/; done
Hit connect just after typing this a few times, then ctrl-c in the terminal to stop it
You should hopefully have a file named /tmp/<ip>.conf where ip is the resolved ip address of your vpn server. Copy this file to /etc/racoon/ and edit it.
Change "verify_cert on" to "verify_cert off" and comment out the next line ("certificate_verification") with a #
Finally, edit /etc/racoon/racoon.conf. At the end, comment out the line 'include "/var/run/racoon/*.conf" ;' and add the line 'include "/etc/racoon/<yourfile>" ;'
This solution totally blows cause any configuration change requires a repeat of the procedure and also prevents you from having multiple VPNs configured without doing this for each of them. Suggestions welcome.

Hi
Could it be that your VPN assigned network of /16 overlaps with your host route? Are you able to change the mask on your split tunnel network to /24 or are you using the whole /16 subnet?
Cammy

How Can I Check the Health of the Time Machine Snapshots?

Hi. The last time I used Time Machine to restore to a fresh install of Mountain Lion, it had an error, I had to manually copy the folders and files in my home folder as well as XCode and bookmarks for Safari.
Is there an app that can check if the Time Machine snapshot will work when you need to restore it to a fresh install of Mountain Lion? Could it also check the backup disk for surface errors? My backup drive that uses Time Machine is fine.
Thank you in advance.
God bless.

Unfortunately, you cannot do diagnostics on a Time Capsule. Data on a Time Capsule are not stored directly to the drive. Data are stored in a sparsebundle disk image. If the disk image goes bad, then you can try to copy it to a regular hard drive so you can try repairing the disk image or you erase the Time Capsule.
You really don't need to check hard drives from time to time. If there are errors on the drive you will know about them before you have time to fix the drive. And, if the errors are fixable usually that doesn't happen using Disk Utility.
File errors are very rare no matter how often you use a HDD. There is no research to support your hypothesis.
To protect against hard drive failure (unrelated to file errors) is best avoided by making multiple backups. You cannot have too many backups. Given your concern for your files this will help you a lot more than running diagnostice tests on one hard drive. I would also recommend you not use Time Machine because its reliability is markedly less than most recommended backup utilities such as these. Furthermore, you can clone any drive using Disk Utility's Restore feature.
Suggested Backup Software
1. Carbon Copy Cloner
2. Get Backup
3. Deja Vu
4. SuperDuper!
5. Synk Pro
6. Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Clone using Restore Option of Disk Utility
1. Open Disk Utility in the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Select the destination volume from the left side list and drag
it to the Destination entry field.
5. Select the source volume from the left side list and drag it to
the Source entry field.
6. Double-check you got it right, then click on the Restore button.
Destination means the drive used for backup. Source means the drive you are backing up.

HDD having problems again!!!!

Hi all,
To save explaining (and typing) all over again, can anybody please have a look at the following link below:
http://forums.overclockers.co.uk/showindex.php?s=&postid=2451906#post2451906
I have posted there as I bought my drive from http://www.overclockers.co.uk
any suggestions please.
Kind Regards,
Andrew

Thanks Wonkanoby,
I will try that at the weekend as I will have more time.. Can you or anyone else tell me if and where I can download a piece of software that will scan the whole RAID Array for surface errors at reboot and mark them a bad.
I have had my RAM replaced and I did and Do check with MemTest86. No errors are found after five passes at the speeds stated (2,3,2,5 @ 180). This RAM is rated at 2,3,2,5 @ 200. I never told you that my 2 x 512 RAM is not matched pairs (Bought separately) and I am running in Duel Channel Mode, would this be a problem as I have never ran MemTest86 since I received this new motherboard a couple of days ago (used to have MSI KT6 Delta LISR in fact still got it as spare).
Cheers Mate

K8T NEO - MSI/Via Raid Tool useless

I am one of those unfortunate people who bought a K8T Neo FSR Motherboard (Mine has been replaced 3 times after failing totally but whose counting?). I am now having serious problems with my fourth version of this motherboard or at least I think I am. I am not sure!
Let me explain:
My SATA HDD Disk drives keep failing - or more correctly - I am getting messages from Windows Error Reporting that tells me there are disk problems. The exact error messages are reproduced below:
Event Type:   Error
Event Source:   viamraid
Event Category:   None
Event ID:     9
Date:      31/08/2006
Time:      8:32:41 PM
User:      N/A
Computer:   MASTER
Description: The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 6a 00 ......j.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 00 01 00 00 00 00 00 00 ........
0018: 5b 09 00 00 00 00 00 00 [.......
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 02 00 00 00 ........
0030: 00 00 00 00 07 00 00 00 ........
This is immediately followed by the following message:
Event Type:   Warning
Event Source:   Disk
Event Category:   None
Event ID:     51
Date:      31/08/2006
Time:      8:32:41 PM
User:      N/A
Computer:   MASTER
Description: An error was detected on device \Device\Harddisk2\D during a paging operation.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 33 00 04 80 ....3..
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 57 87 00 00 00 00 00 00 W......
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 44 00 00 02 00 @..D....
0040: ff 20 0a 12 88 02 20 40 ÿ ... @
0048: 00 00 01 00 0a 00 00 00 ........
0050: 00 00 00 00 00 06 6c 84 ......l
0058: 00 00 00 00 60 36 62 86 ....`6b
0060: 00 00 00 00 f7 04 81 05 ....÷..
0068: 2a 00 05 81 04 f7 00 00 *...÷..
0070: 80 00 00 00 00 00 00 00 .......
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........
I started getting these messages from a brand new SATA HDD which I immediately replaced. All went well for a week or so and then I started getting the exact same error messages all over again!
Were both HDD's really defective? I am beginning to wonder!
The practical implication of the above errors is that my computer freezes totally - I can't do anything at all - no mouse - no keyboard - no saving work - nothing! When I reboot and run Scandisk /F /R I sometimes get some disk surface errors but mostly I don't.
To my way of thinking there are two possibilities:
(1) Both these disk drives have genuine technical problems (ie such as surface errors)
(2) The MSI/Via SATA disk controllers on the motherboard are faulty and this is causing disk errors or possibly even disk crashes (is this even possible? I don't know!)
After the bad run that I have already had with K8T NEO motherboards please forgive me for being suspicious that my HDD problems really could result from a faulty SATA/HDD/Controller rather than genuine disk errors.
To help resolve the issue I downloaded and installed MSI's latest SATA HDD disk drivers which includes the VIA RAID TOOL. The raid tool includes an option to "check the status of controllers and disk drives" and a system "log" which is supposed to record all error conditions/events that occur on devices it controls.
The main problem here is that *IT DOESN'T WORK* !!!
Just a short wile ago my system started acting strangely and then it froze again (third time this hour). I opened the MSI/VIA Raid Tool from the System Tray and checked the logs - There was nothing in them at all - and yet in Windows Error Reporting there were 5 distinct error conditions reported. Obviously the MSI/VIA Raid Tool doesn't work too well.
I am at a loss as to what to do next. Has anybody out there had similar problems?
What steps should I take to resolve these issues?
Any comments/suggestions?

Not sure how a scope can let you know if you are supplying enough amps. Ripple and noise are basically non issues as the voltages are further regulated on the MB before they get to the componant level.
Almost everything is now regulated from the 12v supply unlike past systems were. As Watts do not tell how much 12v is being supplied by the PSU it is a non starter when you desribe your PSU. You can have a PSU that is 500w and only provides 8a on the 12v rail. That will not even allow an A64 system to startup. As is said over and over again in the forum don't assume that a 500w PSU will ruin your Rig. 24 or more amps on the 12v rail is recommended for a small to mid size build now days. More may be needed as you add parts to your system.
As this is not a common problem on that board, and I should know as I built a fairly large rig from one... We need to have complete specs. Did you know that a high end ATi Vid Card can use more juice than many CPU's you can use on that board? See why this is a concern that we get all the specs?
Like Hans said though I won't bother asking again either. Without some idea what we are looking at all we are doing is looking into a crystal ball. We would like to see if we can help but working with a crystal ball isn't in the tech manual.

K8N neo2 raid0 issues... random failure

I'm running 2x80 hitachi sata II in raid0 on sata 3 and 4.
Although everything works fine most of the time, sometimes (rarely) when I turn the pc on only one disk is recognized by the bios, causing a blue screen in windows boot (of course). I push the reset button and all becomes fine then. All the data is still there.
I've checked both disks for surface errors, they're both ok.
Nvraid bios is 4.81.
Does anybody has this issue with ocasional raid0 failure? This is really strange... I don't believe it's due the disks.

I hope you like my signature now, lol... :-)
Well, the PSU is a quality one, I guess, and the two hitachi drives aren't 1 month old yet. I already scanned them several times and found no problems at all.
Also, all my disks have a HDD cooler.
It could really be a power cable issue, since there's really a lot of cables inside... but I only have two sata power cables, and they're both powering the two disks... :-/ Besides, the SATA power cables are independent of all the other cables (that is, nothing else is connected to the wires where they are connected).
The only thing I did today was adding a HDD cooler for my Seagate IDE drive (the only one that didn't have one), after powering the pc up one of the Hitachi drives wasn't detected, I just reset the pc (didn't turned it off) and it was fine... Maybe my system is soooo lightning fast that the electricity wasn't fast enough to reach the 2nd drive on time... bahaha.

One Surface Pro giving 0x8004005 error when looking for task sequence.

This is only happening with one of many Surface Pro's
I am unsure what would cause this, booting from USB in a hub with USB Network Adapter.
<![LOG[LOGGING: Finalize process ID set to 812]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="tslogging.cpp:1495">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816"
file="bootshell.cpp:1052">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="util.cpp:963">
<![LOG[Debug shell is enabled]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:1063">
<![LOG[Waiting for PNP initialization...]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:60">
<![LOG[RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="configpath.cpp:186">
<![LOG[WinPE boot path: D:\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:211">
<![LOG[Booted from removable device]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:241">
<![LOG[Found config path D:\]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:545">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:579">
<![LOG[D:\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:596">
<![LOG[D:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:610">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[Starting DNS client service.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:663">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604"
file="tsmbootstrap.cpp:1129">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:1130">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="util.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="resourceutils.cpp:169">
<![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:963">
<![LOG[Failed to open PXE registry key. Not a PXE boot.]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:844">
<![LOG[Media Root = D:\]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1000">
<![LOG[WinPE boot type: 'Ramdisk:SourceIdentified']LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:779">
<![LOG[Failed to find the source drive where WinPE was booted from]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="2" thread="604" file="tsmbootstrap.cpp:1036">
<![LOG[Executing from Media in WinPE]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1041">
<![LOG[Verifying Media Layout.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:1581">
<![LOG[MediaType = BootMedia]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2565">
<![LOG[PasswordRequired = false]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2591">
<![LOG[Found network adapter "ASIX AX88772 USB2.0 to Fast Ethernet Adapter" with IP Address 10.0.192.203.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="604" file="tsmbootstraputil.cpp:474">
<![LOG[Running Wizard in Interactive mode]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2766">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:45:24.524+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Activating Welcome Page.]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:131">
<![LOG[Loading bitmap]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Spawned thread 1020 to download policy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawelcomepage.cpp:405">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:527">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:555">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:556">
<![LOG[Setting LogLevel to 0]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:557">
<![LOG[Setting LogEnabled to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:558">
<![LOG[Setting LogDebug to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:559">
<![LOG[UEFI: true]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:569">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:584">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsremovablemedia.cpp:322">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="util.cpp:963">
<![LOG[Setting SMSTSLocationMPs TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaSourceVersion TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBrandingTitle TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertSelection TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertStoreName TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSDiskLabel1 TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaSetID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaType TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSRootCACerts TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSupportUnknownMachines TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSTimezone TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Root CA Public Certs=]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:615">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:621">
<![LOG[Support Unknown Machines: 1]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:632">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:675">
<![LOG[No hook is found to be executed before downloading policy]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:699">
<![LOG[Authenticator from the environment is empty.]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:838">
<![LOG[Need to create Authenticator Info using PFX]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:850">
<![LOG[Initialized CStringStream object with string: 1A069864-04BE-4B67-B83D-10B87060836D;2014-01-18T03:47:18Z.]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="stringstream.cpp:101">
<![LOG[Using user-defined MP locations: http://CA1AP03P.cameco.com]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:911">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Set media certificates in transport]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9558">
<![LOG[IP: 10.0.192.203 10.0.192.0]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9579">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 GET /SMS_MP/.sms_aut?MPLOCATION&ir=10.0.192.203&ip=10.0.192.0]LOG]!><time="19:47:18.573+480" date="01-17-2014" component="TSMBootstrap"
context="" type="1" thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="libcrypt.cpp:1914">
<![LOG[Default CSP Type is 24]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libcrypt.cpp:1915">
<![LOG[New settings:]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:925">
<![LOG[    site=CA1,CA1, MP=http://CA1AP03P.cameco.com, ports: http=80,https=443]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="tsmediawizardcontrol.cpp:927">
<![LOG[    certificates are received from MP.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:931">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Preparing Client Identity Request.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:583">
<![LOG[    Setting transport.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:586">
<![LOG[    Setting SourceID = 1A069864-04BE-4B67-B83D-10B87060836D.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:590">
<![LOG[    Setting site code = CA1.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:595">
<![LOG[Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context=""
type="1" thread="1020" file="utils.cpp:1314">
<![LOG[    Setting SMBIOS GUID = 3F9CD3F3-201B-D0BE-FB7A-B6EE09756535.]LOG]!><time="19:47:20.419+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:623">
<![LOG[    Adding MAC Address 00:50:B6:4D:18:2D.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:642">
<![LOG[Executing Client Identity Request.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:666">
<![LOG[Requesting client identity]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:5760">
<![LOG[Setting message signatures.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 CCM_POST /ccm_system/request]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="1"
thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[pNext != NULL, HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,1972)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[reply has no message header marker]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:5868">
<![LOG[Failed to get client identity (80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:6163">
<![LOG[oClientIdentity.RequestClientIdentity(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,668)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="tspolicy.cpp:668">
<![LOG[Failed to read client identity (Code 0x80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="tspolicy.cpp:668">
<![LOG[TS::Policy::GetClientIdentity (&httpTransport, sSiteCode.c_str(), sMediaGuid.c_str(), sClientGUID, sNetbiosName, bUnknown, sServerName, sServerRemoteName, sImportedClientIdentity), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,965)]LOG]!><time="19:47:20.512+480"
date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:965">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:1378">
<![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap"
context="" type="0" thread="1020" file="tsmediawelcomepage.cpp:303">
<![LOG[Setting wizard error: An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time="19:47:20.512+480" date="01-17-2014"
component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:1547">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Skipping Confirmation Page.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaconfirmationpage.cpp:170">
<![LOG[Skipping Task Sequence Selection Page.]LOG]!><time="19:47:20.528+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediataskselectionpage.cpp:118">
<![LOG[Skipping Variables Selection Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediavariablesselectionpage.cpp:155">
<![LOG[Skipping Resolve Progress Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaresolveprogresspage.cpp:96">
<![LOG[Activating Finish Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediafinishpage.cpp:107">
<![LOG[Loading bitmap]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:939">
<![LOG[Successfully launched command shell.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:430">

I've seen this on a few of the Surface Pro 3's we got in recently. It is because you need to update the date/time in the OS. The easiest way to do this is to
(1) Make sure you have command support enabled in your boot image.
(2) Before you start your image process from the boot image, press (Fn + F8)
(3) At the command prompt, check your date/time.
(4.a) Type cd x:\windows\system32
(4.b) Type date the current date is displayed, it's most likely off. It will prompt you to change the date using the mm-dd-yy format, change to the current date there, press enter
(4.c) Type the Time the current time is displayed (24 hour time), key in the current time press enter
(5) Start your imaging process, all should be well
Excellent advice!!! For me, even though I had already booted the OS on my SP3, fully updated the firmware and restarted about 6 different times, I still would get a failure when the Boot image started to load. I followed these instructions and I was good to
good. I'm just floored to see that my date and time were off by 3 days and 11 hrs, even though my OS was correct. I'm flabbergasted that this was the case. Thanks for the post! Helped me a lot!

Persistent surface scan error on techtool- please help

My Powerbook started running slower than usual, so I decided to run the Techtool Deluxe cd I got with my Apple Care plan. I ran all the tests. My result: 5 errors in the Surface Scan test.
I didn't know what to do, so I took my Powerbook to the Apple store Genius Bar. The guy just said I needed to reformat my HD. So, I did the "erase and install" reformat at the store.
But, the genius bar guy didn't seem to know what he was talking about, so after I did all the software updates at home, I decided to run the Techtool Deluxe cd again. Again, the results showed I had 5 errors in the Surface Scan test, even after I had completely reformatted my hard drive.
I had the 3.0.4 version of Techtool, and just to be safe that it wasn't out of date, I installed it on my computer and updated it to version 3.1.2.
With the updated 3.1.2 Techtool Deluxe program, I ran all the tests again.
And STILL I have 5 errors on my Surface Scan test.
Here is a copy of my results (every thing else passed).
Surface Scan
Failed - 5 errors
The Surface Scan test will scan the disk for bad blocks.
Media defects cause this test to fail. You should consider backing up the device, reformatting the media, replacing the data, and then testing again.
Please help! What am I supposed to do???? (I don't think reformatting my HD will help, because I already did, and still have this problem)
Thank you!

Welcome to the Apple discussions.
When you reformatted the hard drive, did you do an erase and write zero's? That's important because that's what remaps the bad sectors of the hard drive. After booting from the OS X CD, choose disk utility, choose the hard drive, and on the erase tab, choose security options and write zero's. If you don't do this step, a plain erase or erase and install only deletes the index or catalog of the disk contents.

Remote Desktop disconnected because of security error from Windows 8.1 Surface to Server 2008

Hello,
I am trying
to connect to a remote app on a 2008 server from a surface pro 3 with 8.1
through Netilla SSL VPN and I getting the following error message.
Remote Desktop Disconnected
Because of a security error, the client could not connect to the remote computer Verify that you are logged on to the network and then try connection again
if I am connected to the network and use the RDP file, it connects fine.
This
was previosluly working, but when I changed the terminal server to per user
license mode from trial mode this happen
This works fine from Windows 7 machines.<o:p></o:p>
Any ideas?
Thanks,
Derek

Hi Derek,
Thank you for posting in Windows Server Forum.
From the error itself it seems that there is some network connection issue with VPN. Kindly see that you get network when you are using VPN connection, also VPN must be running. You can also try to “ping” the remote computer and see whether there is successful
ping result.
Also try to use “Allow connections from computers running any version of Remote Desktop” option on server side and check whether you can remote desktop successfully.
Apart this issue can also be caused due to certificate as VPN can’t resolve the certificate properly and facing this issue because you are facing issue only with usage of VPN (as you have commented). Please check
this link for detail.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Surface Pro 2 freezes briefly - storachi and disk error

Hello tech net
I am running a surface pro 2 with windows 8.1 (updates current as of 3 days ago), 4 GB RAM, 64GB HD. For the last several months the device will freeze up for about 5-10 secs multiple times per hour, and then resolve on it's own. During that
time task manager shows the disk is at 100% and event viewer will display 2 Warnings: an storachi (129) and a disk (153) error. This is in addition to a service control error (7000) that happens multiple times per second but doesn't seem to
affect performance. These freezes happen when plugged in, on battery, SDXC card installed or not, wi-fi or not, and no particular program running. It even happens when I'm not using the device if I go back thru event viewer. The 100% on disk is
not associated with any increase in process or app activity. Most of the time there are a couple 0.1MB/s demands like outlook, explorer or service host running but nothing that looks unusual when it spikes and freezes.
I am not a tech person and my online search for help has yielded a wide variety of solutions to this problem that didn't seem to be reliable fixes and sounded a little beyond my usual capabilities. Anyone know if this is fixable or do I need to send
the device back?
Thanks!

Not much information here to go on. Can you supply the bdd.log file. Copy to a public share like OneDrive, and share the link.
Typically any problems with format and partition have to do with the storage driver. Are you using the latest ADK from Microsoft? As Surface Pro 2 only supports Windows 8.x, you should *only* be using uEFI mode and GPT.
THe default MDT Task Sequence will do the right thing, *however*, if you change the settings in the "FOrmat and Partition Disk" step, you are then responsible for the settings from then on.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Trying to download and install Photoshop Elements and Premium on Surface Pro 3 from the link and receiving an error - anyone know of a resolution?

I have a Surface Pro 3 and just purchased the download link for Photoshop Elements (newest one) from Adobe. I've tried downloading several times and in 64 and 32 bit types, but have only made it as far as the install before receiving an error. Anyone else have this problem and know of a solution?

Hi Jeff -
I tried chatting with someone earlier today, but they ended the session (I think accidentally?) before it was resolved. My error is below. Now chat seems to be closed - although I thought it was open 24/7, so I can't try that again. This is the most frustrating support experience I've ever had. I just want to access and start using the products I purchased Friday. I would be so happy if someone would just help fix this. I am not computer inept, but cannot figure out why the download is failing.
The guy on chat that was helping me before getting cut off had me run a SCANNOW system scan, but that's where the session unexpectedly ended.
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
ERROR: This installer does not support installation on a 64-Bit Windows operating system. Please download the 64-Bit version of Photoshop Elements.
ERROR: System check returned with error : 6

8620 prints, but then gives error message on Surface Pro 3

This error message has been bothering me for some time. From day one when I print from my Surface Pro 3, I get an error message that my document (doesn't matter what it is) did not print. About 95% of the time, it actually DID print but I get the error message. So whenever I print, I don't actually know if the error message is bogus or not. I've tried uninstalling and reinstalling all of the drivers and apps on my surface, but to no avail. Can anyone help me keep my sanity? Here is an example of the error message from just a little bit ago. Notice the error message in the upper right hand corner. And this "test print" did actually print.

Hi!, Egan1: Welcome, to Forum !. Please, download and run, the HP Print and Scan Doctor from ... www.hp.com/go/tools

8620 prints, but hten gives error message on Surface Pro 3

This error message has been bothering me for some time. From day one when I print from my Surface Pro 3, I get an error message that my document (doesn't matter what it is) did not print. About 95% of the time, it actually DID print but I get the error message. So whenever I print, I don't actually know if the error message is bogus or not. I've tried uninstalling and reinstalling all of the drivers and apps on my surface, but to no avail. Can anyone help me keep my sanity? Here is an example of the error message from just a little bit ago. Notice the error message in the upper right hand corner. And this "test print" did actually print.

Hi!, Egan1: Welcome, to Forum !. Please, download and run, the HP Print and Scan Doctor from ... www.hp.com/go/tools

Surface Errors

Similar Messages

Maybe you are looking for