Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks again.
have you tried uninstalling and reinstalling your antivirus?
i have already successfully installed windows 10 creators update on 2 PCs via mounted ISO from windows 10 anni version.
one is an i3-530 with nvidia 9800GT and the other is an i3-3240 with nvidia gtx 960.
no problem so far aside from filehippo updater.
Thank you for the suggestion. I downloaded and this is what it found.
On Wed 4/26/2017 12:22:18 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042617-24078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x19 (0x20, 0xFFFFA4090A8C8CD0, 0xFFFFA4090A8C8DD0, 0xC100001)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Uninstall any drivers youve installed and install the latest
GPU using DDU
Ethernet/Wifi
Any other sort of hardware drivers
and go from there
Download the drivers you need before you uninstall them
Under Windows Defender (bottom-right taskbar), check the "Device Performance & Health". This will check to ensure your drivers are valid and up-to-date.
Go to your offical motherboard website, under support > downloads, and ensure you have those latest drivers.
Update your graphics card driver too.
Device Performance & Health is a joke; that is according to MS; which is meaningless.
Yeah, but Creators Edition has improved it's detection at least. It's ideal to run once just after the update to perform a quick check.
The better but longer way, would be manually going under your Control Panel and checking the "Device Manager" yourself for unknown or conflicting drivers.
Ok, did that. I did the main ones, graphics, sound card, ethernet/wifi stuff, mouse and keyboard from Razer. Most everything else was stock drivers I never messed with.
To answer another post, I do not overclock at all. I dont know how to be honest. And another post response, I checked Windows Defender and it says Performance & Health is ok, but it does say no health report is available.
I went and turned on Windows Update, and searched for updates, said everything was up to date. Fixed? Almost. I did it again to make sure, and sure enough it found some sort of Windows Defender Definitions Update and crashed again upon install.
Ive read that it could be my RAM? Ive been meaning to update to 16GB anyways. I guess I could give that a try.
But again, why does it ONLY happen when an update is trying to happen, and its ALWAYS that Defender Definitions update?
Thanks to all who have given feedback, its seriously appreciated.
RAM? Well run diagnostics on all your Drives and RAM to find out if any faulty.
id just use Shutup10 to disable Win Defender and be done with it
When has it actually been useful for anyone?
While it can be a faulty RAM stick, if it were i think you would have been having issues long before the update.