ubuysa
The BSOD Doctor
No worries. That output does not indicate any disk problems.
Do test the RAM with the tool in the installer DVD.
When you reinstall Windows are you deleting all existing system partitions?
BSOD after windows update
- Thread starter Sick Mick
- Start date
Do test the RAM with the tool in the installer DVD.
When you reinstall Windows are you deleting all existing system partitions?
Sick Mick
Active member
Just to clarify I don’t have a dvd, been using usb. Brand new laptop with no disc tray.
I tried MDSCHED but got “windows cannot check for memory problems”.
I have been deleting partitions
ubuysa
The BSOD Doctor
OK. Visit https://www.memtest86.com/ and download Memtest (it's way better than the tool on the install USB). Use the extracted tool to make a bootable USB containing Memtest and then boot that USB. Memtest will start running (as long as you don't move the mouse of press any keys). Leave it running overnight. If even a single error is found then flaky RAM will be your problem.
Sick Mick
Active member
I’ve set it running now.
Thanks for all the help so far UBUYSA, you are a gentleman and a scholar.
SpyderTracks
We love you Ukraine
when installing windows 10 are you deleting all partitions before installing?
Sick Mick
Active member
I am
Sick Mick
Active member
With the Kensington pen drive it seemed to usually crash at around 30 to 36 percent. I then made a new image on an old pen drive I had and that would usually crash around 10 to 17 percent as it was slower. Pretty consistent.
Sick Mick
Active member
I have made some good progress. I have windows installed and I’m currently rounding up all missing drivers.
I believe the fault may have been an undervolt I applied using Intel XTU which had been running stable at -0.120. The update clearly changed that. I had checked this early on but BIOS was showing Undervolt at 0.
The key was setting the ‘Overclocking Feature’ in BIOS to disabled.
I believe the fault may have been an undervolt I applied using Intel XTU which had been running stable at -0.120. The update clearly changed that. I had checked this early on but BIOS was showing Undervolt at 0.
The key was setting the ‘Overclocking Feature’ in BIOS to disabled.
Last edited:
ubuysa
The BSOD Doctor
Ah. Good catch. With all BSODs it's wise to remove any overclock or undervolt. Fingers crossed then.
Sick Mick
Active member
Ah. Good catch. With all BSODs it's wise to remove any overclock or undervolt. Fingers crossed then.
While I've got you would you be able to help me out with some missing drivers? I got the majority last night but couldnt manahe to get my hands on four of them.
ubuysa
The BSOD Doctor
Where did you get the drivers from? Generally it's much better with Windows 10 to allow Windows Update to install all drivers. I would right-click on those devices, select update driver and then allow Windows to find the best driver.
Alternatively just run Windows Update repeatedly until no more updates are found.
If you installed drivers manually, did you install the chipset driver? The SM Bus Controller driver is certainly part of the chipset driver, possibly the others too.
For the future, when you reinstall Windows and have gone through the initial setup always run Windows Update repeatedly (across reboots if necessary) until no more updates are found. This will generally install all necessary drivers.
Alternatively just run Windows Update repeatedly until no more updates are found.
If you installed drivers manually, did you install the chipset driver? The SM Bus Controller driver is certainly part of the chipset driver, possibly the others too.
For the future, when you reinstall Windows and have gone through the initial setup always run Windows Update repeatedly (across reboots if necessary) until no more updates are found. This will generally install all necessary drivers.
Sick Mick
Active member
I got the drivers from my PCSpecialist download page. I have updated windows over numerous restarts and it now seems to be up to date. I have tried right clicking and allowed windows to find the best driver and also locate the files myself directing it to a file where i have downloaded all PCSpecialist files to. I have manualy gone into these folers and ran applications.
I did install the chipset driver to no avail.
ubuysa
The BSOD Doctor
Those are pretty much the same devices you had issues with after the Windows update. If they're not working after a clean install then I'd start to think it may be hardware.
If it were mine though, I would do another clean install. Ensure that you choose a custom install and delete all system partitions (MSR, Recovery, EFI, System) so that all that space shows as unallocated. Then highlight that unallocated space and click the Next button. The installer will create the correct partition structure and install Windows.
Once Windows is installed and you've gone through the initial setup, run Windows Update repeatedly (also after any reboots) until no more updates are found.
If those devices still show up in Device Manager then it's most likely a hardware problem.
Sick Mick
Active member
This is how I installed Windows last night.
It's worth noting that as I was going through the PCS downloads some of the setup applications where throwing out this error.
ubuysa
The BSOD Doctor
I'm afraid I think you may have a hardware issue there. That error suggests the chipset driver isn't installed yet we know that it is, hence it's likely hardware.
I'd give PCS, a call tomorrow. Live Chat seems to be the best way at the moment.
Sorry for the delay, been watching the F1 GP....
Sick Mick
Active member
Not at all, I appreciate the help. I'll try and have a word with them tomorrow. In the mean time is it worth downloading a program that can find drivers or is this redundant?I'm afraid I think you may have a hardware issue there. That error suggests the chipset driver isn't installed yet we know that it is, hence it's likely hardware.
I'd give PCS, a call tomorrow. Live Chat seems to be the best way at the moment.
Sorry for the delay, been watching the F1 GP....
Enjoy the rest of your Sunday. Thanks again.
ubuysa
The BSOD Doctor
Never use driver search tools. You have no idea whether they find the right driver or even what's in the driver code.