Solution
Well that didn't really make any difference and firstly I'd remove Avast and just use the onboard Defender coupled with the free Malwarebytes. You can always re-install at a later date.
No driver of note has appeared anywhere and it might be an idea to run the driver verifier.
First you need to make sure you have a recovery disk/USB or win 10 install media. You need this in case the verifier set's off a boot loop bsod. If this happens you then use the Link Removed to get back into safe mode and turn the verifer off.
This will guide you through the process:
Link Removed
Good luck and post any new dump files.
No driver of note has appeared anywhere and it might be an idea to run the driver verifier.
First you need to make sure you have a recovery disk/USB or win 10 install media. You need this in case the verifier set's off a boot loop bsod. If this happens you then use the Link Removed to get back into safe mode and turn the verifer off.
This will guide you through the process:
Link Removed
Good luck and post any new dump files.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
If you can boot into safe mode I'd try removing them. I think you had a recovery usb or similar for the driver verifier? Use that to access safe mode and remove them although i'm not exactly sure which three drivers you mean? Two chipset drivers and audio or SATA or USB? Please try and be more precise with your answers as it just helps things along..
If out of the installed drivers you included the SATA drivers then I'd remove them first and see if the system boots up ok.
If out of the installed drivers you included the SATA drivers then I'd remove them first and see if the system boots up ok.
Lukipow
New Member
- Joined
- Apr 10, 2017
- Messages
- 20
- Thread Author
-
- #24
Trying only the both Chipset Drivers now!
EDIT: Installing Both Chipset Driver worked, but still getting the same Bluescreen when starting programs as admin.
Weird is, when starting the problems normal there are no error occuring, There must be something missing.
EDIT: Installing Both Chipset Driver worked, but still getting the same Bluescreen when starting programs as admin.
Weird is, when starting the problems normal there are no error occuring, There must be something missing.
Last edited:
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
If you mean by this that this was an upgrade installation then you need to clean install quickly followed by installing the drivers from your support page.This Windows 10 is an Update, not a clean install.
Usually good practice is chipset drivers first, gpu drivers, audio drivers and SATA (try the Intel rapid storage driver rather than anything else.) You can now pop on anything else which might be left.
Once the drivers are installed update Windows. Then and only then try any third party applications.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
I wouldn't bother then if you know the outcome.
What security are you running?
Where did you get the iso for the Windows 10 install?
When you installed windows was anything else attached by usb other than mouse or k'board?
What security are you running?
Where did you get the iso for the Windows 10 install?
When you installed windows was anything else attached by usb other than mouse or k'board?
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
This is fineI got the Tool for Updating to windows 10 from here: Link Removed
This probably isn't.And I also had my Focusrite Solo For my Micro connected also.
Components like this ideally should be added after the Windows install has finished and I just wonder if it's been attached every time you've tried to install windows? If so then this could be your culprit and you need to install windows with it un-attached.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
I'm puzzled why you stop at the gpu driver after only installing the TWO chipset drivers (chipset should be two installs not one) 'Engine management' and 'Chipset' are two different drivers both are crucially important as are all the other drivers too.I still have nothing else connected then my mouse and Keyboard, but still the same error
Try repeating the bsod steps in safe mode, if the bsod still occurrs then likely it is a hardware issue
Can you post your all of the system's hardware please:
Ok, let's try and rule out one or two things and also make sure it isn't a hardware issue which is becoming more likely.
The dump file at least is looking less corrupted but still something isn't right that is obvious.
Please run a chkdsk:
chkdsk – Guide for Windows XP, Vista, 7, 8, 8.1, 10
Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool
Check your processor:
Link Removed
Good luck with the testing, I'll check back in few hours.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Did you miss this question?I'm puzzled why you stop at the gpu driver after only installing the TWO chipset drivers (chipset should be two installs not one) 'Engine management' and 'Chipset' are two different drivers both are crucially important as are all the other drivers too.
I would still, as a matter of course run the scans specified, what have you got to lose?I think it can't be a Hardware problem, because when the problem first appeared, I switched back to Win 8.1 and everything worked great again, and now, switching Back to Win 10, same Problem appears.
Ok let's look at the actual windows 10 install files. If you have only created the install USB once, I would view it with suspicion and create another, or try using a RW disk.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Have you tried running a program as admin as soon as the os is installed?
You need to make sure nothing else is installed driver wise and just use the os as is.
If the same bsod occur's then chances are your windows copy is corrupted.
If not then download a fresh copy.
You need to make sure nothing else is installed driver wise and just use the os as is.
If the same bsod occur's then chances are your windows copy is corrupted.
Did you try a different ISO file at each time as well?I tried reinstalling windows 10 from 2 disks and 1 USB stick, always different versions.
If not then download a fresh copy.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
You may have answered this question above not sure as answers are a little vague.Have you tried running a program as admin as soon as the os is installed?
You need to make sure nothing else is installed driver wise and just use the os as is.
Have you checked the forums of users with the same motherboard? Might be a bug to do with Creators?
We need to test if only to rule things out so please:
Please run a chkdsk:
chkdsk – Guide for Windows XP, Vista, 7, 8, 8.1, 10
Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool
Check your processor:
Link Removed
Good luck with the testing, I'll check back in few hours.
Similar threads
- Article
- Replies
- 0
- Views
- 75
- Article
- Replies
- 0
- Views
- 65
- Article
- Replies
- 0
- Views
- 5K
- Article
- Replies
- 0
- Views
- 322
- Replies
- 0
- Views
- 173