You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Bug Report BSOD after updating today
- Thread starter Enix
- Start date
I would be more concerned about the fact you got a BSOD than I would be about reverting a patch. There is no reason why OBS would cause a BSOD. Particularly not that BSOD.
-- Run Memtest86+
-- Scan for virusses and malware
And, to answer your question -- reverting to a previous version is relatively easy. Just grab the binaries for that earlier version off the download page, extract to and overwrite the OBS installation and then, to be on the safe side, delete your OBS configuration (start->run->%AppData%\OBS, empty folder).
-- Run Memtest86+
-- Scan for virusses and malware
And, to answer your question -- reverting to a previous version is relatively easy. Just grab the binaries for that earlier version off the download page, extract to and overwrite the OBS installation and then, to be on the safe side, delete your OBS configuration (start->run->%AppData%\OBS, empty folder).
I'm not concerned as it is a new install on an extremely clean and reliable PC, there had been absolutely no signs of damage or poor performance until I downloaded this update and clicked to start my stream. I rebooted and am running fine because I didn't repeat the same behavior, and other people on the forum are saying that this recent patch hasn't been working well as well as BSOD and program crashes. I'm fairly confident its not on my end, however thanks for the information on how to get my program working again.
And yet, I have yet to see one crash, one BSOD, one foul-up of OBS... on a 2-year old installation on which I sometimes install and remove the same piece of software (whichever that may be) more than twice a day, without rebooting. ;)
My point being -- maybe the PC is not as reliable as you think it is. I would be very, very cautious about IRQL_NOT_LESS_OR_EQUAL BSODs, if I were you.
My point being -- maybe the PC is not as reliable as you think it is. I would be very, very cautious about IRQL_NOT_LESS_OR_EQUAL BSODs, if I were you.
BSODs are caused by faulty hardware or broken drivers. OBS does not run any kernel code, thus cannot directly cause a BSOD. Run a LinX test (viewtopic.php?f=18&t=5361) and make sure all your drivers are up to date. If you continue to get a BSOD, post the c:\windows\minidump\xxx.dmp file here for analysis.
Again, advising a stress test to someone who may in fact have faulty hardware. Seriously, stop doing that. He needs to run Memtest86+, not LinX. Regarding IRQL_NOT_LESS_OR_EQUAL, the most common cause for that one is a faulty memory bank. Hence, Memtest86+ again. Since there is no more comprehensive or rigorous test for one's memory.
No, it is not a much better test. LinX is on OS level and consequently is severely limited to what it can test and the range it can test. And Memtest86+ will find errors that LinX could never even hope to find simply because it is far more exhaustive.R1CH said:Memtest can take days to find errors that LinX will find in 5 minutes, it's a much better test.
Besides, the kind of errors LinX will find quickly Memtest86+ will find quickly as well. The most severe errors will pop up in an instant in both tools.