Jump to content

Hello,

Im having a problem with a faulty driver. Im pretty sure its a driver as I ran every possible hardware test ever made.

 

When I put my computer to sleep... it wakes itself back up to a bluescreen. I googled the issue and people facing the same issue solved it by reformatting/reinstalling. This is not a solution for me though as it will take me about a week to get my PC back to its current state.

 

Is there a way for me to uninstall most if not all of my drivers, reboot and let Windows 10 deal with them.


I think the issue was caused by iObit Driver Booster ... i really hate programs like this, but I decided to give it a go as it was highly recommended by a friend. 

 

Thanks.

 

 

WhoCrashed seems to agree with me:
 

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 11/14/2016 1:23:34 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF97F4804080A8) 
Bugcheck code: 0xBE (0xFFFF97F4804080A8, 0x8000000000900021, 0xFFFF8500C3EC6500, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. 
Google query: ATTEMPTED_WRITE_TO_READONLY_MEMORY



On Wed 11/9/2016 12:12:29 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110916-10953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A3B0) 
Bugcheck code: 0xBE (0xFFFF8FFE22C000A8, 0x8000000000900121, 0xFFFF80017ED50150, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

 

P.S. - Its not my RAM. I ran Memtest86 off of a USB with a million passes... windows built in diagnostics and nothing. Issue only happens on wake up!

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/
Share on other sites

Link to post
Share on other sites

2 minutes ago, Antwan said:

Hello,

Im having a problem with a faulty driver. Im pretty sure its a driver as I ran every possible hardware test ever made.

 

When I put my computer to sleep... it wakes itself back up to a bluescreen. I googled the issue and people facing the same issue solved it by reformatting/reinstalling. This is not a solution for me though as it will take me about a week to get my PC back to its current state.

 

Is there a way for me to uninstall most if not all of my drivers, reboot and let Windows 10 deal with them.


I think the issue was caused by iObit Driver Booster ... i really hate programs like this, but I decided to give it a go as it was highly recommended by a friend. 

 

Thanks.

I'd do a clean windows install. Hopefully that fixes shit

AMD Ryzen 7 7800X3D | Sapphire Pulse AMD Radeon RX 7900XT Triple Fan | G.Skill 32GB 2x D5 6000

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/#findComment-8858330
Share on other sites

Link to post
Share on other sites

I'd say letting Windows handle installing your drivers will cause more harm than good. Why not just uninstall and reinstall that specific program/driver that you think is causing the issue? And also why would your PC take so long to get back into current shape if you reinstalled? Can you not back up stuff?

Lenovo Ideapad 720s 14 inch ------ One day I'll have a desktop again...

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/#findComment-8858332
Share on other sites

Link to post
Share on other sites

Clean install is the way to go, it will remove everything and then only install the necessary drivers.

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/#findComment-8858348
Share on other sites

Link to post
Share on other sites

3 minutes ago, Enderman said:

Clean install is the way to go, it will remove everything and then only install the necessary drivers.

I really really don't want to :D

8 minutes ago, Spork829 said:

I'd say letting Windows handle installing your drivers will cause more harm than good. Why not just uninstall and reinstall that specific program/driver that you think is causing the issue? And also why would your PC take so long to get back into current shape if you reinstalled? Can you not back up stuff?

A lot of programs, a lot of settings, a lot of plugins. Its a nightmare.

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/#findComment-8858366
Share on other sites

Link to post
Share on other sites

Just now, Antwan said:

I really really don't want to :D

A lot of programs, a lot of settings, a lot of plugins. Its a nightmare.

Then again I'd say try uninstalling that specific program that you suspect is the issue.

Lenovo Ideapad 720s 14 inch ------ One day I'll have a desktop again...

Link to comment
https://linustechtips.com/topic/690572-uninstall-most-drivers/#findComment-8858369
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×