Maybe installing the latest leaked build (10125) on the iMac wasn't the greatest idea :(

Posted May 27, 2015, 12:51 AM UTC

Posted May 27, 2015, 12:51 AM UTC
bootcamp i take it? u should be fine
yup! luckily, this has only happened once in the last 4 days.
how is it fairing now? I suspect Yosemite is the big culprit in slowing down my Girlfriend's iMac 2011.
windows 10 has given my 2013 imac a new breath of fresh air! it runs wonderful and much more snappier than when i'm on yosemite. can't wait for RTM!!
how do you get such a nice resolution on the BSOD screen?!
That's how it's been since 8.0.
Not on mine, desktop is 2560x1440 but the BSOD has a much lower res.
Maybe it maxes out at 1080?
You chose... poorly.
Which iMac? Was debating bootcamping 10125 on my Retina iMac.
late 2013 model. 2.9GHz quad-core Intel Core i5 processor. 8 gig ram.
it runs beautifully. way snappier than on yosemite. i'm definitely looking forward to RTM!
I kept getting that error when I installed one build on my HP Laptop. Not sure what caused it.
I've been getting that error on my desktop about 25% of the time returning from sleep.
Same here on my HP laptop. and its not only that particular error. I've gotten system_service_exception and others. I know a few people who are using it on their main custom rigs though and swear they never get any BSODs so I think its probably hp drivers not playing well with Win10.
I've been running it full time on my franken-computer which has an HP motherboard without problems, but I haven't downloaded anything off of the HP website for it. So you're probably correct about the HP drivers.
I have an HP Envy j series and I've installed almost all the HP drivers. Haven't had a bsod since build 10041 - I guess it must be a driver for a specific series or model.
10041 was the build I had problems on. Gave up and reinstalled Windows 8.1 so I can't comment on build 10122 stability.
I get a lot of driver pool BSODs, on both laptop and desktops.
Heh, never seen CRITICAL_PROCESS_DIED before.
I saw it when I tricked VMware and hyper-v into running together. I started up the PC, and consequently hyper-v, fine. Opened VMware, BSOD. Honestly, didn't expect anything else, but it was interesting. Wound up having to reinstall.
I have seen that too with my Surface Pro 3.