Windows 10 + Nvidia card problems
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=734
Printed Date: 22 Dec 2024 at 6:10pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Windows 10 + Nvidia card problems
Posted By: maffle
Subject: Windows 10 + Nvidia card problems
Date Posted: 29 Aug 2015 at 11:42am
|
Hello, I have a Z77 Extreme6 and a GTX970, and a friend who has a Z87 Pro3 and a GTX770. We both have the same problem that we get error code 113 bluescreens during Nvidia driver setup, and another black screen issue. I have talked to Nvidia support, and they said I should contact Asrock because they would need to publish a bios update to fully support Windows 10 or fix some issues with it. For example, it can happen that the PC doesnt boot anymore (black screen), when I enable fast boot and disable CSM mode. This is definitely a bug with the BIOS and needs a fix. Please release an updated microcode, ME and VBIOS, also UEFI bug/security fixes. Would be nice hearing some feedback on this. Here is the 113 bsod debug log: 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 000000000000001f, The subtype of the bugcheck: Arg2: ffffe00098b52b80 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ SYSTEM_SKU: To Be Filled By O.E.M. SYSTEM_VERSION: To Be Filled By O.E.M. BIOS_DATE: 07/01/2013 BASEBOARD_PRODUCT: Z77 Extreme6 BASEBOARD_VERSION: BUGCHECK_P1: 1f BUGCHECK_P2: ffffe00098b52b80 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CPU_COUNT: 8 CPU_MHZ: d48 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3a CPU_STEPPING: 9 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x113 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10240.9 amd64fre LAST_CONTROL_TRANSFER: from fffff801c1ff3c3d to fffff80359965d00 STACK_TEXT: ffffd000`afe54828 fffff801`c1ff3c3d : 00000000`00000113 00000000`0000001f ffffe000`98b52b80 00000000`00000000 : nt!KeBugCheckEx ffffd000`afe54830 fffff801`c207c63f : ffffe000`98b52b80 ffffe000`9c46c401 ffffe000`9c46c4b0 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd ffffd000`afe54870 fffff801`c671fe3f : ffffe000`98c14ba0 ffffd000`afe549a0 ffffe000`9c46c4b0 ffffe000`98bbe840 : dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x8f ffffd000`afe548a0 fffff801`c672531b : ffffe000`98c0b000 ffffffff`00000000 ffffc000`86eadb40 ffffe000`9c46c4b0 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa3f ffffd000`afe54a40 fffff801`c6728f5d : ffffe000`98c0b000 ffffe000`98c0b000 00000000`00000000 ffffd000`afe54b99 : dxgmms2!VIDMM_WORKER_THREAD::ProcessPendingTerminations+0xa3 ffffd000`afe54af0 fffff803`598fe948 : ffffe000`95679800 ffffd000`afe54c00 fffff803`59b7b100 fffff803`5996ad00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x9c1 ffffd000`afe54c00 fffff803`5996ade6 : fffff803`59b7b180 ffffe000`98bbe840 fffff803`59bf1740 00000000`00000000 : nt!PspSystemThreadStartup+0x58 ffffd000`afe54c60 00000000`00000000 : ffffd000`afe55000 ffffd000`afe4f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f fffff801`c207c63f eb03 jmp dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x94 (fffff801`c207c644) SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 55bebfed BUCKET_ID_FUNC_OFFSET: 8f FAILURE_BUCKET_ID: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete BUCKET_ID: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete PRIMARY_PROBLEM_CLASS: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!adapter_render::notifydeferreddestructioncomplete FAILURE_ID_HASH: {5460b617-b6dd-456e-0f7a-45a24c5cf63d} Followup: MachineOwner --------- |
Replies:
Posted By: parsec
Date Posted: 29 Aug 2015 at 4:29pm
We need to sort out what is going on with at least two issues you seem to be having. The easier one first, the use of Fast Boot and disabling CSM. If you are disabling CSM, it sounds like you are trying to use the Ultra Fast setting of the Fast Boot option, but you did not state what Fast Boot setting you are using. How did you install Windows 10? By the upgrade method or fresh/new installation? If a new installation, did you install by booting the installation disk, or use a USB flash drive created from a Win 10 iso file or the Win 10 disk image? If you used the upgrade to Win 10 method, was your previous OS installation configured to use the EFI bootloader? I'm trying to determine if Win 10 was installed for EFI booting. The Ultra Fast boot setting with CSM disabled can only be used if Win 10 was installed to use the EFI bootloader. What is the entry for the OS boot drive in the boot order list that you are using? You mentioned a VBIOS update, which is normally needed by a video source to be GOP compatible. GOP video protocol compatibility of the VBIOS is required when using the EFI bootloader. The problem with your request is the VBIOS that is included in the UEFI/BIOS of the boards you listed is the VBIOS for the Intel integrated graphics in the processors you use. When you use a video card, it is the VBIOS of the video card that is used, and it must be GOP compatible in order to disable CSM. I had to update the VBIOS of a GTX 650 I used with an ASRock Z77 Extreme4 board before I could disable CSM. The factory VBIOS version did not support GOP. Intel integrated graphics as far back as the Sandy Bridge HD 3000 series are GOP compatible, as long as the board's UEFI/BIOS has a compatible VBIOS. The ASRock Z77 Extreme series of boards all received a VBIOS update for the Intel graphics in 2012. The Z77 Extreme6 board got that update in UEFI/BIOS version 1.90. We don't know what UEFI/BIOS version you are using with your Z77 Extreme6 board. Nvidia based video cards of the 700 and newer series should/can be GOP compatible from the factory, but that can depend on the card's manufacture. No idea who made the cards you listed. I've used both the Intel graphics and the GTX 650 with updated VBIOS, with my Z77 Extreme4 board with CSM disabled, and it boots and works fine. An ASRock Z87 board will have a GOP compatible VBIOS for the Intel graphics out of the box from the factory. A good test for you is trying to boot with CSM disabled, while using the Intel integrated graphics. If it works fine, then the VBIOS problem is the video card's. If booting fails using the Intel graphics with CSM disabled, then that normally means your Windows installation is not configured for EFI booting. That means you must use CSM, and cannot use the Ultra Fast boot setting. Given the information you provided so far, there is no proof a UEFI/BIOS bug exists on those boards. An "updated microcode, ME and VBIOS...", are things that would be provided by Intel only, if they were actually needed. The "UEFI bug/security fixes" you mentioned are two different things, one of which (security fixes) is mentioned in that statement for the first time in your post. What security fixes are you referring to? Next the apparent driver problem. We know you and your friend are using Windows 10, and you had a 113 BSOD during a driver installation. While the "dxgkrnl" is part of an Nvidia driver, we can see this in the Debugging Details you posted: DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT What driver version are you using, and from whom/where was it downloaded? Sure doesn't appear to be a Windows 10 driver. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
maffle wrote:Posted By: maffle
Date Posted: 30 Aug 2015 at 2:04am
|
Hello, thanks for trying to help. You asked a lot of things, but sadly none of them are relevant in my oppinion. I am sorry I didnt mentioned them from the beginning. Ill try to go through them: - I dont think I used Ultra Fast. After a normal/random reboot, the PC didnt boot anymore. With black screen I dont mean during OS boot, I mean no signal from the beginning, no Asrock logo, nothing. PC also seemed to be frozen, numlock toggle didnt work anymore. I never changed anything with the bios in years it is all default no OC ect ect ect.... Fast boot worked fine with my previous card, I just bought the new GTX970 two weeks ago. It also worked for a few hours, then black screen happened after a reboot. Soft reset, hard reset power off on all didnt change the state anymore of the black screen. I then did a bios reset and it worked again. I set all my settings to where they were, including fast boot, saved, and black screen again / pc frozen. Did bios reset again, left CSM enabled, no black screen issues anymore since then. - It doesnt matter how I installed Windows 10, but I am on my 4th installation right now, so yes, it si a clean install. - Previous Windows 8.1 was installed with fast boot though, but like I said, this isnt connected to the issue. - MSI GTX970 Gamer 4G, bought two weeeks ago, has newest VBIOS..., so again, nope, 900er series should be totally compatible to GOP right? Right. - Mainboard of course has "newest bios"... from 2013, there were no updates since then anymore. I saw a beta bios was released this August 2.80E which though just had a fix of "Supports NVMe Configuration", I installed it but didnt help anything it seems. - Werent there lots of security issues in UEFI detected over the last few years? Im sure it happened after 2013. - The more important problem is the bsod, ..., it is of course the latest Windows >10< Nvidia driver... 355.60 http://www.geforce.com/drivers/results/89125 Yes Ive noticed that WIN8 too in the debug, maybe Nvidia forgot to change this string text in the inf files. Or it is normal that it says WIN8, because WIN8 are technically WIN10 drivers, even WIN7 are. - I have some feeling that is connected to the onboard iGPU and Lucid Virtu Universal MVP stuff, which Nvidia cards arent compatible with. I tried to set the "multimonitor iGPU" option in the bios to disable, which didnt help though. Why is there no option in the bios, to completely disable the onboard Intel gpu?
|