Shark, I'm having a problem with Win 10 on my new PC build. It's a new install, not an upgrade. The BSOD happens on startup, reboots, runs perfectly from then on. Some messages that occur are "Thread_exception_not_handled" "IRQL_NOT_LESS_THAN_OR_EQUAL". ACPI.sys and flmtgr.sys. I am running the memtest86 now and don't expect that it will error. I have downloaded the Window Debugger tool, but am having issues directing it to my "symbols" folder. The symbols folder is located at D: symbols. Can you direct me how to fix that? The computer is online, if directing somewhere online is better, I can do that. Thanks Mang
So, after the crash and reboot the system runs fine? Have you done any overclocking on your CPU/GPU? Also, did you download and install the latest Win10 driver for your Graphics card? What Mother board do you have? Does the board have Win 10 drivers? I would update the chipset drivers if you have not already.
It runs fine. Mobo is Asrock z97e-itx/ac. Bios and gpu are updated to win 10. Other updates won't happen until its on ethernet, which will be soon.
From what I can gather... the ACPI.SYS is due to a driver issue. I would get all of the system drivers up to date and see if that fixes it.
When I went to update the Nvidia driver, it acted like it had never seen it. I hope that solves this. We shall see.
windows 10 just seems a little flakey , with my high end new build i would crash 5 mins after turning it on almost everytime . reboot and be rock solid . now i just dont turn my machine off.
It was a pain in the ass indeed sir...the GPU had to travel across Europe to be fix.Now im seling the fucker.It is my second Broken Sapphire card
i had the same error msgs, didn't feel like digging. reinstall of windows did the job for me i build my windows around that concept, if it derps, i hardly lose anything with a format (learned my lessons from previous win versions) make sure you are making an uefi/gpt install not sure if you are an amd user, but the BSODs started popping up after i installed the crimson driver (running the updated ones now with no issues). was playing around with some different OC settings at the time, so can't be sure what was the actual cause
Figured it out. Turned off fast startup in power settings. Hasn't BSOD'd since. So simple. Glad it wasn't any hardware issue.
![-=[ UP ALL NIGHT ]=-](styles/fracture/xenforo/UAN_Logo.png){kind=logo}