So many metro games crash, screen res or graphics driver issue?

[stefalopod]

So, the closest I could come to finding Bluetooth drivers for my device was to go to IVT's website and download bluesoleil8. I ran the setup utility and it uninstalled my Bluetooth drivers. I'm running it again to install bluesoleil8

 

[stefalopod]

The problem is that the maker of your machine seems to have gone out of business, so they aren't offering drivers or whatnot.

Tell me about it. Rumor on the Viliv forums is that if you can read in Korean you can log in and then download drivers. The company never seemed to bother to update them though.

For the Bluetooth: Right click in device manager. Properties. Details tab. Change dropdown to say hardware ids instead. Copy/paste results here.

Installed Bluesoleil8

USB\VID_0A12&PID_0001&REV_3164
USB\VID_0A12&PID_0001

For the sd8686: Right click, update driver software, browse my computer, let me pick, have disk, browse.
Then double click on the actual inf. Click ok then next. It should install.

This is exactly what I did when I got the timeout screen. Happy to do it again if you want. I took a screenshot if you want to see the error message.

 

[GMan]

Yes, all latest crash dumps are caused by sdbus.sys, which is from the sd8686.sys problem. They all show the 2008 driver still.
Not really sure how or where to get the update, but I can say for sure it does need to be updated.

You could search Google for its hardware id.

0: kd> lmvm sd8686
start    end        module name
a1ef0000 a1f43000   sd8686     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\sd8686.sys
    Image name: sd8686.sys
    Timestamp:        Wed Jun 04 07:24:20 2008 (48467B64)
    CheckSum:         0005CA49
    ImageSize:        00053000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

FAILURE_BUCKET_ID:  0x9F_3_sd8686_IMAGE_sdbus.sys

BUCKET_ID:  0x9F_3_sd8686_IMAGE_sdbus.sys

This driver I previously linked is from 2010:

Marvell SD8686 Wireless LAN SDIO Adapter Windows Driver, Utility | Wireless Driver & Software


You can backup the 2008 driver or rename it. Then copy/paste the one from the download in this post to C:\Windows\System32\drivers

Reboot.

 

[GMan]

Install this for the Bluetooth:

http://bluetoothinstaller.com/BluetoothDriverInstaller.exe

From:

Bluetooth Driver Installer - Get Bluetooth to work with the Microsoft Bluetooth stack

 

[stefalopod]

Bluesoleil updated the drivers to 2011 versions. This is evidently a trial version, I don't know what it will do to the drivers when it expires.
I updated the huaweii modem too and it now has an updated driver
then I ran hive mind and it bluescreened again

Do you still want me to run the Bluetooth installer you mentioned above?

 

[GMan]

Things are looking much, much better now.

Please see my previous post about how to update this (2 of my posts up):

sd8686 sd8686.sys Wed Jun 04 07:24:20 2008

And in the thread I mentioned what to do with this:

hwinterface hwinterface.sys Tue Feb 24 05:44:18 2009

Everything else looks alright. The Intel driver is still crashing with a 0xD1 stop though, which I'm not liking at all. It still could be caused by one of the above in this post, so we'll see.

Very doubtful because of the crash type, but it could be a clocking issue with the adapter and/or cpu and/or memory, in the bios.

One thing at a time. Take care of the two drivers in this post, then post a new crash dump after if still necessary.

 

[GMan]

We are going to employ some trickery here, so please follow closely. We're gonna put a 2012 driver for the video, intended for a different model/chipset.

Before starting, see if you can boot to safe mode in case you need it later by continuously pressing F8 while powering on. If not, follow this:

http://www.eightforums.com/tutorials/2758-safe-mode-add-windows-boot-manager-windows-8-a-3.html

-----------------

1) Rename this file C:\Windows\System32\drivers\igdkmd32.sys to igdkmd32.bak

2) Download my attachment. Extract it so it goes to the folder from step 1.

3) Reboot.

4) Test it out.

5) If you could not boot to Windows, use safe mode to restore the original file by renaming to original. (Should be fine but never tested this with Intel drivers before.)

 

[stefalopod]

Downloaded the Marvell driver again. Installed it through device manager … have disk. Still shows 2008. Here's a screen shot:


Trickery coming next!

 

[stefalopod]

hwinterface hwinterface.sys Tue Feb 24 05:44:18 2009 <<< Belongs to some Windows XP software involving parallel port. Should be uninstalled. You can manually rename the file then reboot:

0: kd> lmvm hwinterface
start    end        module name
883bc000 883bd400   hwinterface   (deferred)             
    Image path: \SystemRoot\System32\Drivers\hwinterface.sys
    Image name: hwinterface.sys
    Timestamp:        Tue Feb 24 05:44:18 2009 (49A3CF82)
    CheckSum:         0000A1FD
    ImageSize:        00001400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I tried looking for hwinterface.sys in device manager but couldn't find it. Then I searched my files for it and the only reference to it was in the W8 log file I still have on my desktop.

Where should I look for it and then what should I do to it?

 

[GMan]

Image path: \SystemRoot\System32\Drivers\hwinterface.sys

I tried looking for hwinterface.sys in device manager but couldn't find it. Then I searched my files for it and the only reference to it was in the W8 log file I still have on my desktop.

Where should I look for it and then what should I do to it?

Whenever you see a reference in Windows computing to "SystemRoot", that means where Windows is installed to, so C:\Windows in most cases.

so

C:\Windows\System32\Drivers\ <<<< You can copy/paste this to the Windows Explorer then press enter.

Rename this file: hwinterface.sys

to hwinterface.bak

Then reboot.

OR

-----------

Open an elevated command prompt (Admin) and run these commands:

cd /d C:\Windows\System32\Drivers\

ren hwinterface.sys hwinterface.bak

then reboot.

 

[stefalopod]

We are going to employ some trickery here, so please follow closely. We're gonna put a 2012 driver for the video, intended for a different model/chipset.

Before starting, see if you can boot to safe mode in case you need it later by continuously pressing F8 while powering on. If not, follow this:

http://www.eightforums.com/tutorials/2758-safe-mode-add-windows-boot-manager-windows-8-a-3.html

-----------------

1) Rename this file C:\Windows\System32\drivers\igdkmd32.sys to igdkmd32.bak

2) Download my attachment. Extract it so it goes to the folder from step 1.

3) Reboot.

4) Test it out.

5) If you could not boot to Windows, use safe mode to restore the original file by renaming to original. (Should be fine but never tested this with Intel drivers before.)

Heya. I did this and it definitely crashed on restart. I loaded in safe mode, deleted the .sys file, and then went to go rename the .bat file but, um, I couldn't find it. So I installed the general graphics driver from microsoft, ran in win8, then reinstalled my old graphics driver from files.
The device manager, properties, driver window is saying that I have a 2010 version of the driver on. Hive mind still causing bluescreen though.

will do hwinterface next

 

[stefalopod]

C:\Windows\System32\Drivers\ <<<< You can copy/paste this to the Windows Explorer then press enter.

Rename this file: hwinterface.sys

to hwinterface.bak

Then reboot.

Did this, ran hivemind, BSOD, crash logs attached


So, that seems to just leave the network adapter and the graphics driver, right?

 

[stefalopod]

Found some updated drivers for gma500 and the Marvell adapter (Hurray!). Installed, rebooted. Ran Hive Mind, BSOD (awww.. )
Latest crash logs attached

 

[GMan]

For some reason, the Bluetooth drivers are older again. Here is general list of what's old needing update:

sd8686nd5 sd8686nd5.sys Fri Jul 24 09:19:41 2009
btnetBus btnetBus.sys Thu Sep 24 01:38:41 2009 (4ABB05E1)
BtHidBus BtHidBus.sys Thu Sep 24 01:36:27 2009 (4ABB055B)
IvtBtBus IvtBtBus.sys Tue Aug 25 23:12:48 2009

With these files present and active, I can't say for sure about anything as a definite cause.

I can say for sure though that the Intel driver is crashing with stop 0xD1 time and time again. The driver is known well. If it had not been, Intel would have updated it since 2010 and made a new version that the internet is not complaining about. Generally, the internet is not complaining on this driver.

So that leaves 2 possibilities. One of the drivers above is messing things up or your hardware settings are unwell. I would double check that the latest bios is installed and then after, set Optimized Defaults in the bios.

And as said, those above drivers are very important to have up to date because it could also either fix things or if not, they then can be ruled out.

 

[stefalopod]

Hey GMan,
I'll try the Bluetooth file you recommended.
I don't know how to identify whether my bios needs updating or how to find updated bios. Can you point me in the right direction?

 

[stefalopod]

Install this for the Bluetooth:

http://bluetoothinstaller.com/BluetoothDriverInstaller.exe

From:

Bluetooth Driver Installer - Get Bluetooth to work with the Microsoft Bluetooth stack

Tried this, it gave me an error message and said to report it to the developer.

 

[stefalopod]

Used a driver manager to track down some more drivers. Updated Bluetooth and GMA 500
Still BSOD though. It happens when I run a performance analysis too.

 

[GMan]

The best you can hope for is to track down the motherboard manufacturer's website to install the new bios from, since the maker of the whole machine is out of town. Type msinfo32 in the start menu, then press enter. Look at System model line for the motherboard.

Intel driver still crashing.

You can humor me here by trying something. At least it can rule out or in with this process. Go in the device manager. Right click on the (or all if > 1) Bluetooth entry(ies) and disable it/them.

Do the same exact thing for the Marvell network.

Reboot and test. If it crashes, post the crash dump so I can verify that all running drivers are well.

If they are all well, you definitely have some kind of hardware issue.

If it does crash, also go into your bios settings and set it to "Optimized Defaults". You can do this anytime - before or after bios update. This might help.


But ya - test with those drivers disabled and make a new crash dump. Or tell us of success - either way - and good luck as always!

 

[GMan]

Please humor with this too - I notice this involved in the crashes. igfxsrvc.exe

Your system does not need this, so we can get rid of it.

Install the trial of Dameware. Open up Dameware NT Utilites (not mini remote).

See your machine in the left side. If it is not there, add 127.0.0.1 to the favorites.

Then go to services | remove service. Check the box to show drivers also. Then look for Intel Graphics service or similar. Uninstall it then reboot.

Dameware - Downloads | NT Utilities and Mini Remote Control | DameWare

 

[GMan]

And the last bit of info for now:

Use !analyze -v to get detailed debugging information.

BugCheck 116, {859f9008, 8bc1f6d0, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
Probably caused by : igdkmd32.sys ( igdkmd32+106d0 )

Followup: MachineOwner

Bug check 116 is notorious. First thing to look at is overheating, as it is the most likely cause. (If you're so inclined, you might research how to open the machine and run it with a room fan on it to see if it crashes or not. Check the fan inside the machine too.) Other drivers can affect this happening too, and I already said how to disable culprits.

116 can definitely be caused by incorrect bios settings as well, and that has been covered.

It can not be ruled out that there is a defect in the hardware, but all other considerations must be dealt with to help finding out.

Another idea that can not hurt to try is to remove the battery if there is one. Perhaps if it is defective in some way, running the machine without it trying to recharge the battery might help in some way.

Just many ideas and things to try and go by.

116 is a tough one because there are tons of possible causes.

STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

BSOD - Windows 7 Forums