Houdini crashes on start
up vote
0
down vote
favorite
Unable to start Houdini on Windows 10 Home and Nvidia GeForce 770 because of a crash.
Crash Window says:
Houdini Console 7272: Fatal error: Segmentation fault Saving
application data to ....hipnc
Inside the crash log there is a text
Crash report from Соня; Houdini FX Version 17.0.352 [windows-x86_64-cl19.15]
Uptime 0 seconds
Fri Nov 30 17:20:18 2018
Caught signal 11
Traceback from 4620 ThreadId=0x000003d8
CURRENT THREAD 984
+0x78640819 [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862c4a7 C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7867ceda [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862d10e [clGetPlatformIDs] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x786341e9 [clEnqueueTask] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x88e432b5 [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0x88e0c85b [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0xd0ea10c8 C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea302b [clWaitForEvents] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea293c [clGetPlatformIDs] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0x230fc18a [cl::Platform::get] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x230fdba2 [CE_Context::getDevices] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x10765f32 [FUSE_PrefDialog::setOpenCLDevice] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d67f6 [FUSE_App::restoreApplicationState] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d33eb [FUSE_App::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x10ca1be0 [OPUI_MainApp::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibOPUI.dll
+0x109bc7b5 [AP_Interface::loadWindowGeometry] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x109bd25d [myWinMain] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x40001b9a C:Program FilesSide Effects SoftwareHoudini 17.0.352binhoudini.exe
+0xe7be3034 [BaseThreadInitThunk] C:WindowsSystem32KERNEL32.DLL
+0xe8661471 [RtlUserThreadStart] C:WindowsSYSTEM32ntdll.dll
igdrclneo64.dll points to Intel Graphics, which is present in the system, but the monitor is plugged into discrete NVidia card.
What can be the reason?
windows-10 graphics-card crash houdini
edited Nov 30 at 14:58
Ramhound
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
add a comment |
up vote
0
down vote
favorite
Unable to start Houdini on Windows 10 Home and Nvidia GeForce 770 because of a crash.
Crash Window says:
Houdini Console 7272: Fatal error: Segmentation fault Saving
application data to ....hipnc
Inside the crash log there is a text
Crash report from Соня; Houdini FX Version 17.0.352 [windows-x86_64-cl19.15]
Uptime 0 seconds
Fri Nov 30 17:20:18 2018
Caught signal 11
Traceback from 4620 ThreadId=0x000003d8
CURRENT THREAD 984
+0x78640819 [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862c4a7 C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7867ceda [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862d10e [clGetPlatformIDs] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x786341e9 [clEnqueueTask] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x88e432b5 [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0x88e0c85b [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0xd0ea10c8 C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea302b [clWaitForEvents] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea293c [clGetPlatformIDs] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0x230fc18a [cl::Platform::get] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x230fdba2 [CE_Context::getDevices] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x10765f32 [FUSE_PrefDialog::setOpenCLDevice] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d67f6 [FUSE_App::restoreApplicationState] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d33eb [FUSE_App::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x10ca1be0 [OPUI_MainApp::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibOPUI.dll
+0x109bc7b5 [AP_Interface::loadWindowGeometry] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x109bd25d [myWinMain] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x40001b9a C:Program FilesSide Effects SoftwareHoudini 17.0.352binhoudini.exe
+0xe7be3034 [BaseThreadInitThunk] C:WindowsSystem32KERNEL32.DLL
+0xe8661471 [RtlUserThreadStart] C:WindowsSYSTEM32ntdll.dll
igdrclneo64.dll points to Intel Graphics, which is present in the system, but the monitor is plugged into discrete NVidia card.
What can be the reason?
windows-10 graphics-card crash houdini
edited Nov 30 at 14:58
Ramhound
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Unable to start Houdini on Windows 10 Home and Nvidia GeForce 770 because of a crash.
Crash Window says:
Houdini Console 7272: Fatal error: Segmentation fault Saving
application data to ....hipnc
Inside the crash log there is a text
Crash report from Соня; Houdini FX Version 17.0.352 [windows-x86_64-cl19.15]
Uptime 0 seconds
Fri Nov 30 17:20:18 2018
Caught signal 11
Traceback from 4620 ThreadId=0x000003d8
CURRENT THREAD 984
+0x78640819 [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862c4a7 C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7867ceda [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862d10e [clGetPlatformIDs] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x786341e9 [clEnqueueTask] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x88e432b5 [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0x88e0c85b [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0xd0ea10c8 C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea302b [clWaitForEvents] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea293c [clGetPlatformIDs] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0x230fc18a [cl::Platform::get] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x230fdba2 [CE_Context::getDevices] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x10765f32 [FUSE_PrefDialog::setOpenCLDevice] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d67f6 [FUSE_App::restoreApplicationState] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d33eb [FUSE_App::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x10ca1be0 [OPUI_MainApp::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibOPUI.dll
+0x109bc7b5 [AP_Interface::loadWindowGeometry] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x109bd25d [myWinMain] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x40001b9a C:Program FilesSide Effects SoftwareHoudini 17.0.352binhoudini.exe
+0xe7be3034 [BaseThreadInitThunk] C:WindowsSystem32KERNEL32.DLL
+0xe8661471 [RtlUserThreadStart] C:WindowsSYSTEM32ntdll.dll
igdrclneo64.dll points to Intel Graphics, which is present in the system, but the monitor is plugged into discrete NVidia card.
What can be the reason?
windows-10 graphics-card crash houdini
edited Nov 30 at 14:58
Ramhound
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
Unable to start Houdini on Windows 10 Home and Nvidia GeForce 770 because of a crash.
Crash Window says:
Houdini Console 7272: Fatal error: Segmentation fault Saving
application data to ....hipnc
Inside the crash log there is a text
Crash report from Соня; Houdini FX Version 17.0.352 [windows-x86_64-cl19.15]
Uptime 0 seconds
Fri Nov 30 17:20:18 2018
Caught signal 11
Traceback from 4620 ThreadId=0x000003d8
CURRENT THREAD 984
+0x78640819 [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862c4a7 C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7867ceda [clGetKernelSubGroupInfoKHR] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x7862d10e [clGetPlatformIDs] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x786341e9 [clEnqueueTask] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eigdrclneo64.dll
+0x88e432b5 [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0x88e0c85b [clEnqueueWriteBufferRect] C:WindowsSystem32DriverStoreFileRepositoryigdlh64.inf_amd64_250db833a1cd577eIntelOpenCL64.dll
+0xd0ea10c8 C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea302b [clWaitForEvents] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0xd0ea293c [clGetPlatformIDs] C:Program FilesSide Effects SoftwareHoudini 17.0.352binOpenCL.dll
+0x230fc18a [cl::Platform::get] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x230fdba2 [CE_Context::getDevices] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibCE.dll
+0x10765f32 [FUSE_PrefDialog::setOpenCLDevice] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d67f6 [FUSE_App::restoreApplicationState] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x106d33eb [FUSE_App::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibFUSE.dll
+0x10ca1be0 [OPUI_MainApp::initApplication] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibOPUI.dll
+0x109bc7b5 [AP_Interface::loadWindowGeometry] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x109bd25d [myWinMain] C:Program FilesSide Effects SoftwareHoudini 17.0.352binlibSI.dll
+0x40001b9a C:Program FilesSide Effects SoftwareHoudini 17.0.352binhoudini.exe
+0xe7be3034 [BaseThreadInitThunk] C:WindowsSystem32KERNEL32.DLL
+0xe8661471 [RtlUserThreadStart] C:WindowsSYSTEM32ntdll.dll
igdrclneo64.dll points to Intel Graphics, which is present in the system, but the monitor is plugged into discrete NVidia card.
What can be the reason?
windows-10 graphics-card crash houdini
windows-10 graphics-card crash houdini
edited Nov 30 at 14:58
Ramhound
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
edited Nov 30 at 14:58
Ramhound
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
edited Nov 30 at 14:58
Ramhound
19.5k156084
edited Nov 30 at 14:58
Ramhound
19.5k156084
edited Nov 30 at 14:58
Ramhound
19.5k156084
19.5k156084
asked Nov 30 at 14:41
Dims
2,91043107177
asked Nov 30 at 14:41
Dims
2,91043107177
asked Nov 30 at 14:41
Dims
2,91043107177
2,91043107177
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55
add a comment |
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
I contacted with Houdini dev.
Email:
It looks like you have an Intel OpenCL driver installed and somehow this driver is corrupted and causing a crash as soon as it gets queried or loaded in any way.
Some laptops come with Intel HD graphics as the default, low-end graphics adapter, and also an NVIDIA card for performance graphics
To temporarily disable the OpenCL driver, you can try running regedit and editing the Windows registry. I believe the key you're looking for is: SOFTWAREKhronosOpenCLVendors. Within that there should be keys for the NVIDIA driver and the Intel driver. If you remove the Intel key that should mean that the faulty Intel OpenCl driver won't try to load.
I followed the way that delete Intel key. And It worked.
May it help you.
Sorry about by bad English.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I contacted with Houdini dev.
Email:
It looks like you have an Intel OpenCL driver installed and somehow this driver is corrupted and causing a crash as soon as it gets queried or loaded in any way.
Some laptops come with Intel HD graphics as the default, low-end graphics adapter, and also an NVIDIA card for performance graphics
To temporarily disable the OpenCL driver, you can try running regedit and editing the Windows registry. I believe the key you're looking for is: SOFTWAREKhronosOpenCLVendors. Within that there should be keys for the NVIDIA driver and the Intel driver. If you remove the Intel key that should mean that the faulty Intel OpenCl driver won't try to load.
I followed the way that delete Intel key. And It worked.
May it help you.
Sorry about by bad English.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
add a comment |
up vote
1
down vote
I contacted with Houdini dev.
Email:
It looks like you have an Intel OpenCL driver installed and somehow this driver is corrupted and causing a crash as soon as it gets queried or loaded in any way.
Some laptops come with Intel HD graphics as the default, low-end graphics adapter, and also an NVIDIA card for performance graphics
To temporarily disable the OpenCL driver, you can try running regedit and editing the Windows registry. I believe the key you're looking for is: SOFTWAREKhronosOpenCLVendors. Within that there should be keys for the NVIDIA driver and the Intel driver. If you remove the Intel key that should mean that the faulty Intel OpenCl driver won't try to load.
I followed the way that delete Intel key. And It worked.
May it help you.
Sorry about by bad English.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
add a comment |
up vote
1
down vote
up vote
1
down vote
I contacted with Houdini dev.
Email:
It looks like you have an Intel OpenCL driver installed and somehow this driver is corrupted and causing a crash as soon as it gets queried or loaded in any way.
Some laptops come with Intel HD graphics as the default, low-end graphics adapter, and also an NVIDIA card for performance graphics
To temporarily disable the OpenCL driver, you can try running regedit and editing the Windows registry. I believe the key you're looking for is: SOFTWAREKhronosOpenCLVendors. Within that there should be keys for the NVIDIA driver and the Intel driver. If you remove the Intel key that should mean that the faulty Intel OpenCl driver won't try to load.
I followed the way that delete Intel key. And It worked.
May it help you.
Sorry about by bad English.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I contacted with Houdini dev.
Email:
It looks like you have an Intel OpenCL driver installed and somehow this driver is corrupted and causing a crash as soon as it gets queried or loaded in any way.
Some laptops come with Intel HD graphics as the default, low-end graphics adapter, and also an NVIDIA card for performance graphics
To temporarily disable the OpenCL driver, you can try running regedit and editing the Windows registry. I believe the key you're looking for is: SOFTWAREKhronosOpenCLVendors. Within that there should be keys for the NVIDIA driver and the Intel driver. If you remove the Intel key that should mean that the faulty Intel OpenCl driver won't try to load.
I followed the way that delete Intel key. And It worked.
May it help you.
Sorry about by bad English.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 6 at 16:51
Hasegawa.G
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 6 at 16:51
Hasegawa.G
111
answered Dec 6 at 16:51
Hasegawa.G
111
111
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hasegawa.G is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
add a comment |
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
Wow, thank you! But the hypothesis that driver is corrupted implies to reinstall it, not disable?
– Dims
Dec 6 at 18:32
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
I had same problem like you. Even the crash log is same. Intel HD graphics shouldn't installed in my computer, but somehow IT did.
– Hasegawa.G
Dec 7 at 20:23
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379755%2fhoudini-crashes-on-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried simply uninstalling the Intel drivers?
– Ramhound
Nov 30 at 14:55