Running WinSAT crashes DWM => Fixed in SVN

[Andre.Ziegler]

Hi,

I installed VB4.1.0 on a Windows 7 x64 Sp1, installed a Windows 7 Embedded as Guest and Aero works. But if I leave the PC idle, Windows starts WinSAT to calculate the Experience Index. In this case the DWM.exe crashes:

ChildEBP RetAddr  
0340d6bc 77d46a04 ntdll!KiFastSystemCallRet
0340d6c0 760e6a36 ntdll!ZwWaitForMultipleObjects+0xc
0340d75c 764cbd1e KERNELBASE!WaitForMultipleObjectsEx+0x100
0340d7a4 764cbd8c kernel32!WaitForMultipleObjectsExImplementation+0xe0
0340d7c0 764e05ff kernel32!WaitForMultipleObjects+0x18
0340d82c 764e089a kernel32!WerpReportFaultInternal+0x186
0340d840 764e0848 kernel32!WerpReportFault+0x70
0340d850 764e07c3 kernel32!BasepReportFault+0x20
0340d8dc 77d77f1a kernel32!UnhandledExceptionFilter+0x1af
0340d8e4 77d1e304 ntdll!__RtlUserThreadStart+0x62
0340d8f8 77d1e18c ntdll!_EH4_CallFilterFunc+0x12
0340d920 77d471b9 ntdll!_except_handler4+0x8e
0340d944 77d4718b ntdll!ExecuteHandler2+0x26
0340d968 77d1f96f ntdll!ExecuteHandler+0x24
0340d9f4 77d47017 ntdll!RtlDispatchException+0x127
0340d9f4 0061118c ntdll!KiUserExceptionDispatcher+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
0340dd1c 00612a05 VBoxOGLcrutil+0x1118c
0340dd6c 00612ccb VBoxOGLcrutil+0x12a05
0340dd94 006066c1 VBoxOGLcrutil+0x12ccb
0340ddb8 01e33bda VBoxOGLcrutil+0x66c1
0340dddc 01e3d1c4 VBoxOGLpackspu+0x3bda
0340ddf4 0226da36 VBoxOGLpackspu+0xd1c4
0340de04 0226df67 wined3dwddm+0x6da36
0340de1c 0226e503 wined3dwddm+0x6df67
0340de2c 02236d93 wined3dwddm+0x6e503
0340e21c 02237416 wined3dwddm+0x36d93
0340e22c 0227088e wined3dwddm+0x37416
0340e24c 01371c14 wined3dwddm+0x7088e
0340e264 01371cc2 VBoxD3D9wddm+0x1c14
0340e270 10006af7 VBoxD3D9wddm+0x1cc2
0340eecc 6d62dcce VBoxDispD3D+0x6af7
0340f114 6d630547 D3D10Level9!UMAdapter::CreateUnderlyingAdapter+0x169
0340f29c 6d63066e D3D10Level9!UMAdapter::Open+0xfc
0340f2b4 71c30ba9 D3D10Level9!OpenAdapter10_2+0x2e
0340f530 71c2d0cd dxgi!CUMDAdapter::CUMDAdapter+0x8a7
0340f56c 71c2f2f5 dxgi!CDXGIBaseAdapter::GetUMDAdapter+0x60
0340f65c 703d8027 dxgi!DXGID3D10CreateDevice+0x278
0340f688 70415f34 d3d10_1core!D3D10CoreCreateDevice1+0x53
0340f6bc 6d62c1a3 d3d10_1!D3D10CompleteDeviceCreationForExternalImplementation+0x57
0340f720 704162c3 D3D10Level9!D3D10CreateDeviceExternalImplementation+0x234
0340f988 70416665 d3d10_1!D3D10CreateDeviceAndSwapChain1+0x125
0340f9b4 7048a489 d3d10_1!D3D10CreateDevice1+0x23
0340fa00 7048a373 dwmcore!CD3DDeviceTable::CreateD3DDevice+0x9c
0340fa24 70486209 dwmcore!CD3DDeviceTable::CreateAdapterDevicePair+0x1e
0340fb80 70483c8c dwmcore!CD3DDeviceTable::GetDeviceCapsForAdapter+0x68
0340fbfc 704828e2 dwmcore!CDisplay::ReadGraphicsAccelerationCaps+0x51
0340fc14 70482820 dwmcore!CDisplaySet::ReadGraphicsAccelerationCaps+0x35
0340fc2c 704826c8 dwmcore!CDisplaySet::Init+0xd9
0340fc48 70482504 dwmcore!CDisplayManager::CreateNewDisplaySet+0x93
0340fc98 70486ebf dwmcore!CDisplayManager::DeriveCurrentDisplaySet+0x80
0340fcbc 70442a45 dwmcore!CDisplayManager::GetCurrentDisplaySet+0x3d
0340fcdc 70442923 dwmcore!CDisplayManager::UpdateDisplayState+0x24
0340fd0c 704428be dwmcore!CComposition::ProcessComposition+0x39
0340fd28 70486e16 dwmcore!CComposition::Compose+0x4c
0340fd48 704877a5 dwmcore!CPartitionThread::RenderPartition+0x1e
0340fd6c 70487086 dwmcore!CPartitionThread::Run+0xb4
0340fd84 764ced6c dwmcore!CPartitionThread::ThreadMain+0x1e
0340fd90 77d637f5 kernel32!BaseThreadInitThunk+0xe
0340fdd0 77d637c8 ntdll!__RtlUserThreadStart+0x70
0340fde8 00000000 ntdll!_RtlUserThreadStart+0x1b

[Andre.Ziegler]

Crash dump of DWM

[Andre.Ziegler]

have you looked at the dump?

[misha]

Replying to Andre.Ziegler:

have you looked at the dump?

Sorry for delay, we are investigating the problem currently.

[misha]

We've fixed the issue. Here is the test build that contains the fix, please give it a try: ​http://www.virtualbox.org/download/testcase/VirtualBox-2011-08-04-18-16-04-win-rel-4.1.1-r73333-MultiArch.exe note that you need to update guest additions to make the fix work. Let me know if you need a build for some other non-windows host platform.

[Andre.Ziegler]

ok, can I install this addition over the official Release 4.1?

[Andre.Ziegler]

ok, I installed the new version and ran the VM again and installed the new guest additions.

I ran the WinSAT task from the task scheduler MMC snapin.

After a while the Windows Error Reporting service pops up and showed that WinSAT.exe crashed. When I click close, the VM hangs and exactly at the time when the VM hangs, the virtualbox.exe in my Windows 7 host consumed 50% CPU usage and I can only force the VM to shutdown becasue the VM is complete frozen.

I attached my Vbox.log. But I can't attach (Trac error) the WinSAT crash dump and the dump I created with ProcEx of the virtualbox.exe which hogs my CPU in my host Windows 7.

Any idea?

[misha]

Reproduced another crash with WinSAT, sorry I didn't encounter it before. Will fix and test more thoroughly, and provide you with a test build after that.

[Andre.Ziegler]

Do you need my WinSAT dump?

Also should I create a new ticket for the VM hang and 50% CPU usage issue after WinSAT crashes? You can get a minidump and a xperf trace if needed, I can't see anything because I don't have the Debug files (PDBs).

[misha]

Yes, the WinSAT dump would be very useful to ensure I see the same crash as you do.
I think the 50% CPU issue might related to winsat crash, so let's track it here for now. I'll try to reproduce it locally.

[Andre.Ziegler]

Because I can't attach the larger 7z file, here is the link to my public dropbox:

​http://dl.dropbox.com/u/5749744/VirtualBox_WinSAT_crash.7z

it includes a picture with the 50% usage, a minidump of the virtualbox.exe of my host which consumes the 50% cpu usage, a xperf trace from the virtualbox.exe and the WinSAT crash dump generated by the Windows Error Reporting service from the VM.

I hope this helps.

[misha]

Hmm, the WinSAT.exe.3924.dmp dump file seems corrupt :( , I'm unable to open it with WinDbg here.

[misha]

FYI: in case you're unable to attach a big file here, feel free to mail at me at mikhail dot sennikovsky at oracle dot com and I will post an ftp link where you can upload the file if it is more convenient for you.

[Andre.Ziegler]

it seems that the VM hang corrupted the dump :(

This time I go a smaller dump (which I can open), before the VM freezed again.

I also added the output of winsat formal (Which shows a lot of warnings) which I redirected into a text file.

[Andre.Ziegler]

the 50% CPU issue also happens at normal shutdown and the VM doesn't respond. Have you looked at the xperf trace and the minidump or should I create a new ticket?

[misha]

Replying to Andre.Ziegler:

the 50% CPU issue also happens at normal shutdown and the VM doesn't respond. Have you looked at the xperf trace and the minidump or should I create a new ticket?

I'll try to reproduce it locally, and will look into the xperf trace you provided. No need for the new ticket so far.

[Andre.Ziegler]

ok, 1 note:

I have a quad core AMD CPU and assigned 2 Cores to the VM, so the 50% are caused by the 2 assigned CPUs.

[Andre.Ziegler]

the 50% CPU usage on reboot is also 3D related. If i turn off the Aero Glass I can reboot the VM without any issues.

I hope this helps you.

[Andre.Ziegler]

Hi misha,

any news about it? Was the xperf trace helpful?

[misha]

Yes, here is a new test build that should hopefully solve your problem: ​http://www.virtualbox.org/download/testcase/VirtualBox-2011-08-11-23-12-35-win-rel-4.1.1-r73468-MultiArch.exe let me know how it works for you.

[Andre.Ziegler]

the exe is always corrupted. I tried to download it with Firefox 5, Freedownloadmanger and Chrome. The file is only 41.3 MB :'(

[misha]

oh, sorry let me try it one more time

[Andre.Ziegler]

ok, this time the download works, I need to reboot and next I test the Aero.

[misha]

Replying to Andre.Ziegler:

the exe is always corrupted. I tried to download it with Firefox 5, Freedownloadmanger and Chrome. The file is only 41.3 MB :'(

Re-uploaded the file, please retry downloading again now: just checked, and it works alright here.

[misha]

Note that you need to update guest additions from this package.

[Andre.Ziegler]

Replying to misha:

Note that you need to update guest additions from this package.

Yes, I know this. I installed this build over the older 4.1.1 which caused the "can't access kernel driver issue". I repaired the newer version and now it works.

I updated the Guest Additions and I can run WinSAT without getting a crash and rebooting the VM with Aero Glass enabled works, too.

But I can see that Winsat still shows a lot of warnings:

Wird ausgefhrt: WinSAT Direct3D-Bewertung '-aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' Grafikleistung des Desktops wird bewertet

err:[0xd38]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\state.c 58: Undefined state.

And I can see that VirtualBox uses the IGP instead of my PCIe card (Radeon HD 5770). Can I control which card is used by VB? Because with the IGP, the speed is slower.

00:00:00.942 VBoxSharedClipboard mode: Bidirectional 00:00:01.229 OpenGL Info: Render SPU: GL_VENDOR: ATI Technologies Inc. 00:00:01.229 OpenGL Info: Render SPU: GL_RENDERER: ATI Radeon HD 4250 00:00:01.229 OpenGL Info: Render SPU: GL_VERSION: 3.3.10907 Compatibility Profile Context

Afair I had the IGP disabled last time. I try to disable the IGP and only use the PCIe card and test it again.

[misha]

VBox is using the Graphics card used by your host, the "ATI Radeon HD 4250" actually comes from the glGetString(GL_RENDERER) query on your host.

[misha]

Replying to Andre.Ziegler:

err:[0xd38]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\context.c 1392: Can't find a suitable iPixelFormat err:[0xdb0]:d3d:D:\tinderbox\add\src\VBox\Additions\WINNT\Graphics\Wine\wined3d\state.c 58: Undefined state.

Those warnings are normal, we should and will disable them in the driver, thanks for noting.

[misha]

Anything left for this ticket? Does the guest shutdown work ok now for you as well?

[Andre.Ziegler]

yes, the VM shuts down fine. WinSAT also works fine for the HD 5770.

If you disable all the warnings from the driver I have no issues left. So you can close this ticket.

thanks for the fixed version.

Have a nice weekend misha.

best regards André

[misha]

Disabled those warnings. Thanks a lot for your help in finding the bugs & testing! I'll mark this bug as Fixed in SVN

[Poul Bak]

I can confirm that the bug has been fixed when RUNNING IN A WINDOW.

When running FULLSCREEN Winsat still crashes. So the bug has not been fixed, only reduced!

[Andre.Ziegler]

for me it doesn't crash in Fullscreen. Which host GPU do you use?

[Frank Mehnert]

The fix is contained in VBox 4.1.2. But I will keep this ticket open due to the fullscreen report.

[Poul Bak]

Ok, haven't tried 4.1.2, only 4.1.1 from link above.

My GPU is 'ATI Mobility Radion HD 4650'.

Switching to fullscreen causes bad behaviour for me, not just Winsat. Really wish, you have access to my GPU type (if that's the problem).

[misha]

In case 4.1.2 does not solve your problem, please create a dump for your crash. You can do it the following way:

1. You need to install Debugging Tools for Windows available at ​http://www.microsoft.com/whdc/devtools/debugging/default.mspx
2. Install the latest VBox 4.1.2 available at ​http://www.virtualbox.org/wiki/Downloads and update guest additions to 4.1.2
3. Start winsat
4. Open elevated console window (Start->All Programs->Accessories->righ click "Command line" and select "Run As Administrator").
5. In the console window cd to Debugging tools installation dir and run the following command from there:

adplus.exe -crash -pn WinSAT.exe -o c:\dumps -MiniOnSecond -NoDumpOnFirst If run successfully, this should print a destination directory inside the c:\dumps, where logs/dumps for winsat process will be placed.
Note: You could specify/use any directory instead of "c:\dumps" in the command above as well.

6. Once winsat crashes please zip/rar the contents of logs/dumps directory specified in step 5 and post me the archive at mikhail dot sennikovsky at oracle dot com for investigation.

[misha]

copy-paste is evil :) please see the corrected instructions in my previous comment

[Andre.Ziegler]

@ misha

starting with Vista Sp1 you can use the Windows Error Reporting service to generate dumps:

​http://cid-128fc518635be2dc.office.live.com/self.aspx/.Public/MS%20Foren/Registry/LocalDumps.reg

this reg file forces Windows to generate Fulldumps of all crashing apps and the dumps are stored into C:\localdumps. Changing the value DumpType to 1 generates Minidumps.

But I have 1 issue left which doesn't fit to this issue. The UAC prompt causes the display to be come black when using the VM in fullscreen. But based on the comments in the Beta forum, this happens since the first 4.1 Beta.

[misha]

Replying to Andre.Ziegler:

@ misha

starting with Vista Sp1 you can use the Windows Error Reporting service to generate dumps:

​http://cid-128fc518635be2dc.office.live.com/self.aspx/.Public/MS%20Foren/Registry/LocalDumps.reg

this reg file forces Windows to generate Fulldumps of all crashing apps and the dumps are stored into C:\localdumps. Changing the value DumpType to 1 generates Minidumps.

Thanks a lot for the info!
poulbak: so you even do NOT need to install debugging tool for windows, just apply the .reg file as Andre.Ziegler suggests and the crash dump files will be placed in C:\localdumps dir.

But I have 1 issue left which doesn't fit to this issue. The UAC prompt causes the display to be come black when using the VM in fullscreen. But based on the comments in the Beta forum, this happens since the first 4.1 Beta.

Yes, I'm aware of this issue, however none of us here can reproduce it :( We will look into this issue once again. Meanwhile could you attach here a log file for a VM that exposed this issue?

[Andre.Ziegler]

ok, I added the log. The black screen only occurs in full screen, not if I run the VM in a normal Window.

[Poul Bak]

Good news and bad news. Installed 4.1.2 with 3D

My first attempt to run Winsat failed, no crash (so no crash dump), just a no good error message, not even anything in Windows eventlog.

Second attempt: I managed to make an index, no errors at all, BOTH in a window and in fullscreen!

Now the bad news: The actual index for 3D is 2.4 !!! It's 6.7 on the host !!! That's very poor performance in my view and can easily explain all the flicker I experience. But that is probably another bug report.

To Andre.Ziegler: That's exactly, what I see, too, and what I wrote about in beta forum. Also, the VBox menu disappears in fullscreen and WMP doesn't show videos, same reason, I guess.

Don't know, but this seems to be an ATI only problem. May be you could get hold of an ATI card?

[Poul Bak]

Another observation: I ran dxdiag successfully (with old 3D, it failed). I noticed, it said: 'Acceleration of AGP structure: Not present' On the host, it says: Activated. Don't know, can that explain the bad performance?

[misha]

Ok, I'll try to get on this fullscreen issue. As for the 'Acceleration of AGP structure: Not present', this is right that it should not be present in guest.

[Andre.Ziegler]

@misha

which graphic cards do you use? We both have ATI/AMD cards. And yes, the score is also low for me. VMWare Player has 6.0 has graphic score.

[misha]

Replying to Andre.Ziegler: You're right I mostly used NVIDIA cards for testing recently, going to try it on ATI.

[Andre.Ziegler]

ok. Hopefully you can can reproduce and fix it.

[Poul Bak]

I too am glad, you get your hands on an ATI card, it's hard to describe with words, what we see. At least it seems, we have got rid of the crashes, so now crash dumps and logs don't do much good, you have to see it yourself.

[Leonid Lobachev]

Andre.Ziegler could you disable 2d acceleration and check if that fixes issue with black screen in fullscreen mode after uac prompt?

[Andre.Ziegler]

Replying to leonid:

Andre.Ziegler could you disable 2d acceleration and check if that fixes issue with black screen in fullscreen mode after uac prompt?

I updated the ATI driver to 10.8 and now, the UAC prompt is not shown, but I can see the Desktop. The blackscreen is gone. To continue, I have to press CTRL+Alt+Del to get the taskmgr on my host running. Now in windowed mode I can see the UAC prompt which I can accept.

I tested it without 2D and it makes no difference.

[Andre.Ziegler]

If I move a Windows inside the VM, the screen gets corrupted. I attach a picture.

[Poul Bak]

Replying to Andre.Ziegler:

I updated the ATI driver to 10.8 and now, the UAC prompt is not shown, but I can see the Desktop. The blackscreen is gone. To continue, I have to press CTRL+Alt+Del to get the taskmgr on my host running. Now in windowed mode I can see the UAC prompt which I can accept.

I tested it without 2D and it makes no difference.

I can confirm this behaviour, with or without 2d enabled !

[Leonid Lobachev]

Please check test build available at ​http://www.virtualbox.org/download/testcase/VirtualBox-2011-08-23-14-20-24-win-4.1-rel-4.1.3-r73626-MultiArch.exe to see if it solves your issue.

[Poul Bak]

Uninstalled VBox, installed 4.1.3, updated guest additions with 3D

Sorry, but I see absolutely no difference (and Windows Experience Index agrees with me)

I have set the UAC to not show the secure desktop. When I tried to set it back to default and launched an application as admin, not only the guest, but also the host froze. Ctrl-Alt-Del and Cancel did not work. Ctrl-Alt-Del and show taskmanager: The screen (ON HOST) was black, but now I could see the VBox menu (FROM GUEST). Had to kill the guest process from task manager.

I have attached a screenshot of this

This is not a keeper!

[Poul Bak]

Frozen host screen with bleeding guest

[Andre.Ziegler]

4.1.3 also doesn't fix it.

Also now WinSAT shows the videos. On my native Windows the videos are never shown.

After WinSAT finished I get the blackscreen again. I also have a large flickering with Aero Glass enabled.

In Windowed mode everything works.

And of course I mean Catalyst 11.8.

[Fred Houweling]

I have guest stability issues too on a Fedora 15 host with a Win 7 guest all 64 bit versions. Very keen to get it all fixed and more stable. Please let me know if I can provide any information. VBox 4.1.2 r73507 Intel 960 3.2 GHz, 24 gig ram, raid 6. Thank you.

[Poul Bak]

Replying to FredH: Do you also have an ATI card?

[Fred Houweling]

No, it's a NVIDIA GEFORCE GTX 550 Ti 1GB I'll attache a dmesg output if you like.

[Fred Houweling]

VBox.log for Fred Houweling's Virtual Box install.

[Andre.Ziegler]

Any news?