Defrag 006: Troubleshooting Windows 7, Outlook Crash, SSD speeds

Why don't you release the public striped out PDBs for Office? Without them we can't use WinDbg to debug crashes or use xperf to trace slowness.

and the same procedure like every show again. Use xperf to trace the slow IO operations. The ntdebugging team made a video about it:

http://blogs.msdn.com/b/ntdebugging/archive/2009/08/17/xperf-to-investigate-slow-i-o-issues.aspx

My WindowsUpdate problem is still not solved

http://channel9.msdn.com/Forums/TechOff/WindowsUpdate-problem

@ZippyV

the NTFS trasnaction manager is broken. Delete all files (*.*) from C:\Windows\System32\config\TxR, next run

fsutil resource setautoreset true C:\

and you're fine again.

best regards
André

Another very good and interesting show, thanks.

Thanks for putting this video together! Outlook crashing is definitely one of the more frustrating troubleshooting issues that can happen around the office. Are you planning to do weekly Q&A’s to address more of these Windows problems?

Around 7;30 or so, it was mentioned that EASY TRANFER works for Win7 x86?  I want to save the files from x64, and ET won't load.  Any solution available?  (Using Acronis Image, but that's a hassle in itself)

Thanks.

18 hours ago

@ZippyV

the NTFS trasnaction manager is broken. Delete all files (*.*) from C:\Windows\System32\config\TxR, next run

fsutil resource setautoreset true C:\

and you're fine again.

best regards
André

SOLVED, you are my hero.

4 hours ago, ZippyV wrote

SOLVED, you are my hero.

nice to hear this

21 hours ago, RhymesWith​Orange wrote

@MagicAndre1981:

there must be a good reason why they are not available. The best I can do is inquire and update here.

can you ask this please? I asked it in the German and English Technet forums and never got an answer.

I have a question to you. My German Windows 7 Sp1 x64 displays "Resume Windows" when I get back from Hibernation instead of "Windows wird fortgesetzt" which expect on my German Windows. The language is set in BCD to German:

Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {current}
resumeobject            {386d7f0d-3735-11e0-9054-da9937c8e486}
displayorder            {current}
                        {386d7f13-3735-11e0-9054-da9937c8e486}
                        {386d7f14-3735-11e0-9054-da9937c8e486}
                        {386d7f19-3735-11e0-9054-da9937c8e486}
                        {386d7f16-3735-11e0-9054-da9937c8e486}
                        {d3dce997-7447-41fc-9740-a8d20ee3bf55}
toolsdisplayorder       {memdiag}
timeout                 30
displaybootmenu         Yes

Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate (x64)
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {386d7f0f-3735-11e0-9054-da9937c8e486}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {386d7f0d-3735-11e0-9054-da9937c8e486}
nx                      OptIn

I checked the "C:\Windows\System32\de-DE\winresume.exe.mui" and "C:\Windows\System32\Boot\de-DE\winresume.exe.mui" and the included Resume.xsl is German, too.

Any ideas?

André

this is a great site i have learned alot

RhymesWith​Orange wrote

@MagicAndre1981:

I will check and answer in this thread.

ok.

I solved the resume text issue by removing hotfix KB2519400. I accidentally applied it to my desktop.

2 days ago, RhymesWith​Orange wrote

Ok, so I found out why, and you won't really like the answer... the long and the short of it is that it isn mired in red tape at this point. Yes there has been requests, but none have been so great as to actually warrent the work involved to publish public symbols. It seems to get investigated around every release, and then gets depriortized against the other work. We can only hope at this point that it will happen in the future.

Hi Gov,

I don't like the information, but I like that I now finally got an answer. It is always better to say, "you don't get the debug symbols" instead of never replying again. If the next Beta program starts, I ask this again on connect. Maybe they offer them at this time.

So thanks for your effort to ask. And have a nice weekend.

best regards

André

ok

I have 2 other things I want to ask. Running xbootmgr with the DRIVERS trace flag sometime causes a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) bug check in Windows 7. Hotfix available?

The next thing is an issue which was closed from the German MS support without a real answer. What prevents Windows to release the paged pool MmSt memory? I ran xperf with Pool tracing and stackwalk PoolAlloc. This shows me that FindFirstFileW or the MiAddViewsForSection allocate the Memory. But why is the allocated memory never freed? This happens when running a 3rd party search tool which updates the index and other tools like TortoiseSVN, TortoiseHg, TortoiseGit. So sometimes I have over 1 GB paged pool usage. The strange thing is that hibernating Windows frees the memory. I used xbootmgr with POOL and stackwalk PoolFree to verify this. So why is the memory freed at hibernation and not at normal work?

Any ideas?

http://truc7g.sn2.livefilestore.com/y1psUQk2zY_S8RYHqQadkvscEAHwRgGBdDUDSoprrxhUvObmpBKlSRB9bDYxaXWanKqGWgdbQKDKwriz498Gpu-GVVT7XC_f2_U/xperf_AOFO_paged_Mmst_NTFS_ntkrpamp_MiAddViewsForSection.png

where can I upload all things?

http://cid-128fc518635be2dc.office.live.com/browse.aspx/xbootmgr^_bugcheck

hibernation doesn't work any longer so I can't give you the free trace

I only get a blinking cursor. chkdsk repaired issues and I recreated the hibernation file with powercfg but it still fails. System restore to 2 days ago where everything works also doesn't sove it. Damn Windows hype. I want my stable Vista back

ok, the hibernation works again but extremely slowly.

the ACPI driver takes 70s to resume:

<resumedevices start="630284439" duration="70791941">
<device start="630284750" duration="70420610" name="ACPI_HAL\PNP0C08\0">
  <driver start="630284759" duration="70420591" name="\Driver\ACPI" /> 

Any ideas why? I had this last year and it has suddenly gone and hibernation was fast again. But now it suddenly came back

RhymesWith​Orange wrote

Have you updated the BIOS recently?

no, I have send my PC to hibernation at the evening, and next day when I came back home and tried to resume, the resume failed completely. I checked the HDD with chkdsk and now hibernation works again, but slowly. So I made the xbootmgr trace and saw this ACPI issue.

The same thing happened last year for me. Hibernation worked and suddenly it was extremely slow, so I made the trace and also saw the ACPI issue. The next months I turn the PC off by making a shutdown. Some day I made an mistake and send the PC to hibernation and it suddenly worked again. Now the ACPI issue is back for an unknown reason. BIOS reset, uninstalling the driver from device manager doesn't fix it. I talked to the ASRock support last year and they also have no idea (they never heard about xbootmgr and how to use it)..

any new ideas about the ACPI issue?

I also have a performance issue with IE9. Loading a XML file with IE9 is extremely slow:

I looged a bug during IE9 development on connect, but it was closed. I reopened it and attached a xperf trace but no response.

Can you look at this?

Wow we really are slow compared to hardware.

If the first email can crash your email app. Or a font cant do the same.

It is a sad state for software. I guess the great apes making hardware are holding their end up and the great apes making software are all over the place.

How about software get their act together. How much duplication do you want before stupid people look at you and go come on ?