Jump to content

Image of the Day

#QuestOfDungeons is an old-fashioned dungeon crawler. #ScreenshotSaturday  #PS4share

https://t.co/1mztLegxeN https://t.co/DpYimg3MZb
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net's newsletters to receive the latest updates and exclusive content.


Sign up now

D3D11: Removing Device

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
2 replies to this topic

#1 70780533   Members   

128
Like
0Likes
Like

Posted 12 December 2012 - 12:59 AM

hi, when porting my game frome Windows 8 Store App to WindowsPhone 8, I encounter a error:
D3D11: Removing Device.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DB64.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DFA0.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148E0DC.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DB64.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DFA0.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148E0DC.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DB64.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DFA0.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148E0DC.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DB64.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DFA0.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148E0DC.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DB64.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DFA0.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148E0DC.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DA34.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: _com_error at memory location 0x0148DF2C.
First-chance exception at 0x77BD277C in TaskHost.exe: Microsoft C++ exception: Platform::COMException ^ at memory location 0x0148E008. HRESULT:0x887A0005

Call GetDeviceRemovedReason(), the return value is DXGI_ERROR_DEVICE_REMOVED
besides, I use Windows Phone 8 emulator.

Attached Thumbnails

  • 1354186560_6018.png


#2 MJP   Moderators   

19023
Like
1Likes
Like

Posted 12 December 2012 - 01:43 PM

This generally means that the display driver crashed or hung, and you got a TDR. This can be from something simple, like a draw call with a shader that uses a shader with a really long loop that takes so long that the drive times out. Or it might be from a bug in the driver itself. Or it could even be something in the emulator. The best advice I can give is to start removing bits of code until you can narrow it down further.

#3 70780533   Members   

128
Like
0Likes
Like

Posted 12 December 2012 - 08:32 PM

thank you for your reply, MJP.
This error occurs when game init, ID3D11Device create many render states, textures, and shaders and all this is done in one game update. The error occurs some times at creating render states, some times at creating textures.




Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.