GT70 20D BSoD on win 8.1 - Nvidia driver

Hello,
I have several BSod (blue screen of death) under windows 8.1. (around one every days) i try to run driver verifier on ALL the drivers, one by one (it's take me few hours) and finally discover
that it's the driver for nvidia (nvlddmkm.sys exactly) that do all the time the BSoD ! (in driver verifier it's do BSoD few seconds after windows start)
I try everything possible, uninstalling nvidia driver (no more bsod but not perfect solution because compatible vga driver is used in place), using the last nvidia
driver (9.18.13.3182 but it's not work) and even the beta driver (not work either)
What the solution i have now ? is someone really have one GT70 20D and win8.1 with the laster nvidia driver without any BSoD ??
Also my win8.1 is a clean install from iso DVD
thanks by advance

Quote from: loki5100 on 03-January-14, 21:53:52
but i can't go to windows 8 ! the only previous version i can go (supported by our company) it's windows 7 ! but on the website on msi they said we can not update the bios with a windows 7 version when the bios was originally with a windows 8 version :( this can brick the laptop they say ... so what i can do ???
and sorry but when i read here :
http://www.msi.com/product/nb/GT70-2OD.html
it's clearly say it's work with Windows 8.1 !
So i buy it regarding this ! but it's false advertising because it's never work on windows 8.1 !
it's msi that choose to work with nvidia, so it's their responsibility to say that it's not compatible with windows 8.1 !
anyone with the windows 8.1 can try driver verifer on the nvidia driver to see that it's immediately crash after few minutes
First off, calm down. You're being rather irrational.
The BIOS doesn't matter if it's a Windows 7 or a Windows 8 BIOS. It will work with the OS. You can install Windows 7 perfectly fine on a GT70 20D with it having a Windows 8 or 8.1 BIOS. The bios doesn't effect the OS. The reason they state information regarding the OS is that GT70 0NX's can come with both Windows 7 or Windows 8 pre-installed. Those notebooks can only upgrade to the same BIOS that corresponds to the OS originally installed.
That being said, you don't seem to understand what I said. MSI cannot control NVidia's drivers. If the NVidia drivers don't work well with Windows 8.1, that doesn't mean the notebook is incompatible. The notebook runs Windows 8.1 just fine. The problem lies more with NVidia and the drivers provided for Windows 8.1. I've been over this a million times on many different websites, getting mad at MSI over NVidia's drivers is the same as getting mad at Microsoft for printer manufacturer's not putting out updated printer drivers for Windows 8.1. Microsoft can't control what those manufacturer's do. Get mad at them.
As zipper has said, it does work, but look at what he did...he went through many different versions of both the Intel and NVidia drivers. Most likely you will have to do the same. This is not something we can do for you, you're going to have to do it on your own.

Similar Messages

Problem with BSOD/Freezing probably related to Nvidia driver on Touchsmart IQ810

I have an HP Touchsmart IQ810, now a little elderly but otherwise going strong.
For the last couple of years now I've had a problem with occasional/frequent BSODs, one or two a week. Using crash dump analyser WhoCrashed this is almost certainly related to the driver for onboard Nvidia 9600GM video chip. The usual advice is to make sure you have the latest driver, but I've tried more recent drivers and they seem to make the problem worse - rather than BSODs, I get screen freezes at least once a day, so I've gone back to the old driver version.
I've run the hardware diagnostic tools and found no problems, I've even tried using MSI Afterburner to turn down the clock speed of the card to prevent overheating, but this makes no difference. BSODs/freezes sometimes occur not long after booting, so surely it can't be overheating.
I've pretty much had to put up with this but I would like it fixed. Any suggestions?

NVIDIA and RADEON Drivers, depending oin what they are doing can really point you in the right spot. If you are still having issues after fully removing and reinstalling the drivers then you are looking towards a Hardware issue. I would check the contact points on your motherboard and other hardware, this is looking more like an issue with your motherboard.
The biggest problems for example when it comes to computers with RADEON cards, because they are big like the NIVIDA cards; just moving your computer or bumping it can cause damage to your componets within your computer and cause issue like this. RADEONS cards are known to have screen tearing and different colored lines through the screen, another thing I would check is to make sure the swtich or voltage on you video card isn't flipped. If the switch is flipped the wrong way, if you end up forcing your card to hard with the little voltage it has running through it your computer WILL BSOD and MSI Afterburner won't even matter, usually voltage is a setting that you don't want to mess with when it comes to using that program, that is why they make switches on these cards.
If it was a driver issue, your machine won't not be BSOD. The reason why I say that is because BSOD happens to help you prevent further damage to your hardware and if the correct settings are not how they should be, something as simple as skype can cause your machine to do thing's it shouldn't. I've had many issues myself that I've gone through, being in the IT field as well I've seen this to be a common issue due to changing configurations or changing what you do on your computer.
You may of not changed anything but just a simple virus can cause programs to do what they are not meant to do.
Boot into safemode and see if you run into this issue still after running it for a few hours, with safemode as you know. You boot with the processes that you need to run the core functions of your computer. If nothing happens it is because your computer has taken a chill pill. If everything is good and you boot into your main OS then you start having this issue again then you know it IS hardware and setting's related. Little thing's like this will make a hug difference.
The switch also is verd had to find but it will be very small and colored white, if you still have the box you video card came in they should have it pointed out where it is.
I hope this helps, if you have any questions please ask.

GT70 20D blue screen of death on win 8.1

hello,
I have very often BSoD (blue screen of death) at random moment :(
microsoft team say that it's a know issue with graphic driver :(
* I already check all the memory, it's ok
* i already check the hard drive, it's ok
* i have no antivirus (i even uninstall windows defender)
* i have all the latest driver
* the computer is a new msi GT70 20D with intel hd 4600 + Nvidia GE force 780M + 32 GB memory + 3 ssd hard drive in raid 0
* clean install of windows 8.1 from the ISO DVD
The history of all the BSod that i receive :
122713-4812-01.dmp 12/27/2013 9:23:06 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff802`01061a45 ffffd000`26d619c0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14dca0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16452 (winblue_gdr.131030-1505) x64 ntoskrnl.exe+14dca0 C:\Windows\Minidump\122713-4812-01.dmp 8 15 9600 297,872 12/27/2013 9:24:07 PM
122513-5468-01.dmp 12/25/2013 2:40:20 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0000636f`6c65722e 00000000`00000002 00000000`00000008 0000636f`6c65722e ntoskrnl.exe ntoskrnl.exe+14dca0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16452 (winblue_gdr.131030-1505) x64 ntoskrnl.exe+14dca0 C:\Windows\Minidump\122513-5468-01.dmp 8 15 9600 297,832 12/25/2013 2:41:07 PM
122213-4718-01.dmp 12/22/2013 4:28:53 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000000 00000000`0000000d 00000000`00000000 fffff801`fa067eb7 igdkmd64.sys igdkmd64.sys+4f001 Intel Graphics Kernel Mode Driver Intel HD Graphics Drivers for Windows 8(R) Intel Corporation 10.18.10.3379 x64 ntoskrnl.exe+14dca0 C:\Windows\Minidump\122213-4718-01.dmp 8 15 9600 297,920 12/22/2013 4:29:32 PM
122213-4593-01.dmp 12/22/2013 1:00:28 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`002cae3c ffffd000`3787b460 00000000`00000000 win32k.sys win32k.sys+261e3c Multi-User Win32 Driver Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0 C:\Windows\Minidump\122213-4593-01.dmp 8 15 9600 297,832 12/22/2013 1:01:27 AM
121913-4406-01.dmp 12/19/2013 12:42:56 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff800`52edbc97 00000000`00000000 ffffffff`ffffffff igdkmd64.sys igdkmd64.sys+2f4980 Intel Graphics Kernel Mode Driver Intel HD Graphics Drivers for Windows 8(R) Intel Corporation 10.18.10.3379 x64 ntoskrnl.exe+14dca0 C:\Windows\Minidump\121913-4406-01.dmp 8 15 9600 297,808 12/19/2013 12:43:28 AM
is their any workaround ?
thanks by advance !
stéphane

Quote from: darkhawk on 28-December-13, 12:00:33
Go to the Intel website and use their automated driver installation there.
There's been a known issue with the Intel drivers that are included. Give that a try and report back.
yes i already do (http://www.intel.com/p/en_US/support/detect) and it's say that all my drivers are current
also in the windows update their is even a more recent drivers ... i try it also without success :(

GT70 20D Dragon Edition 2 Blinking led continuosly

Good night, i have a GT70 20D Dragon Edition 2. I have installed Windows 8.1 with clean installation but i have seen something that before to install win 8.1, my laptop not did. Now after the system start the power button led is blinking all time between amber and White continuosly. Anyone could tell me if this is normal or how i could to fix in amber colour as before to install win 8.1 ? i think, before with win 8.1, the color was amber all time after boot and start the SO.
I updatep the BIOS and EC firmware to Windows 8.1 BIOS verson " J", but not last versión ( R versión) because with last versión when the laptop enterd to sleep mode or push power off screen the laptop always restart and with " J version" BIOS works fine.
A greeting

White = Intel iGPU in use
Amber = NVidia Dedicated GPU in use
Generally, in Windows, you want it to be WHITE (ie Intel iGPU). This will give you the best battery life if mobile, and plugged in it really doesn't matter to be honest.
When playing games and doing other graphically intensive things, you want it to be AMBER, because then you get the best performance.
These settings can be changed within the NVidia driver, under the 3D Settings.
In the NVidia driver control panel, it's also possible to add a taskbar icon that allows you to see what programs are causing the NVidia GPU to be activated. That should help you in order to finding out what program is causing the NVidia video card to be enabled at boot like that, on and off.

Which Nvidia driver to install MSI gt70

I downloaded NVIDIA experience and it alerts me when the new driver is ready, so right now I installed 331.82 driver, is this correct?
On msi site the recommended drivers are much older, so what to do??
Also I am experienceing BSOD after win 8.1 and the error says something about NVD64 not sure, it happens like once per day, my computer gives me BSOD and then restarts

Quote from: garfiola on 20-November-13, 22:25:25
I downloaded NVIDIA experience and it alerts me when the new driver is ready, so right now I installed 331.82 driver, is this correct?
On msi site the recommended drivers are much older, so what to do??
Also I am experienceing BSOD after win 8.1 and the error says something about NVD64 not sure, it happens like once per day, my computer gives me BSOD and then restarts
Roll back to the 327.xx drivers. They were rather stable. If everything works on the 327.xx drivers, then I would stick to them until the next update is available and try that. If it doesn't work, roll back again. Drivers really are a trial and error event anymore. =/

[Solved] Starcraft 2 crashe with wine bunblebee nvidia driver

After the upgrade of yesterday (2013/05/12) my starcraft II (under wine) crashes.
After a downgrade of the nvidia driver ( and linux kernel ) my SCII is running once again perfectly, so I guess there is something wrong between the new nvidia driver (319.17-2) and the following package : bumblebee (3.2.1-1), wine (1.5.30-2) .
I'm a little buzzy actually and didn't take time to check deeply why, but if someone wants some data just ask
humhumhum
Edit: the package bunmblebee has been updated and solves the problem. Thanks.
Last edited by humhumhum (2013-06-03 11:59:43)

Do other GL programs work? e.g. glxgears. Is direct rendering enabled? (glxinfo | grep -i direct)

[SOLVED] Wow doesn't launch after lastest wine or latest nvidia update

I'm not exactly sure which. I'm guessing it's the wine update. I get the launcher, but when i click play, it never loads the game. I'm getting a bunch of errors, but I don't know if it's any more than usual:
Error: API mismatch: the NVIDIA kernel module has version 169.12,
but this NVIDIA driver component has version 169.09. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.
NVIDIA: Direct rendering failed; attempting indirect rendering.
fixme:advapi:SetSecurityInfo stub
fixme:win:EnumDisplayDevicesW ((null),0,0x34ed84,0x00000000), stub!
Error: API mismatch: the NVIDIA kernel module has version 169.12,
but this NVIDIA driver component has version 169.09. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.
NVIDIA: Direct rendering failed; attempting indirect rendering.
fixme:win:EnumDisplayDevicesW ((null),0,0x34ec8c,0x00000000), stub!
wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0025), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0027), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0029), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 002b), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 002d), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 002f), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0031), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0033), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0035), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0037), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0039), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 003b), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 003d), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 003f), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0041), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0043), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0045), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0047), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 000e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 000c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0013), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0015), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0017), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0012), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0021), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 001a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 001c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 001f), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0022), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0048), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 004a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 004c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 004e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0050), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0052), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0054), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0056), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0058), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 005a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 005c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 005e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0060), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0062), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0064), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0066), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0068), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 006a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 006c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 006e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0070), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0072), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0074), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0076), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0078), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 007a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 007c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 007e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0080), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0082), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0084), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0086), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0088), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 008a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 008c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 008e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0090), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0092), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0094), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0096), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0098), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 009a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 009c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 009e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00a0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00a2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00a4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00a6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00a8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00aa), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00ac), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00ae), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00b0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00b2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00b4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00b6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00b8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00ba), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00bc), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00be), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00c0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00c2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00c4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00c6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00c8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00ca), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00cc), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00ce), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00d0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00d2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00d4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00d6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00d8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00da), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00dc), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00de), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00e0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00e2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00e4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00e6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00e8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00ea), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00ec), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00ee), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00f0), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00f2), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00f4), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00f6), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00f8), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00fa), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 00fc), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 00fe), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0100), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0102), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0104), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0106), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0108), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 010a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 010c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 010e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0110), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0112), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0114), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0116), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0118), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 011a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 011c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 011e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0120), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0122), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0124), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0126), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0128), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 012a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 012c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 012e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0130), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0132), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0134), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0136), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0138), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 013a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 013c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 013e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0140), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0142), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0144), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0146), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 0148), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edcd564 (thread 014a), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 014c), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 014e), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0150), starting debugger...
wine: Unhandled page fault on read access to 0x0000002a at address 0x7edd8564 (thread 0152), starting debugger...
wine client error:0: init_thread failed with status c000011f
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 337 48") (1359)
Read the Wine Developers Guide on how to set up winedbg or another debugger
EDIT:
forgot to mention, I'm using 64-bit arch, and have tried both bin32-wine and bin32-wine-suse from AUR
Last edited by heleos (2008-03-06 19:34:18)

brebs wrote:
heleos wrote:Error: API mismatch: the NVIDIA kernel module has version 169.12,
but this NVIDIA driver component has version 169.09.
Get all these packages at consistent versions:
nvidia
nvidia-utils
lib32-nvidia-utils
I am finding that this is the most common cause of nVidia woes these days. Mirrors are being updated, but the utils and lib packages are often lagging behind the nvidia package- sometimes by 12 hours or more.

Gt70 20D unlocked

gt70 20D
BIOS E1763IMS.50T
EC Version 1763EMS1 Ver5.06
EC Build 08/28/2013
cpu i7-4700MQ
video card gtx 780mx
work your magic Svet
Paypal Transaction 6DK60401SF885853W

received it, working on it and will send back to you when its done after 2-3 hours

GT70 20D E1763IMS.70J

Hi there,
Is last bios for GT70 20D Raid is unlocked?
If yes i'm going to make donation.
Thanks
Bios Information:
EC Version:11763EMS1 Ver5.01

Quote from: Svet on 20-October-13, 21:54:59
hello,
it can be done, once donation is received can start work over it and to send back to you when its done.[normally after 2-3 hours]
if you want along with unlock can also update the intel sata fw to the latest version
Let's go
I've make a donation 1CA40332UK057045W
I'm going to search latest FW for Intel

GT70 20D bios update gone horribly wrong

Hi, I have never ran into issues like this previously, due to a number of problems with issues like the Dragoon software not detecting fan speeds, a number of the MSI apps saying unable to read from BIOS I decided to update the BIOS following the MSI instructions to the letter with the latest update up on the MSI site for the laptop. Well it didn't go well.
Hoping someone can help, my laptop is the GT70 20D with raid 0 configured running windows 8.1 pro, laptop was built with Windows 8 from factory. I booted into the BIOS and performed the UEFI update following these instructions. msi.com/files/pdf/Flash_BIOS_by_UEFI_BIOS_Setup_Utility_en.pdf
I got to stage 12 and the laptop itself powered down and restarted (It didnt get to stage 13 onwards and actually flash it) on the restart I simply get the hard drive light flash once, black screen and nothing. Please help I am in the UK and will be contacting MSI UK during office hours and suspect this might need a RMA but wanting to cover everything myself first, I work in IT and have performed this sort of thing plenty of times in the past and slightly annoyed at the min lol.

Quote from: spthacker on 20-March-14, 14:58:10
Just got my GT70-20D back from MSI after a bad flash, took 27 days in total
I had to pay as they stated that bios is classed as software and not covered by warranty!
you had to pay? is that a joke?
If you flash from their official guide do everything correctly and you brick it because their bios is faulty or motherboard and you have topay for it?
Wow, that is the most insane thing I have ever heard

BIOS Mod MSI 1763 GT70-20D whitebook with a 4700MQ and 780M

Hello svet,
hello community.
i have a MSI 1763 GT70-20D whitebook with a 4700MQ and 780M, sold by a german manufacturer called "Hyrican". The laptop performs well, but I would like to have all options. Yet, I don't know if its possible with my Notebook to flash a custom BIOS?
here is my information:
BIOS Version E1763IMT.70A (do i need a update? Is it old?)
BIOS Build 07/08/2013
EC VERSION 1763EG61 Ver5.06
EC BUILD 07/23/2013
intel core i7-4700mq @2.4ghz
intel haswell graphocs
dimm1 8192 ddr3
dimm2 8192 ddr3
donation: 6UM66611NA340921Y
thanks in advance and great job!
best regards

hello,
you mean to unlock all bios options or/and some other kind of customization?
Quote
BIOS Version E1763IMT.70A (do i need a update? Is it old?)
will pm you shortly for query

975X Plat BSOD on WinXP install with NVIDIA Graphics

Thought you might like to know of a config that does not allow WinXP Pro SP2 to install.
I had to swap out the Nvidia to get installed, otherwise installer took a BSOD while setting up drivers.
Once XP was installed, I put the Nvidia Graphics back in, XP tried to install the driver on login and the whole system took an immediate reset.
Then I booted to safe mode and was able to install the driver. System then worked fine .
To be on the safe side, I then downloaded the latest Nvidia driver and things are working fine. The config of interest:
Nvidia GeForce2 MX400 Graphics (old PCI board)
MSI 975X Platinum mobo
Pentium D 3.2 Ghz
Maxtor 160 SATA
Samsug DVD r/rw
generic cd r/rw
OCZ 800Mhz 1024MB dual channel

Quote from: Frankenputer on 20-January-07, 12:46:51
It would be even better if XP and SP2 are slipstreamed and the new disc, XP+SP2 is installed.
FULLY CONCUR!!! Installing a slipstreamed SP2 version is definitely the route to go.
What I do not understand is why someone cannot post a link to a fully slipstreamed SP2 version???
Those working should be able to just go and download it - reinstall using their own license and get on with it. Seems ruddy rediculous to make each of uns reinvent the wheel..........Excuse my rant - but reinventing wheels and thus making issues more difficult should not be an objective in life.
OFFER TO THOSE WHO DO NOT HAVE THE TIME TO DO THEIR OWN SLIPSTREAMING: If anyone wants an already prepared WINXP SP2 slipstreamed version (~605MB) - private message me and I can give u a link to our ftp site where the slipstreamed version I have stored the version I have been using since July 06 for XP SP2 reinstalling and onto new computers. Then u just burn the whole contents to a CD and stert setup. We consider this without copyright issues as you need your own licence key to install it. It should save you about 1 to 2 hours of work however, if you have never slipstreamed a version before. But for those of you who want to get your hands dirty - then google 'slipstream WINXP" and follow some of the reading and the instructions - (like I had did mid last year when DELL no longer suppoerted WINXP SP1).
Best of luck --Keith

MSi GT70 stuck at nVidia driver 311.48

I forget the quick way to post my specs (please refresh). I'm on hold now to speak with an MSi tech. The driver's on nVidia's website are 320.xx I've tried everything but the new WHQL does not recognized the graphics hardware?? Help

so!
First of all, you have to do that:
https://forums.geforce.com/default/topic/534575/geforce-drivers/official-nvidia-verde-notebook-gpu-driver-request-thread/
Request a support for your gpu.
Keep your ID, it'll be usefull for the next step.
Because of i can't past a link there, i'll make a Copy/Paste for a topic from another forum:
Quote
Steps:
1. Get your device ID: click on CONTROL PANEL, then CLICK on SYSTEM, then CLICK on DEVICE MANAGER
2. Under Other Devices/ (or if your video card already has a driver under Display Adapter) click on Video Adapter
3. Click on Details, Device Instance Id should already be selected
4. You will see something similar to this:
PCI\VEN_10DE&DEV_0DD1&SUBSYS_20421043&REV_A1\ 4&30DE1B
This has the detail about your specific video card maker, chipset and model
For instance in my system
VEN_10DE tells me the Vendor is 10DE which is the Vendor ID for NVIDIA
DEV_0DD1 tells me the Chipset is 0DD1 which is the Chipset GTX 460M
SUBSYS_20421043 tells me that this is the Specific MODEL GTX 460M in the Asus 73JW Laptop
5. If you haven't already done so then MANUALLY Download the latest NVIDIA driver for your video card from the NVIDIA website and run the install program. It will give your the error : "This graphics driver could not find compatible graphics hardware" Don't Panic.
6. GOTO the install directory. The default will be something like:
c:\nvidia\DisplayDriver\275.50\WinXP\ English\Display.Driver\
or
c:\nvidia\DisplayDriver\260.63\WinXP\ International\Display.Driver\
7. there will be many INF files there of the type:
nvaa.inf
nvac.inf
nvam.inf
nvao.inf
nvbl.inf
etc...
8. Pick any one of them (I picked nvam.inf) and make a backup copy then open the original in NOTEPAD or your favourite text editor
9. Scroll down until you see lines like:
[NVIDIA_Devices.NTx86.5.1]
%NVIDIA_DEV.0405.01% = Section001, PCI\VEN_10DE&DEV_0405&SUBSYS_15D21043
%NVIDIA_DEV.0405.02% = Section001, PCI\VEN_10DE&DEV_0405&SUBSYS_16341043
%NVIDIA_DEV.0407.01% = Section001, PCI\VEN_10DE&DEV_0407&SUBSYS_080117FF
%NVIDIA_DEV.0407.02% = Section002, PCI\VEN_10DE&DEV_0407&SUBSYS_15881043
%NVIDIA_DEV.0407.03% = Section003, PCI\VEN_10DE&DEV_0407&SUBSYS_16181043
%NVIDIA_DEV.0407.04% = Section004, PCI\VEN_10DE&DEV_0407&SUBSYS_16321043
%NVIDIA_DEV.0407.05% = Section001, PCI\VEN_10DE&DEV_0407&SUBSYS_17A21043
%NVIDIA_DEV.0407.06% = Section005, PCI\VEN_10DE&DEV_0407&SUBSYS_3D7B17AA
%NVIDIA_DEV.0408.01% = Section001, PCI\VEN_10DE&DEV_0408&SUBSYS_19021043
These files are for the most part listed BY the four digit HEXidecimal number that appears after DEV.
10. NOW CAREFULLY scroll down to the section that is similar to your chipset / DEV number
%NVIDIA_DEV.0CB1.01% = Section041, PCI\VEN_10DE&DEV_0CB1&SUBSYS_203C1043
%NVIDIA_DEV.0DEE.02% = Section042, PCI\VEN_10DE&DEV_0DEE&SUBSYS_15621043
%NVIDIA_DEV.0DEE.04% = Section042, PCI\VEN_10DE&DEV_0DEE&SUBSYS_15A21043
11. Take a look at this pattern. You will make a DEVICE ID for your Video Adapter and insert it here
The first part is the same for everyone:
%NVIDIA_DEV.
From Step 4
my DEV is 0DD1
so my device id so far is:
%NVIDIA_DEV.0DD1.01%
NOTE: id there is already DEVs same as yours then your line will be the next increment ie...
%NVIDIA_DEV.0DD1.02%, or %NVIDIA_DEV.0DD1.03%, etc
for the section just make it the same as the section where you're inserting it so I have:
%NVIDIA_DEV.0DD1.01% = Section042,
the next part is the same for everyone so you will have:
%NVIDIA_DEV.0DD1.01% = Section042, PCI\VEN_10DE&DEV_
add the rest (your DEV and SUBSYS numbers) so it matches your DEVICE ID and your finished device ID should look similar to this:
%NVIDIA_DEV.0DD1.01% = Section042, PCI\VEN_10DE&DEV_0DD1&SUBSYS_20421043
INSERT IT WILL LOOK LIKE THIS:
%NVIDIA_DEV.0CB1.01% = Section041, PCI\VEN_10DE&DEV_0CB1&SUBSYS_203C1043
%NVIDIA_DEV.0DD1.01% = Section042, PCI\VEN_10DE&DEV_0DD1&SUBSYS_20421043
%NVIDIA_DEV.0DEE.02% = Section042, PCI\VEN_10DE&DEV_0DEE&SUBSYS_15621043
12. NOW SCROLL DOWN to the [Strings] section it will look like this:
[Strings]
DiskID1 = "NVIDIA Windows 2000/XP (32 bit) Driver Library Installation Disk 1"
NVIDIA = "NVIDIA"
NVIDIA_DEV.0405.01 = "NVIDIA GeForce 9500M GS"
NVIDIA_DEV.0405.02 = "NVIDIA GeForce 9500M GS "
NVIDIA_DEV.0407.01 = "NVIDIA GeForce 8600M GT"
NVIDIA_DEV.0407.02 = "NVIDIA GeForce 8600M GT "
NVIDIA_DEV.0407.03 = "NVIDIA GeForce 8600M GT "
NVIDIA_DEV.0407.04 = "NVIDIA GeForce 8600M GT "
NVIDIA_DEV.0407.05 = "NVIDIA GeForce 8600M GT "
NVIDIA_DEV.0407.06 = "NVIDIA GeForce 8600M GT "
Same as before add a line in for your Video card:
NVIDIA_DEV.0CB1.01 = "NVIDIA GeForce GTS 360M"
NVIDIA_DEV.0DD1.01 = "NVIDIA GeForce GTX 460M - KAPs INF MOD"
NVIDIA_DEV.0DEE.02 = "NVIDIA GeForce GT 415M "
NVIDIA_DEV.0DEE.04 = "NVIDIA GeForce GT 415M "
NOTE: id there is already DEVs same as yours then your line will be the next increment ie...
NVIDIA_DEV.0CB1.01 = "NVIDIA GeForce GTS 360M"
NVIDIA_DEV.0DD1.01 = "NVIDIA GeForce GTX 460M"
NVIDIA_DEV.0DD1.02 = "NVIDIA GeForce GTX 460M - KAPs INF MOD"
NVIDIA_DEV.0DEE.02 = "NVIDIA GeForce GT 415M "
NVIDIA_DEV.0DEE.04 = "NVIDIA GeForce GT 415M "
13. SAVE FILE
14. If you have the file ListDevices.txt open it and add a line under the appropriate section
15. GO back and manually run setup.exe from where the NVIDIA files where extracted:
NOTE: DO NOT RUN THE DOWNLOADED APPLICATION OR YOUR WILL OVERWRITE EVERYTHING YOU'VE JUST DONE!
For Example Your setup program may be here:
c:\nvidia\DisplayDriver\260.63\WinXP\ International\setup.exe
THATS IT YOUR DRIVER WILL BE INSTALLED...ENJOY
It just come from the nvidia forum, enjoy it! It works

BSOD after installing NVIDIA driver (nvlddmkm.sys error)

Hi, I hope I'm posting this in the right place.
A few days ago I purchased an MSI GS60 044 (970m) laptop with Windows 8 preinstalled on it. I have an intense hatred for Windows 8 so I decided to do a clean install of Windows 7 using a disk I own. Everything was going well until I installed the NVIDIA graphics driver. The computer would run sluggishly and then Blue Screen with an error regarding "nvlddmkm.sys."
I got the drivers from MSI's website and followed the installation order on that page. I even tried downloading the latest driver from NVIDIA's website, but I got the same results.
Is anyone familiar with this issue? Is there anything I can do?
Thanks!
- Daniel

I really appreciate the help! I ended up reinstalling windows again and this time before installing the NVIDIA driver I installed the BIOS update that's provided under the "BIOS" tab on the GS60's support page. It's been installed for about 2 hours now with no crashes, so I hope that means it's fixed. I could just be getting lucky though, I'll post again tomorrow with results.
Unfortunately, now my LAN and WLAN drivers have stopped working. When I troubleshoot, windows says that there aren't any drivers detected. I have tried uninstalling and reinstalling both the bigfoot and intel drivers but neither are working. I just can't catch a break with this thing. >_<
In the event that I do have to send it to MSI, wouldn't the computer not be covered in their service anymore since I installed a different OS/formatted the original drives? I'm really hoping there isn't a hardware issue since I ordered the laptop brand new off of ebay.
Thanks again for all of the help!

Windows 8 64-bit install on 970a-g46 Mainboard AHCI and NVIDIA DRIVER issues

My Box:
MSI 970A-G46
BIOS 1.9 (AUG 2012) (Tried 1.11 but the nightmare started then)
AMD FX-6100 (STOCK SPEED AND SETTINGS) WITH OEM HSF
16GB PATRIOT VIPER 3 (1866) RUNNING @ (1600)
USED an EVGA 9800GT 1ST AND UPGRADED TO NVIDIA REFERENCE CARD GTX 550 Ti (1GB) WITH SAME ISSUES
90gb MonsterDigital Daytona SATA III SSD DRIVE (OS and minimal programs)
Antec HE 550
I am at a point of pulling my hair out. I decided to upgrade my system to enhance Diablo III game play. I got a combo deal on the mainboard and cpu, and thought the speed of the game caching on a SSD would also help. The first attempt which took a little struggle was Vista 64-bit. Eventually, I was able to get the OS to work with me, and it was smooth. Since M$ decided to offer the Windows 8 Pro upgrade for only $39.99, I thought, what do I had to lose. Well….lots of time. Now, I am not a newbie, though SSD drives haven’t been more than an interesting thought. So yes, I read many guides on everything from Trim enabled Win 7 and 8, and many other do’s and don’ts. What is driving me to the Netherlands of hell, is the installation and how buggy it has been. It boils down to drivers for the IDE/SATA/AHCI CONTROLLER. First, even thought it “sees” the SSD on installation drive selection, after pulling the USB installation drive, the system forgets it, and there is a “problem with the boot sector”. If you load the driver from the AMD site, it lets the install occur “fine”, but there is an issue with that driver which causes an irq conflict which leads to D3 audio issues and freeze ups. I did finally get things in order (not sure which driver I choose for that), and things were smooth, except I tried to install the GTX 550 ti and that led to a corrupt file error, which the system runs a check disk and cycles the “preparing to repair” and “diagnosing PC” a few times and never allows me to enter SAFE MODE (shift+f8), to disable the NVIDIA driver that is buggy, and doesn’t allow for the NVIDIA Control Panel to install without losing video, and starts the repair cycles again… Leading to ANOTHER RE-INSTALL...
My question, for the Windows 8 Pro installation on the 970a-G46 mainboard and then after install is complete, which driver is the correct choice for the AHCI/SATA Controller? All I find is Win7 64-bit AHCI inf’s, and SB7XX 64-bit inf’s (no SB950 INF). The Driver disk which came with the mainboard is very dated pre Win 8 stuff, ASMEDIA X106 which are not recognized by the OS as written for Win 8. AMD’s latest drivers are the ones causing the IRQ type lags and corruption.
What version, build and type of Windows 8 installations have you used on this mainboard, and what drivers allowed you install it without the above conflicts? Your input may decrease my insanity… So, thank you in advance…

Quote from: m0r9h3u5 on 28-January-13, 12:11:16
I understand what you are telling me, only the generic drivers deliver subpar results. What is the point of running those drivers instead of windows 8 certified drivers written for said devices. My last install is functioning better, but still windows update fails every attempt, the apps i install (ie. weather bug) on the start screen wont load... to me windows 8 is a big fail....but that is just my view...
OK...I also own the 970a G46, and my upgrade experience from Win7 x64 AHCI to Win8 x64 AHCI was flawless the first time. No problems at all. You are running an AMD chipset board with a nVidia gpu, which means that your chipset drivers are not automatically updated with every gpu driver update you do--this would happen automatically if you owned an AMD gpu because AMD includes them in its gpu driver install packages. But--all you have to do to get the proper drivers for your motherboard is go here and download them. You only need the *chipset drivers* from this page--you do not need the RAID drivers, of course. That's it. It's no big deal, and back in the days when nVidia was making motherboard chipsets you had to separately download both the motherboard chipset drivers from nVidia and the AMD gpu drivers from AMD if you did not also own a nVidia gpu.
From your description of your problems it sounds like your installation of Win8 is hosed and you need to format C:\ and clean install from scratch, anyway, so...
A note about AHCI--the *ideal* way to install the AHCI drivers is prior to installing your OS for the first time, you enter the UEFI and set "AHCI" in the appropriate place, instead of IDE, and *then* you reboot from DVD and install your OS which will automatically install the correct AHCI driver from Windows. After the driver installation is complete you should then install the updated 970a drivers from AMD as linked above.
However, it is actually very easy to activate and install AHCI *after* you have installed Windows in normal IDE mode:
To enable AHCI in existing Windows 8 IDE Installation's
Caution: Do NOT enable AHCI in UEFI prior to making the following changes in your Registry! If you had AHCI enabled alreadyin UEFI, disable it first and restart your computer!
Use WinKey + R and type Regedit in the command line and hit the Enter key, this will open the Registration Editor.
Go to:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/iaStorV
right click on Start, select Modify and set Data Value to 0
Close Registration Editor and restart computer.
While booting, open the UEFI Page and set the SATA Mode to AHCI from IDE
Save UEFI settings and restart.
Windows will now install the AHCI drivers automatically and they should work without issues.
In order to avoid installation problems just like you have been experiencing, here is what I would do in your shoes:
1) Set UEFI for normal IDE drive mode
2) Reboot into IDE mode and install your OS
3) After you have finished with the installation, you should be having no troubles in IDE mode. Then go to the instructions above on how to properly enable AHCI *after* you have installed Windows 8 in normal IDE mode.
4) After everything is coming up roses in AHCI mode and you are having no problems, then install the AMD chipset drivers as linked above and you are golden.
Those 4 steps worked perfectly for me the first time (the first time I got them right, that is...).
There's nothing wrong with Win8--this is strictly operator error caused by insufficient research into what AHCI is and how to properly enable it. The Internet has some bad info on Win8 registry settings for AHCI because of the developer preview and the consumer preview versions of Win8 that Microsoft released to the public prior to the final shipping build--many "instructions" for Win8 are therefore not valid for the shipping version of Win8. At first I made some of the same goofs that you did, but now you get to benefit from my hard-won experience... Good luck! Should work like a charm. And, registry AHCI is done differently in Win8 than it is done in Win7 or Vista. Also, the registry settings relative to AHCI in Windows 8 for AMD are different from the registry values that must be changed for an Intel controller.
Parenthetically, My FX-6300 (Vishera) will be here in a couple of days! Yeah!

GT70 20D BSoD on win 8.1 - Nvidia driver

Similar Messages

Maybe you are looking for