Shady Drivers...

Well, it was a good try. I converted everything over to run on the down level hardware for my NSE Simulation, which should run on D3D_FEATURE_LEVEL_10_0. When I run it with the reference device everything works well, except for the speed of course. When I try running it on my experimental drivers that I mentioned last time, it renders the initial frame then I get a driver lockup and recovery with the following output on the debug window:

D3D11: Removing Device.
D3D11: ERROR: ID3D11Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). [ EXECUTION ERROR #378: DEVICE_REMOVAL_PROCESS_AT_FAULT ]
The thread 'Win32 Thread' (0x145c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1784) has exited with code 0 (0x0).
First-chance exception at 0x763642eb in LivingBook.exe: Microsoft C++ exception: _com_error at memory location 0x0012f3dc..

That is one heck of an error description if I do say so myself. Since it works fine with the REF device, I'm not sure I can spend too much time looking for something that I'm doing wrong. Has anyone seen anything like this before... My only recourse could be to wait for some actual drivers to come out, which may be never with a Dell laptop [rolleyes]!