Could be anything from driver issue to something more serious, I would of checked Event Viewer and Reliability History for any issues.
As you know BSODs like that are not normal in any modern OS like 7,8,10 etc...
I think that I'd run memtest and the drive manufacturers test suite before blaming the os. I love 10 and will never go back to the older os's.
I think that I'd run memtest and the drive manufacturers test suite before blaming the os. I love 10 and will never go back to the older os's.
Agree with this. For whatever reason, it seems like Windows 10 is more sensitive to RAM problems than earlier Windows versions. My neighbor had me take a look at his system that was having terrible blue screen issues even trying to get Windows 10 to install. We finally swapped the RAM out and it is working perfectly now. That same system had been running Windows 8 and then 8.1 with no problems right up until the Windows 10 upgrade became available on his system.
As I said. It was tested not too long ago. Unless memtest is just not catching the problem I don't think that's it.
Yeah, somehow I missed the entire second page of posts![]()
I did..... Windows 7 works without errors in event viewer or any BSD's. Windows 10 does not. Windows 10 is an event viewer nightmare lol.
Look I know you people are really sold on 10. I'm not. IMO it's BUGGY, and too new. MS has issues they need to work through before I use it. Besides that it's a privacy nightmare.
It's not a question of being sold or not, my brother had issues on Win7 clean install and that was last year, now do I tell them and say Win7 is not ready for release or full of bugs?..You can't have it both ways .
He got it fixed in the end but had to do a few attempts of clean installs, FYI he had no hardware changes.
Personally it's not buggy on either of my PCs, btw my brother (yes one that had issues with Win7 last year) did the upgrade to Win10 from 7 and it's running great, now you tell me why are we having no issues and you are?
Always easy to blame the OS when you don't know the real cause.
Could be something simple as a corrupt or bad Win10 download or copy.
Windows 10 is like only a month old. Do you think they squashed all the problems already? If you're able to run it well then that's great for you. I'm happy for you. I on the other hand am not able to, and i'm not going to pull my hair out worrying about it. It's much easier for me to just go back to 7 and try again with 10 in say 6 months to a year.
Win10 has been in testing phase a lot longer.
IMHO very polished for a new OS, I even say more polished then what Win7 was on day one.
? Windows 10 was pretty buggy when it was released. Way more so than win7.
Like what it does or not it's stretching credulity to claim that it was polished at launch.
Win7 was really an updated Vista SP3, Win10 has way more features then Win7 ever had and for it's first month very polished IMHO when you consider the changes/features etc, so much so I'm still waiting for my first crash.
Every new OS has some bugs, but that does not take away the fact it's still a polished OS when you look at Microsoft's history on new Operating Systems, things will only get better for Win10 with further refinements so the future is looking good for Win10.
I still stand by my statement.
I'd say not even close. Win 7 way more polished at launch.Win10 has been in testing phase a lot longer.
IMHO very polished for a new OS, I even say more polished then what Win7 was on day one.
If you're going to use that logic, some would argue that Windows 10 is Windows 8.2.Win7 was really an updated Vista SP3, Win10 has way more features then Win7 ever had and for it's first month very polished IMHO when you consider the changes/features etc, so much so I'm still waiting for my first crash.
I'd say not even close. Win 7 way more polished at launch.
If you're going to use that logic, some would argue that Windows 10 is Windows 8.2.
That's the great thing about forums, we all have different view points and opinions.
End of the day Win10 is a fine OS and I'm looking forward to its refinements in the future.
As I said. It was tested not too long ago. Unless memtest is just not catching the problem I don't think that's it.
Did you do an upgrade in place or clean install? I had issues with my first upgrade in place and ended up doing a clean install of 8.1 and about a week later upgraded it to 10 which worked and is what I'm running now. How many passes of memtest did you perform? Memtest will catch bad memory if it is present and sometimes it takes a few passes for the bad module to act up.
Clean install from a Windows 10 iso, burned to disk. I don't remember the passes on memtest but it was close to 48 hours that I let it run. No errors.
Win10 definitely is a bit buggy. My event viewer has plenty of errors in it. Most are transparent as far as their effects (I don't actually see anything wrong happening) but the fact the events are there just goes to show things aren't quite right.
Most of them are Cortana errors. Maybe because I don't have it set up so it can't actually do much. I have a routine ShellExperienceHost.exe crash also, which that particular process seems related to the buggy action center.
Maybe a clean install would fix some of those quirks, I don't know, but I've seen others report the same thing going on so I know I'm at least not alone. And so far it hasn't annoyed me enough yet to make me want to have to reload absolutely everything. That would be a far larger annoyance right now than the occasional action center/calendar hiccup.
Bad burn or disk?..Worth doing a fresh download at some point down the road on to USB flash drive via Win10 Media Creation tool, https://www.microsoft.com/en-gb/software-download/windows10 .
Don't give up.