OS name: Windows 7, version: 6.1 build 7601, 64 bit, platform id: 2, service pack: Service Pack 1ĭisplay Device 0 name: \\.\DISPLAY1, context: NVIDIA GeForce GTX 770, primary: yes, mirroring: noĭisplay Device 1 name: \\.\DISPLAY2, context: NVIDIA GeForce GTX 770, primary: no, mirroring: noĭisplay Device 2 name: \\.\DISPLAY3, context: NVIDIA GeForce GTX 770, primary: no, mirroring: noĭisplay Device 3 name: \\.\DISPLAY4, context: NVIDIA GeForce GTX 770, primary: no, mirroring: noĭisplay Device 4 name: \\.\DISPLAYV1, context: RDPDD Chained DD, primary: no, mirroring: yesĭisplay Device 5 name: \\.\DISPLAYV2, context: RDP Encoder Mirror Driver, primary: no, mirroring: yesĭisplay Device 6 name: \\.\DISPLAYV3, context: RDP Reflector Display Driver, primary: no, mirroring: yesĭisplay Adapter Name: NVIDIA GeForce GTX 770ĭisplay Adapter DeviceID: VideoController1ĭisplay Adapter VideoProcessor GeForce GTX 770ĭisplay Adapter VideoModeDescription: 1680 x 1050 x 4294967296 colors Process path: C:\Program Files (x86)\Oculus\Tools\OculusConfigUtil.exe Hmd Caps: 280, Hmd Service Caps: 280, Latency test active: no, Last frame time: 0.000000, Last get frame time: 0.000000, Rendering configred: no, Begin frame called: no, Begin frame thread id: 0x00000000 HMD 0: Type: 6 ProductName: Oculus Rift DK2, Manufacturer: Oculus VR VendorId: 10291, ProductId: 33, SerialNumber: 203NM703FVQ5, FirmwareMajor: 2, FirmwareMinor: 12, Resolution: 1920x1080, DisplayDeviceName:, DisplayId: -1 A user would just have to be careful not to accidentally move a 3D video file to the wrong directory, because that will crash the computer.Įxception report file: C:\Users\Harolddd\AppData\Roaming\Exception Report ( 04.17.42).txtĮxception minidump file: C:\Users\Harolddd\AppData\Roaming\Exception Minidump ( 04.17.42).mdmpĮxception instruction address: 0圆78acf60 (see callstack below)Įxception description: ACCESS_VIOLATION writing address 0x00000000 Until Microsoft fixes their bug, my only option is to keep all 3D video files in special directories that don't use thumbnails. It is of course too difficult to install the update for Oculus Rift and then uninstall it when I want to work with stereoscopic video. I tried the demo scene and got an instant crash, as expected. Why has Microsoft not fixed this major bug!?įollow up. Will avoidance of KB2670838 cause problems for the Oculus Rift? I only recently learned that KB2670838 is DirectX 11.1 and is even suggested as required by MaxVR. If they don't already know about this bug, they won't know why their computer is crashing and they'll think it is because of the Rift. So why is this a problem for Oculus? Because Oculus Rift users are likely to view SBS stereoscopic videos. Windows automatically reinstalls it, so you have to turn off auto update. Rather than get rid of my stereo video files, I uninstalled KB2670838. :evil: It has been called the "evil update." :evil: It goes into a memory leak that can't be stopped if you browse a directory, showing thumbnails, that contains SBS (stereoscopic) mp4 video. After some searches I learned that it is the Windows update KB2670838. I thought I had a virus, so I wiped my computer clean and re-installed everything. I found there was a process running out of control (dllhost.exe) and using all the memory until the system crashed. About a year ago my Win7 desktop started crashing. I do stereo photography and stereo video. I've been a stereoscopic imaging enthusiast for decades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |