Frequent Random Pauses/Freezes

[null4end]

Also, disabling HW Acceleration in Office didn't help...

 

[drolem]

Look in the event viewer to see if the CPU is throttled by FW when these freezes are happening.

 

[unruledboy]

1. check disk for integrity problems (including sd card if u r using one)
2. scan for virus
3. kill all apps or use safe mode to observe
4. if all above do not work, system recovery and see.

 

[null4end]

Figured out that it is tied to the following:
Event 129 - storahci
Reset to device, \Device\RaidPort0, was issued.

Researching causes and fixes now...

 

[ctitanic]

Figured out that it is tied to the following:
Event 129 - storahci
Reset to device, \Device\RaidPort0, was issued.

Researching causes and fixes now...

Please report back on this.

 

[null4end]

Sorry it has been a while since I posted... The freeze coincides with an storahci warning in the System log. The message is: "Reset to device, \Device\RaidPort0, was issued.

I've removed my SD card for now and I will do a diskchk.

 

[null4end]

Got a freeze and warning in the log with the SD removed, chkdsk /r didn't find any bad errors but it did cleanup some index entries. Waiting to see if it happens again now.

------------ Log from chkdsk /r -----------------------

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
270848 file records processed. File verification completed.
4441 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
344986 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 2112 unused index entries from index $SII of file 0x9.
Cleaning up 2112 unused index entries from index $SDH of file 0x9.
Cleaning up 2112 unused security descriptors.
Security descriptor verification completed.
37070 data files processed. CHKDSK is verifying Usn Journal...
39793928 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
270832 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
11655905 free clusters processed. Free space verification is complete.

Windows has made corrections to the file system.
No further action is required.

118553599 KB total disk space.
71428744 KB in 162556 files.
117828 KB in 37071 indexes.
0 KB in bad sectors.
383403 KB in use by the system.
65536 KB occupied by the log file.
46623624 KB available on disk.

4096 bytes in each allocation unit.
29638399 total allocation units on disk.
11655906 allocation units available on disk.

Internal Info:
00 22 04 00 55 0a 03 00 0b ea 05 00 00 00 00 00 ."..U...........
cb 01 00 00 e9 09 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[null4end]

I am optimistic that I have it fixed but reinstalling the SATA driver. In an effort to jinx myself, here are the steps I followed:

1. Download and unzip "Surface Pro 3 - June 2014" driver pack from Microsoft.
2. Uninstalled Intel 8 Series SATA AHCI Controller from Device Manager (check the option to delete the driver)
3. Reboot and let Windows use the default driver
4. After the reboot, open Device Manager and right click on the controller (should show generic driver name) and chose Update Driver Software
5. Click to Browse my computer
6. Browse the to "Intel\SATA_AHCI\9.4.0.1023" directories in the unzipped driver pack
7. Next, Finish etc to instal the driver
8. Reboot and hopefully enjoy

 

[null4end]

The jinx worked. Still having the issue today. I am working with MS Support now and it looks like it may end up being a warranty issue.

 

[cdf3]

I was scrolling past your thread, and said to myself "good thing I don't have that issue".
Left my Surface Pro running to go do something. When I came back, the keyboard didn't work.
I did my usual, disconnect and reconnect the keyboard. Still didn't work.
Touched the screen, and noticed it wasn't responding as well.
Did a force reboot by holding down the Power & Volume Down Button.
Hoping this isn't an on going issue.

 

[null4end]

Mine always comes back in about 30 seconds and there is a corresponding warning in the System log in Event Viewer.

 

[null4end]

In the middle of a Windows 8 reinstall now. It wouldn't be so bad if I didn't have to re-upgrade to Enterprise and rejoin the domain.

Thankfully my company provides a nice tool to take care of both steps, but it still takes a while.