Currently Being ModeratedSep 1, 2013 3:55 AM (in response to Robury)
I just set-up my iMac with bootcamp Win 8 and have exactly the same experience, at least one or more times a day.
Any idea or fix? on the latest of everything,,,
Currently Being ModeratedSep 1, 2013 4:37 AM (in response to wojski)
when I first installed win8 upgrade for my win7 i let windows update install what it said was a newer ati driver
I said yes and it was big big trouble
went back to the driver that came with the apple driver pack from osx bootcamp and it was better still had crashes once in awhile
then apple started to official support win8 and I updated the ati driver with the new one from the apple driver pack and all have been well since
can't remember if it was the same eror text I had though
Currently Being ModeratedSep 1, 2013 8:13 AM (in response to wojski)
I discovered that windows update installed a new graphics package that caused my problems. I tried removing the program but it didnt help so I installed bootcamp again and changed windows update to only download updates and not to automatically install them. I then identified the one that caused the problem and gave it the hidden attribute. This has stopped the crashing.
However, not being satisfied with geting windows 8 to work correctly I installed windows 8.1, and its now crashing as before! I am clearly pushing my luck with 8.1, but changing the settings to switch of the monitor after 10min but never go into sleep mode has stopped the crashing. As I am now in 8.1 I cannot give you the exact update that caused me the problems, but I am sure it had graphics in its title and the description stands out from all the others.
Hope this helps
Currently Being ModeratedSep 1, 2013 1:40 PM (in response to Robury)
Win8.1 is nor a finished product it will not be released for another month or so
And then it could take some time before it get official support in bootcamp after theat
Currently Being ModeratedSep 1, 2013 3:36 PM (in response to Rudegar)
October 17th. It is "RTM" and everyone is furious that MSDN and others will not have access to the final bits until then.
It runs better than 8.0 (on my own PC I built 4+ yrs ago) than 7 ever could or than 8 (I have dual boot with 8 and 8.1 on their own SSDs)
Currently Being ModeratedSep 3, 2013 1:37 PM (in response to Robury)
OK, what a pain but finally resolved for me.
I was a bit confused as I thought it was with the 6770M graphics driver but finally found that it was with the seperate Intel one ofcorse that must have come down with Windows Update automatically (I was unlucky I think when setting up via bootcamp the drivers were not inserted even though I did the exact same thing and it worked beutifully before.. later I couldn't find the bootcamp control panel so I installed it and a little bit after this issue started exhibiting)
Anyways in Win 8 Device Manager under View Menu your select Show hidden Devices, then (finally) under Diplay Adapters "Intel(R) HD Graphics Family (Microsoft Corporation - WDDM 1.2)" pops up.... you might be able to disable it there, although for me this was greyed out (probably because in the driver it actually said "Currently, this hardware device is not connected to the computer. (Code 45)... ha ha ha... thanks for whoever installed it then). Anyways, I uninstalled it but problem still kept happening... ***?!?... so in the end I just found the igdkmd64.sys file under drivers and renamed it... problem finally fixed... no crashes.... hope that assist someone or at least sheds some light.
Currently Being ModeratedSep 3, 2013 10:50 PM (in response to wojski)
I tried renaming of igdkmd64 and it stop the crashing but the next day it returned, I think this could have been due to the microsoft update, I am going to wait until the official 8.1 is released then reinstal bootcamp and work from there. Out of interest, does your computer time keep changing to 1 hour ahead?
Currently Being ModeratedSep 5, 2013 2:20 PM (in response to Robury)
Strange, mine hasn't crashed again... I renames two of the files btw... yes, my clock was also out even though it was getting internet time?!? I have seen that before, anyways, if you change to different internet time provider and update it seems to fix it up after a bit of fiddling... I think this is just a windows thing...