New
#1
BSOD - 0x139 KERNEL_SECURITY_CHECK_FAILURE
Hello,
I assembled my desktop several weeks ago, and got several BSOD per day.
After a fresh reinstall, I still got problems...
Thanks for your help :)
Hello,
I assembled my desktop several weeks ago, and got several BSOD per day.
After a fresh reinstall, I still got problems...
Thanks for your help :)
Welcome aboard, Thomas42.
Stop 0x139 is a bad BSOD. Because ....
The in this application part is different in three dumps. In one it is Dropbox, in another one it is Plays TV and in another one it is crrss.exe, a core system file. So it is none of them but something that is playing in the background, not coming in the front. And that is the basic nature of a disguising malware.ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
I would suggest you to do another clean reinstall. Then dont rush the programs, we have to use the program installation process as the eliminating process. Add one driver/software at a time; see its effect on the system, then install another one. Go on this way. See at what stage the BSOD comes back. That will be the program in fault.
P.S. While installing the display driver, follow this method: AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
I'll agree that you want to re-install and go through testing each of your applications one-by-one. You may want to install either a disk imager like Macrium Reflect or a snapshot tool like Rollback rx. I'd suggest the latter based on the speed and performance, makes it easier for testing like this. At the company I used to work for we'd test driver updates this way, so this methodology works well in your situation too.
Hello,
I have reinstalled Windows, then Rollback rx and just a few apps (google chrome, dropbox and keepass password safe)
I experienced another BSOD, then try to restore a snapshot with Rollback Rx.
Now on boot I have this screen:
Attachment 77983
What should I do ?
So this error means that Windows has lost access to the System Partition.
Are you using an SSD and HDD? If so, Win 10 could be ignoring the SSD, unplugging the HDD then booting should be fine (if it's simply a data partition
I would also recommend verifying where you picked up the ISO (as in verify it's from Microsoft) and make sure it's a fresh install.
You can also try uninstalling Rollback Rx from its pre-os menu. I doubt it's the culprit but it's possible. If it is, you might want to send log files to the dev and they can look into it.
Good luck!
Yes Windows is installed on a SSD, and it comes from Microsoft.
I reinstalled Windows again and today I got 2 BSODs, with no software installed.
Do you think it can be a hardware issue ?
I ran CristalDiskInfo and memtest86+, and found no error.