program that hunts out old system drivers and removes

Forums › Microsoft Windows › program that hunts out old system drivers and removes

fundanglr

169 posts

Master Geek
+1 received by user: 2

#173639 30-May-2015 18:23

can anyone tell me, if this program will do the job , to remove old system drivers ( i changed mobo and keep getting the same BSOD issue and belive its a clash from an old driver)

http://ghostbuster.codeplex.com/

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41029

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1314799 30-May-2015 19:01

Changing motherboards almost always require a fresh install.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Lurch

1061 posts

Uber Geek
+1 received by user: 71

#1314802 30-May-2015 19:10

What is currently set in the BIOS AHCI or IDE/Native IDE? Try changing the value to IDE if it is AHCI. Should allow the machine to boot and then grab the latest chipset drivers.

You can also check also the Windows system logs will also give you an idea what is causing it then uninstall the offending item.

fundanglr

169 posts

Master Geek
+1 received by user: 2

#1314805 30-May-2015 19:18

i have it, its a directx issue, found it with who crashed me, ill post it up shortly

fundanglr

169 posts

Master Geek
+1 received by user: 2

#1314808 30-May-2015 19:28

On Sat 30/05/2015 1:57:01 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\053015-19734-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF88008526B99)
Bugcheck code: 0x50 (0xFFFFF8800B4296BD, 0x1, 0xFFFFF88008526B99, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.