<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic IDirect3DSurface9::LockRect() returning 88760827 (D3DERR_DRIVERINTERNALERROR) in Developing Games on Intel Graphics</title>
    <link>https://community.intel.com/t5/Developing-Games-on-Intel/IDirect3DSurface9-LockRect-returning-88760827-D3DERR/m-p/915750#M708</link>
    <description>Hi - When using DX9 Surfaces on XPPro with DG33TL motherboard (G33) and latest GFX drivers (14.32.3.64.4906), IDirect3DSurface9::LockRect() will sometimes return 88760827 - D3DERR_DRIVERINTERNALERROR. We use the D3DSurface9 to display bitmaps at 30 fps with: BeginScene() GetBackBuffer() LockRect() CopyMemory() UnlockRect() StretchRect() EndScene() Present() The code works with other graphics adapters and usually works with the G33. However, sometimes the G33 will fall over with the 88760827 error. Why does the driver return "internal error" from LockRect? How can I prevent this? Destroying the d3d device and surface, then recreating them doesn't fix the problem. It seems that the driver is hanging on to objects or getting into bad state that can't be recovered from. // Thanks, // J</description>
    <pubDate>Thu, 28 Feb 2008 02:11:18 GMT</pubDate>
    <dc:creator>eomewrk</dc:creator>
    <dc:date>2008-02-28T02:11:18Z</dc:date>
    <item>
      <title>IDirect3DSurface9::LockRect() returning 88760827 (D3DERR_DRIVERINTERNALERROR)</title>
      <link>https://community.intel.com/t5/Developing-Games-on-Intel/IDirect3DSurface9-LockRect-returning-88760827-D3DERR/m-p/915750#M708</link>
      <description>Hi - When using DX9 Surfaces on XPPro with DG33TL motherboard (G33) and latest GFX drivers (14.32.3.64.4906), IDirect3DSurface9::LockRect() will sometimes return 88760827 - D3DERR_DRIVERINTERNALERROR. We use the D3DSurface9 to display bitmaps at 30 fps with: BeginScene() GetBackBuffer() LockRect() CopyMemory() UnlockRect() StretchRect() EndScene() Present() The code works with other graphics adapters and usually works with the G33. However, sometimes the G33 will fall over with the 88760827 error. Why does the driver return "internal error" from LockRect? How can I prevent this? Destroying the d3d device and surface, then recreating them doesn't fix the problem. It seems that the driver is hanging on to objects or getting into bad state that can't be recovered from. // Thanks, // J</description>
      <pubDate>Thu, 28 Feb 2008 02:11:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Developing-Games-on-Intel/IDirect3DSurface9-LockRect-returning-88760827-D3DERR/m-p/915750#M708</guid>
      <dc:creator>eomewrk</dc:creator>
      <dc:date>2008-02-28T02:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: IDirect3DSurface9::LockRect() returning 88760827 (D3DERR_DR</title>
      <link>https://community.intel.com/t5/Developing-Games-on-Intel/IDirect3DSurface9-LockRect-returning-88760827-D3DERR/m-p/915751#M709</link>
      <description>It might be a driver bug... though I would think that you'd want to only do the StretchRect() between the BeginScene()/EndScene() pair. See if that doesn't help the driver behave any better...
&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Apr 2008 20:19:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Developing-Games-on-Intel/IDirect3DSurface9-LockRect-returning-88760827-D3DERR/m-p/915751#M709</guid>
      <dc:creator>wedamon</dc:creator>
      <dc:date>2008-04-29T20:19:02Z</dc:date>
    </item>
  </channel>
</rss>

