Quantcast
Channel: Intel Communities: Message List - Graphics
Viewing all articles
Browse latest Browse all 28450

Re: Intel igdkmd64.sys recent BSODs

$
0
0

Replacing the processor did not effect the problem with the graphics.

 

Since then I had a drive in my RAID fail. The instructions on how to install intel RAID are fairly clear but info on how to replace a drive is virtually non-existent. I went to great lengths to make multiple backups before replacing the drive. It actually was quite simple but I had found nothing to tell me how or what to expect.

 

One odd effect is that the drive number changed so that it did not boot to the correct drive. The BIOS is supposed to let you set the boot drive when pressing f2 to start but the RAID did not show since it only shows the first 4 drives and I have more. I found that instead pressing F11 brought up the full list of drives so I could get it to start, but every-time had to manually press F11 I eventually found a document from microsoft explaining that this can happen. Of course they acknowledge the problem but have not fixed it. I had to swap SATA connectors to make it swap correctly.

 

I did a sfc /scannow to check system files. It found some errors it could not fix.

I followed that by

DISM /online /cleanup-image /restore health that successfully replaced corrupt system files.

image version is 6.3.9600.17031

 

A that point I tried re-enabling the Intel Graphics driver and immediately got the same error as before. I applied the latest update

Disc Management showed the version as 10.18.10.3496

but in driver details it shows as 10.19.10.3412

Why are they not the same number?

 

I tried refresh but it says the drive is locked also since I had win 8.0 upgraded to win8.1 I do not have the install disk to re-install without going to win 8.0 and then updating again - another consumer unfriendly Microsoft behaviour

 

Any other ideas?


Viewing all articles
Browse latest Browse all 28450

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>