Windows 8 bootup crash, cause NVIDIA Driver.

Hello people, it's me again. I just used bootcamp assistant on OS X 10.9.1 and installed Windows 8.1 Pro. I installed the BootCamp 5 drivers and it said to restart, and I did so, but when it restarted back into windows it shows the windows bootup screen and fades to black, but when it fades to black the screen shuts off and it restarts with the chime, and goes back through the same loop. I tried uninstalling every driver through safe mode until I found out it was the NVIDIA GeForce 9400m driver. I tried downloading the driver from the NVIDIA website, Windows update, BootCamp 5 drivers, BootCamp 4 drivers, the disk that came with my Mac but it ends up the same outcome. Could someone please help me, or if someone has the same problem but fixed it could tell me.
-JP

While we all have MacBooks in this forum not all of us use BootCamp. There's a BootCamp Support Community where everybody uses BootCamp. You should also post this question there to increase your chances of getting an answer.
https://discussions.apple.com/community/windows_software/boot_camp

Similar Messages

IE crashed with NVidia driver

IE crashes when use nvidia driver. It seems like IE10 use driver not properly or
Disabling hardware acceleration solves the problem.
IE stack trace:
13a290b0 5f6b41ae nvwgf2um+0x1a2519
13a29368 5f6c5226 nvwgf2um+0x1841ae
13a29538 5f6ba139 nvwgf2um+0x195226
13a29558 5f5f4e20 nvwgf2um+0x18a139
13a29570 605c279d nvwgf2um+0xc4e20
13a29584 60922e8b d3d11!CContext::ID3D11DeviceContext1_Draw_<6>+0x1d
13a297e0 60923356 d2d1!CD3DDeviceLevel1::DrawDynamicVB+0x146
13a29850 6091e3c1 d2d1!CD3DDeviceLevel1::ProcessDeferredOperations+0x197
13a298b4 6091e09f d2d1!CHwSurfaceRenderTarget::FlushQueuedOperations+0x1ee
13a298d0 609d7473 d2d1!CHwSurfaceRenderTarget::ProcessBatch+0xb1
13a29910 6090c858 d2d1!CBatchSerializer::FlushInternal+0x52
13a29924 609aea10 d2d1!DrawingContext::FlushInternal+0x11
13a2993c 60966a47 d2d1!BatchTrackedObject::OnChange+0x2d
13a29978 72d28ada d2d1!CDIEffect::SetInput+0xc0
13a29990 72d29392 mshtml!CDXEffectBase::ConnectInput+0x16
13a299a8 72d29388 mshtml!CDXEffectBase::DisconnectInputs+0x33
13a299b8 72d29388 mshtml!CDXEffectBase::DisconnectInputs+0x29
13a299c8 72d29388 mshtml!CDXEffectBase::DisconnectInputs+0x29
13a299d8 72d29337 mshtml!CDXEffectBase::DisconnectInputs+0x29
13a299ec 72dd1155 mshtml!CDXEffectGraphImage::UnlockFromRender+0x1f
13a29ad4 73047e1d mshtml!CDXRenderTarget::DrawImageInternal+0x501
13a29ba0 72de73dc mshtml!CDXRenderTarget::TileImage+0xf3
13a29c94 72de8403 mshtml!CDXRenderTarget::Gaussian+0x367
13a29ecc 72de7980 mshtml!CDispSurface::RenderShadows+0xa3a
13a2a0e8 72cafb7b mshtml!PositionAndDrawShadows<0>+0x2be
13a2a204 72caf9e6 mshtml!HtmlLayout::ContainerBox::PositionAndDrawShadowOutset+0x135
13a2a28c 72caf7c8 mshtml!HtmlLayout::ContainerBox::DrawShadowsOutset+0x180
13a2a2c8 72b6d484 mshtml!HtmlLayout::ContainerBox::DrawClientShadowOutset+0xe1
13a2a66c 72b67cd6 mshtml!CDispContainer::DrawSelf+0x130a
13a2a980 7303ab9d mshtml!CDispNode::Draw+0x8a4
13a2aa34 7303aaae mshtml!CDispProxyNode::DrawSelf+0x24c
13a2aaf0 72b6c8c7 mshtml!CDispProxyNode::Draw+0x1ab
13a2ab5c 72ca3c64 mshtml!CDispContainer::DrawChildren+0x153
13a2ac38 72b6a341 mshtml!CDispContainer::DrawContentAdvanced+0x40e
13a2afd4 72b67cd6 mshtml!CDispContainer::DrawSelf+0xca8
13a2b2e8 72b6c8c7 mshtml!CDispNode::Draw+0x8a4
13a2b354 72b6cf98 mshtml!CDispContainer::DrawChildren+0x153
13a2b6ec 72b67cd6 mshtml!CDispContainer::DrawSelf+0xfd6
13a2ba00 72b6c8c7 mshtml!CDispNode::Draw+0x8a4
13a2ba6c 72b6cf98 mshtml!CDispContainer::DrawChildren+0x153
13a2be04 72b67cd6 mshtml!CDispContainer::DrawSelf+0xfd6
13a2c118 72d35870 mshtml!CDispNode::Draw+0x8a4
13a2c1c4 72bc6b95 mshtml!CDispRoot::DrawEntire+0x7f
13a2c3c4 72b687cf mshtml!CDispRoot::DrawRoot+0x346
13a2c53c 72b669da mshtml!CView::RenderViewWithPostTransform+0x414
13a2c774 72e241ff mshtml!CDoc::PaintWorker+0x49b
13a2c780 7308989f mshtml!CDoc::PaintInPlace+0x25
13a2c7a0 72b62507 mshtml!CPaintController::RunRenderingLoop+0x4a
13a2c7b8 72b61f2b mshtml!CPaintController::OnUpdateBeat+0x25
13a2c7d8 72b62672 mshtml!CPaintBeat::OnBeat+0x17a
13a2c7f0 72b61b59 mshtml!CPaintBeat::OnVSyncMethodCall+0x51
13a2c848 72b2a719 mshtml!GlobalWndOnPaintPriorityMethodCall+0x179
13a2c894 752c62fa mshtml!GlobalWndProc+0xd3
13a2c8c0 752c7316 user32!InternalCallWinProc+0x23
13a2c938 752c6de8 user32!UserCallWinProcCheckWow+0xd8
13a2c994 752c6e44 user32!DispatchClientMessage+0xe0
13a2c9d0 7713010a user32!__fnDWORD+0x2b
13a2c9e4 009e7560 ntdll!KiUserCallbackDispatcher+0x2e
13a2ca4c 752c788a 0x9e7560
13a2ca5c 638a37f4 user32!DispatchMessageW+0xf
13a2fbe0 63916990 ieframe!CTabWindow::_TabWindowThreadProc+0x4ad
13a2fca0 74e0627b ieframe!LCIETab_ThreadProc+0x377
13a2fcb0 674331a9 iertutil!IsUserAdmin+0x61
13a2fcd4 75e5336a IEShims!NS_CreateThread::DesktopIE_ThreadProc+0x66
13a2fce0 77159f72 kernel32!BaseThreadInitThunk+0xe
13a2fd20 77159f45 ntdll!__RtlUserThreadStart+0x70
13a2fd38 00000000 ntdll!_RtlUserThreadStart+0x1b

Hi，
Hardware Acceleration (also called GPU rendering) is used to increase the program performance, but sometimes this feature can cause problems on old computers and even some new computers, depends on the display drivers, manufactured BIOS, chipset drivers,
some outdated video cards/chips and drivers will not support this feature, therefor, users have to update driver or replace it with a more appropriate video card\driver, or just turn off this feature.
Yolanda Zhu
TechNet Community Support

HTML5 media such as HTML5-enabled YouTube and the Ingress Intel page causes Firefox to crash my nVidia driver.

I've began to notice that HTML5 media causes strange issues with my graphics drivers. Watching HTML5 videos on YouTube or browsing the Ingress Intel page causes Firefox to lock up after a period of a few minutes, though I can still hear audio and use keybindings, I'm not able to move my mouse onto the desktop that Firefox is currently on (I use two monitors). I'm forced to reboot my PC to resolve the error.
This appears in the event viewer when the issue occurs.
"The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video5
!06d7(2640)"
I've tried resetting Firefox, reinstalling video drivers, etc. It only happens with HTML5, not Flash.

Yep, that fixed it.

Acrobat causes Nvidia driver to stop and recover

I accidentally started this in the Photoshop forum in an nvidia thread - I was told to move it, so here I am. Apologies.
I am running an EVGA nVidia GeForce 7200GS 512 MB VGA/DVI/TV-out PCI-Express Video Card (model# 512-P2-N430-LR).
Windows 7 (32bit), 2X2.6ghz, 4gb ram, dual monitors.
I'm running Adobe Acrobat 9.0.0 Pro, as a part of Web Premium CS4.
When I run Adobe Acrobat, I see the driver fail and recover - 11 times in the last 30 days. It's often when I'm using Acrobat in a pretty heavy handed manner, like opening 3 large documents at once (but not always that heavy). I updated my driver on June 6th and it still happens.
Event viewer details are:
Log Name:      System
Source:        Display
Date:          6/23/2010 12:33:49 PM
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
I'm installing roughly 1GB of updates for CS4 right now, so hopefully the issue will stop.
I realize this is a video card issue, since it is stopping, but I also realize this is a video card stopping only with the help of Acrobat. Photoshop, Dreamweaver, Fireworks and Flash all have had no trouble from what I can recall.
I have posted a similar issue at the nvidia website, but they have a horrible website and I can't even tell if they support the 7200.
Thanks so much for any help in finding a solution.
Joby

9.3.3 apparently fixed it. I haven't had it happen since I updated and the usual reproduction doesn't stop the driver.
Thanks for the help!!!

I installed Windows 8.1 bootcamp but I'm having problems with the nvidia driver

Windows 8.1 is boot camped and it works perfectly, Almost. Ill find myself scrolling, usually with the trackpad, sometimes with a mouse, and the screen will go black, flicker, and resume. It will also stop the driver in games when i press keys too quickly. It seems to be an input problem but i don't see how the keyboard and trackpad affect the video driver. I get an error message that says "NVIDIA driver has temporarily stopped but has recovered." I have installed the latest drivers from the NVIDIA Website as well as all windows 8.1 updates. Sometimes its bad enough that the computer reboots completely. Its getting frustrating as i can't complete tasks or enjoy recreational time. Has anyone had this issue and been able to fix it?
NVIDIA driver fails but recovers(or Reboots computer) when
     When i scroll through webpages using the trackpad or mouse, usually when i scroll quickly
     or input keystrokes quickly while running programs, usually games
Computer
     Macbook Pro(mid 2010)
     Intel core i5 (built in geforce 330M)
     OS X Yosemite 10.10.1
     Bootcamp 5.1.2
     Windows 8.1

Is the current nVidia driver the one that came with Bootcamp?

[SOLVED] nvidia driver causes blank screen soon after boot

Hi,
I have a NVIDIA 560 and was originally using the nouveau driver, but that gave slow performance when doing anything (eg. resizing windows), so I installed the nvidia driver instead by following the wiki section:
https://wiki.archlinux.org/index.php/NV … au_drivers
by essentially just following the scripts given there. After switching to nvidia, the screen goes blank soon after boot. I get back into the system by using nomodeset in menu.cfg.
My question is how do I even begin to find the problem, eg. what log file(s) should I look in and post?
Thanks
Last edited by mark1977 (2012-08-19 17:38:42)

Yes it's the 560 Ti. Thanks I just installed straight from the repos. I've also installed cuda-sdk and cuda-toolkit. I've compiled the libraries inside /opt/cuda-sdk/CUDALibraries fine.
No I go to compile the sdk examples by running make in /opt/cuda-sdk/C and get the following error:
# make
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/shared'
make[1]: Leaving directory `/opt/cuda-sdk/shared'
make[1]: Entering directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Leaving directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Entering directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
/usr/bin/ld: cannot find -lcuda
collect2: error: ld returned 1 exit status
make[1]: *** [../../bin/linux/release/simpleTextureDrv] Error 1
make[1]: Leaving directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
make: *** [src/simpleTextureDrv/Makefile.ph_build] Error 2
The Makefile itself essentially seems to just include the file /opt/cuda-sdk/C/common/common.mk, which is:
# Copyright 1993-2011 NVIDIA Corporation. All rights reserved.
# NVIDIA Corporation and its licensors retain all intellectual property and
# proprietary rights in and to this software and related documentation.
# Any use, reproduction, disclosure, or distribution of this software
# and related documentation without an express license agreement from
# NVIDIA Corporation is strictly prohibited.
# Please refer to the applicable NVIDIA end user license agreement (EULA)
# associated with this source code for terms and conditions that govern
# your use of this NVIDIA software.
# Common build script for CUDA source projects for Linux and Mac platforms
.SUFFIXES : .cu .cu_dbg.o .c_dbg.o .cpp_dbg.o .cu_rel.o .c_rel.o .cpp_rel.o .cubin .ptx
# Add new SM Versions here as devices with new Compute Capability are released
SM_VERSIONS := 10 11 12 13 20 21 30
CUDA_INSTALL_PATH ?= /opt/cuda-toolkit
ifdef cuda-install
CUDA_INSTALL_PATH := $(cuda-install)
endif
# detect OS
OSUPPER = $(shell uname -s 2>/dev/null | tr [:lower:] [:upper:])
OSLOWER = $(shell uname -s 2>/dev/null | tr [:upper:] [:lower:])
# 'linux' is output for Linux system, 'darwin' for OS X
DARWIN = $(strip $(findstring DARWIN, $(OSUPPER)))
ifneq ($(DARWIN),)
SNOWLEOPARD = $(strip $(findstring 10.6, $(shell egrep "<string>10\.6" /System/Library/CoreServices/SystemVersion.plist)))
LION = $(strip $(findstring 10.7, $(shell egrep "<string>10\.7" /System/Library/CoreServices/SystemVersion.plist)))
endif
# detect 32-bit or 64-bit platform
HP_64 = $(shell uname -m | grep 64)
OSARCH= $(shell uname -m)
# Basic directory setup for SDK
# (override directories only if they are not already defined)
SRCDIR ?=
ROOTDIR ?= ..
ROOTBINDIR ?= $(ROOTDIR)/../bin
BINDIR ?= $(ROOTBINDIR)/$(OSLOWER)
ROOTOBJDIR ?= obj
LIBDIR := $(ROOTDIR)/../lib
COMMONDIR := $(ROOTDIR)/../common
SHAREDDIR := $(ROOTDIR)/../../shared/
# Compilers
NVCC := $(CUDA_INSTALL_PATH)/bin/nvcc
CXX := g++ -fPIC
CC := gcc -fPIC
LINK := g++ -fPIC
# Includes
INCLUDES += -I. -I$(CUDA_INSTALL_PATH)/include -I$(COMMONDIR)/inc -I$(SHAREDDIR)/inc
# Warning flags
CXXWARN_FLAGS := \
-W -Wall \
-Wimplicit \
-Wswitch \
-Wformat \
-Wchar-subscripts \
-Wparentheses \
-Wmultichar \
-Wtrigraphs \
-Wpointer-arith \
-Wcast-align \
-Wreturn-type \
-Wno-unused-function \
$(SPACE)
CWARN_FLAGS := $(CXXWARN_FLAGS) \
-Wstrict-prototypes \
-Wmissing-prototypes \
-Wmissing-declarations \
-Wnested-externs \
-Wmain \
# architecture flag for nvcc and gcc compilers build
CUBIN_ARCH_FLAG :=
CXX_ARCH_FLAGS :=
NVCCFLAGS :=
LIB_ARCH := $(OSARCH)
# Determining the necessary Cross-Compilation Flags
# 32-bit OS, but we target 64-bit cross compilation
ifeq ($(x86_64),1)
NVCCFLAGS += -m64
LIB_ARCH = x86_64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
else
# 64-bit OS, and we target 32-bit cross compilation
ifeq ($(i386),1)
NVCCFLAGS += -m32
LIB_ARCH = i386
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
ifeq "$(strip $(HP_64))" ""
LIB_ARCH = i386
NVCCFLAGS += -m32
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
LIB_ARCH = x86_64
NVCCFLAGS += -m64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
endif
endif
endif
# Compiler-specific flags (by default, we always use sm_10, sm_20, and sm_30), unless we use the SMVERSION template
GENCODE_SM10 := -gencode=arch=compute_10,code=\"sm_10,compute_10\"
GENCODE_SM20 := -gencode=arch=compute_20,code=\"sm_20,compute_20\"
GENCODE_SM30 := -gencode=arch=compute_30,code=\"sm_30,compute_30\"
CXXFLAGS += $(CXXWARN_FLAGS) $(CXX_ARCH_FLAGS)
CFLAGS += $(CWARN_FLAGS) $(CXX_ARCH_FLAGS)
LINKFLAGS += -L/usr/lib
LINK += $(LINKFLAGS) $(CXX_ARCH_FLAGS)
# This option for Mac allows CUDA applications to work without requiring to set DYLD_LIBRARY_PATH
ifneq ($(DARWIN),)
LINK += -Xlinker -rpath $(CUDA_INSTALL_PATH)/lib
endif
# Common flags
COMMONFLAGS += $(INCLUDES) -DUNIX
# If we are enabling GPU based debugging, then we want to use -G, warning that this
# May have a significant impact on GPU device code, since optimizations are turned off
ifeq ($(gpudbg),1)
NVCCFLAGS += -G
dbg = $(gpudbg)
endif
# Debug/release configuration
ifeq ($(dbg),1)
COMMONFLAGS += -g
NVCCFLAGS += -D_DEBUG
CXXFLAGS += -D_DEBUG
CFLAGS += -D_DEBUG
BINSUBDIR := debug
LIBSUFFIX := D
else
COMMONFLAGS += -O2
BINSUBDIR := release
LIBSUFFIX :=
NVCCFLAGS += --compiler-options -fno-strict-aliasing
CXXFLAGS += -fno-strict-aliasing
CFLAGS += -fno-strict-aliasing
endif
# architecture flag for cubin build
CUBIN_ARCH_FLAG :=
# OpenGL is used or not (if it is used, then it is necessary to include GLEW)
ifeq ($(USEGLLIB),1)
ifneq ($(DARWIN),)
OPENGLLIB := -L/System/Library/Frameworks/OpenGL.framework/Libraries
OPENGLLIB += -lGL -lGLU $(COMMONDIR)/lib/$(OSLOWER)/libGLEW.a
else
# this case for linux platforms
OPENGLLIB := -lGL -lGLU -lX11 -lXi -lXmu
# check if x86_64 flag has been set, otherwise, check HP_64 is i386/x86_64
ifeq ($(x86_64),1)
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
else
ifeq ($(i386),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
# check if i386 flag has been set, otehrwise check HP_64 is i386/x86_64
ifeq ($(i386),1)
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
ifeq ($(x86_64),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
endif
endif
ifeq ($(USEGLUT),1)
ifneq ($(DARWIN),)
OPENGLLIB += -framework GLUT
else
ifeq ($(x86_64),1)
OPENGLLIB += -lglut -L/usr/lib64
endif
ifeq ($(i386),1)
OPENGLLIB += -lglut -L/usr/lib
endif
ifeq ($(x86_64),)
ifeq ($(i386),)
OPENGLLIB += -lglut
endif
endif
endif
endif
ifeq ($(USEPARAMGL),1)
PARAMGLLIB := -lparamgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USERENDERCHECKGL),1)
RENDERCHECKGLLIB := -lrendercheckgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USENVCUVID), 1)
ifneq ($(DARWIN),)
NVCUVIDLIB := -L../../common/lib/darwin -lnvcuvid
endif
endif
# Libs
ifneq ($(DARWIN),)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib $(NVCUVIDLIB)
else
ifeq "$(strip $(HP_64))" ""
ifeq ($(x86_64),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
else
ifeq ($(i386),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
endif
endif
# If dynamically linking to CUDA and CUDART, we exclude the libraries from the LIB
ifeq ($(USECUDADYNLIB),1)
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB} -ldl -rdynamic
else
# static linking, we will statically link against CUDA and CUDART
ifeq ($(USEDRVAPI),1)
LIB += -L/usr/lib -lcuda ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
else
ifeq ($(emu),1)
LIB += -lcudartemu
else
LIB += -lcudart
endif
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
endif
endif
ifeq ($(USECUFFT),1)
ifeq ($(emu),1)
LIB += -lcufftemu
else
LIB += -lcufft
endif
endif
ifeq ($(USECUBLAS),1)
ifeq ($(emu),1)
LIB += -lcublasemu
else
LIB += -lcublas
endif
endif
ifeq ($(USECURAND),1)
LIB += -lcurand
endif
ifeq ($(USECUSPARSE),1)
LIB += -lcusparse
endif
# Lib/exe configuration
# Lib/exe configuration
# Lib/exe configuration
ifneq ($(STATIC_LIB),)
TARGETDIR := $(LIBDIR)
TARGET := $(subst .a,_$(LIB_ARCH)$(LIBSUFFIX).a,$(LIBDIR)/$(STATIC_LIB))
LINKLINE = ar rucv $(TARGET) $(OBJS)
else
ifneq ($(OMIT_CUTIL_LIB),1)
LIB += -lcutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifneq ($(OMIT_SHRUTIL_LIB),1)
LIB += -lshrutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
# Device emulation configuration
ifeq ($(emu), 1)
NVCCFLAGS += -deviceemu
CUDACCFLAGS +=
BINSUBDIR := emu$(BINSUBDIR)
# consistency, makes developing easier
CXXFLAGS += -D__DEVICE_EMULATION__
CFLAGS += -D__DEVICE_EMULATION__
endif
TARGETDIR := $(BINDIR)/$(BINSUBDIR)
TARGET := $(TARGETDIR)/$(EXECUTABLE)
LINKLINE = $(LINK) -o $(TARGET) $(OBJS) $(LIB)
endif
# check if verbose
ifeq ($(verbose), 1)
VERBOSE :=
else
VERBOSE := @
endif
# Check for input flags and set compiler flags appropriately
ifeq ($(fastmath), 1)
NVCCFLAGS += -use_fast_math
endif
ifeq ($(keep), 1)
NVCCFLAGS += -keep
NVCC_KEEP_CLEAN := *.i* *.cubin *.cu.c *.cudafe* *.fatbin.c *.ptx
endif
ifdef maxregisters
NVCCFLAGS += -maxrregcount $(maxregisters)
endif
ifeq ($(ptxas), 1)
NVCCFLAGS += --ptxas-options=-v
endif
# Add cudacc flags
NVCCFLAGS += $(CUDACCFLAGS)
# Add common flags
NVCCFLAGS += $(COMMONFLAGS)
CXXFLAGS += $(COMMONFLAGS)
CFLAGS += $(COMMONFLAGS)
ifeq ($(nvcc_warn_verbose),1)
NVCCFLAGS += $(addprefix --compiler-options ,$(CXXWARN_FLAGS))
NVCCFLAGS += --compiler-options -fno-strict-aliasing
endif
# Set up object files
OBJDIR := $(ROOTOBJDIR)/$(LIB_ARCH)/$(BINSUBDIR)
OBJS += $(patsubst %.cpp,$(OBJDIR)/%.cpp.o,$(notdir $(CCFILES)))
OBJS += $(patsubst %.c,$(OBJDIR)/%.c.o,$(notdir $(CFILES)))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu.o,$(notdir $(CUFILES)))
# Set up cubin output files
CUBINDIR := $(SRCDIR)data
CUBINS += $(patsubst %.cu,$(CUBINDIR)/%.cubin,$(notdir $(CUBINFILES)))
# Set up PTX output files
PTXDIR := $(SRCDIR)data
PTXBINS += $(patsubst %.cu,$(PTXDIR)/%.ptx,$(notdir $(PTXFILES)))
# Rules
$(OBJDIR)/%.c.o : $(SRCDIR)%.c $(C_DEPS)
$(VERBOSE)$(CC) $(CFLAGS) -o $@ -c $<
$(OBJDIR)/%.cpp.o : $(SRCDIR)%.cpp $(C_DEPS)
$(VERBOSE)$(CXX) $(CXXFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(OBJDIR)/%.cu.o : $(SRCDIR)%.cu $(CU_DEPS)
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(CUBINDIR)/%.cubin : $(SRCDIR)%.cu cubindirectory
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -cubin $<
$(PTXDIR)/%.ptx : $(SRCDIR)%.cu ptxdirectory
$(VERBOSE)$(NVCC) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -ptx $<
# The following definition is a template that gets instantiated for each SM
# version (sm_10, sm_13, etc.) stored in SMVERSIONS. It does 2 things:
# 1. It adds to OBJS a .cu_sm_XX.o for each .cu file it finds in CUFILES_sm_XX.
# 2. It generates a rule for building .cu_sm_XX.o files from the corresponding
# .cu file.
# The intended use for this is to allow Makefiles that use common.mk to compile
# files to different Compute Capability targets (aka SM arch version). To do
# so, in the Makefile, list files for each SM arch separately, like so:
# This will be used over the default rule abov
# CUFILES_sm_10 := mycudakernel_sm10.cu app.cu
# CUFILES_sm_12 := anothercudakernel_sm12.cu
define SMVERSION_template
#OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_$(1))))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_sm_$(1))))
$(OBJDIR)/%.cu_$(1).o : $(SRCDIR)%.cu $(CU_DEPS)
# $(VERBOSE)$(NVCC) -o $$@ -c $$< $(NVCCFLAGS) $(1)
$(VERBOSE)$(NVCC) -gencode=arch=compute_$(1),code=\"sm_$(1),compute_$(1)\" $(GENCODE_SM20) $(GENCODE_SM30) -o $$@ -c $$< $(NVCCFLAGS)
endef
# This line invokes the above template for each arch version stored in
# SM_VERSIONS. The call funtion invokes the template, and the eval
# function interprets it as make commands.
$(foreach smver,$(SM_VERSIONS),$(eval $(call SMVERSION_template,$(smver))))
$(TARGET): makedirectories $(OBJS) $(CUBINS) $(PTXBINS) Makefile
$(VERBOSE)$(LINKLINE)
cubindirectory:
$(VERBOSE)mkdir -p $(CUBINDIR)
ptxdirectory:
$(VERBOSE)mkdir -p $(PTXDIR)
makedirectories:
$(VERBOSE)mkdir -p $(LIBDIR)
$(VERBOSE)mkdir -p $(OBJDIR)
$(VERBOSE)mkdir -p $(TARGETDIR)
tidy :
$(VERBOSE)find . | egrep "#" | xargs rm -f
$(VERBOSE)find . | egrep "\~" | xargs rm -f
clean : tidy
$(VERBOSE)rm -f *.stub.c *.gpu *.cu.cpp *.i *.ii
$(VERBOSE)rm -f *.cubin *.ptx *.fatbin.c *.hash
$(VERBOSE)rm -f *.cudafe1.c *.cudafe2.c *.cudafe1.cpp *.cudafe2.cpp
$(VERBOSE)rm -f $(OBJS)
$(VERBOSE)rm -f $(CUBINS)
$(VERBOSE)rm -f $(PTXBINS)
$(VERBOSE)rm -f $(TARGET)
$(VERBOSE)rm -f $(NVCC_KEEP_CLEAN)
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.ppm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.pgm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bin
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bmp
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.txt
$(VERBOSE)rm -f $(CUBINDIR)/*.cubin $(PTXDIR)/*.ptx
$(VERBOSE)rm -rf $(ROOTOBJDIR)
$(VERBOSE)rm -rf $(LIBDIR)
$(VERBOSE)rm -rf $(OBJDIR)
$(VERBOSE)rm -rf $(TARGETDIR)
clobber : clean
$(VERBOSE)rm -rf $(COMMONDIR)/lib/*.a
$(VERBOSE)rm -rf $(SHAREDDIR)/lib/*.a
$(VERBOSE)rm -rf $(COMMONDIR)/obj
$(VERBOSE)rm -rf $(SHAREDDIR)/obj
The output of echo $LD_LIBRARY_PATH is blank.
I have checked for libcuda and can find it:
# ls /usr/lib | grep libcuda
libcuda.so.1
libcuda.so.304.32
Is there something obvious I need to do to get these to compile?
Thanks again.

Has anyone got the B500 to work with Ubuntu? (nvidia driver problems)

In two weeks, I have been completely unable to get the nvidia driver working with the B500 on Linux. No matter what I try to do, the X server doesn't start, and my /var/log/Xorg.0.log file ends with "fatal server error: no screens found." I have tried feeding a custom modeline to xorg.conf, explicitly calling an EDID file which I extracted from the Windows installation, using the upstream nvidia driver installer, using the official repository driver, and probably a bunch of other stuff that I'm not recalling right now.
Versions I've tried this on:
Kubuntu 10.04, 32- and 64-bit
Ubuntu 10.04, 32-bit
Kubuntu 9.10, 32-and 64-bit
I am stumped. Has anyone successfully gotten this to work?
best,
-p.
Solved!
Go to Solution.

Solved with the kind assistance of paulricardomc on the Ubuntu Forums: http://ubuntuforums.org/showthread.php?t=1477507
Short version of the fix:
1. Extract the edid from the Windows partition using softMCCS, saving as edid.bin
2. Save the edid.bin file in /etc/X11 (or wherever you like)
3. Include the following in the device section of your xorg.conf:
"Option" "ConnectedMonitor" "DFP-0"
"Option" "CustomEDID" "DFP-0:/etc/X11/edid.bin"
Fire up X and you're good to go.

ESATA card w/ drive connected causes Windows 7 bootup to hang

I installed the NewerTech MAXPower eSATA 6G PCIe 2.0 card in slot 2 (PCI Express 2.0) of my Mac Pro (January 2008). My Mac Pro is configured with Mac OS X 10.6.x. It also has 64-bit Windows 7 installed via Boot Camp.
The NewerTech eSATA card works fine with Mac OS X. However, if an external drive connected to the eSATA card is powered ON at the time I natively boot-up to Windows 7, booting up hangs with the following message:
Marvell 88SE91xx Adapter - BIOS Version 1.0.0.1003.
Initializing...
If the external drive is OFF at the time I boot-up Windows 7, boot-up doesn't hang. I get the following message during bootup:
Disk Information:
No hard disk detected!
Then, my Mac Pro continues to boot up into Windows 7; it does not hang. However, I can't use the drive. If I turn on the drive (a LaCie D2 Quadra 1 TB hard drive) after logging into Windows 7, it is not detected by Windows 7. This is different behavior than with Mac OS X. If my LaCie drive was off when I boot-up into Mac OS X, and I turn on the LaCie drive after logging into Mac OS X, the drive is detected properly and shows up in Finder. I also have the OWC Mercury Extreme Pro Qx2. If I turn it OFF prior to booting into Windows 7 (to prevent a hang), and then turn it back ON after booting into Windows 7, then Windows 7 recognizes the Qx2.
So, does anyone have any suggestions on how to bootup Windows 7 natively while an external drive is connected? I reported the problem to OWC and they said that their "engineers are working on it", but it's been weeks, and it seems nothing is being done. BTW, I only tried slot 2 on my Mac. Wonder if it will help to try another slot.
Thanks.

I haven't had any problems using the card other than Windows 7 bootup hanging if an external drive is connected to the card. Do you think it's a good chance that it's an issue with the external drive having the USB/eSATA/firewire interfaces, and not the card itself? Unfortunately, all my external drives (all of which hang during Windows 7 bootup via bootcamp) have the USB/eSATA/firewire interfaces.
I did some write tesing (large video files) using the OWC Mercury Elite-AL Pro Qx2 (4 drives in a RAID 5 config), which has a USB/eSATA/firewire interface. Using the eSATA interface, I was getting 202 MB/sec. Using Firewire 800, I was getting 65 MB/sec. So the eSATA was 202/65 = 3.1 times faster than Firewire 800. So, eSATA is certainly desirable to use. Not sure how much better I'd get with an enclosure that has only eSATA, and whether or not I'd get rid of the Windows 7 "hanging during bootup" bug.... Not an easy test to do given how much these external enclosures cost.
If anyone has any suggestions on alternate eSATA cards that work with Mac OS X SL, Windows 7 (natively via boot camp and via Parallels), let me know. Driverless would be great. I've done a lot of searching around for an ideal eSATA card, but seems that each one has different pros/cons.
thanks.

[SOLVED] nVidia driver 195.36.08 causes KDE4.4 to crash after logging?

Hi to all Archers
I noticed the new nVidia driver (195.36.08) on pacman's yesterday updates, I didn't update it immediately and preferred to wait until I was available to fiddle with it in case things went wrong. Apparently, that was the case
Here's what happens if I install the new driver:
KDM starts as usual, I login in, I see KDE loading progress and before it finishes, boom it crashes and returns to KDM login once again.
I tried reinstalling KDE, Xorg and read nVidia wiki to see if there is any hints. I tried once again with a new stock xorg.conf, and removed .nvidia-settings-rc and even disabled KDE compositing but all this couldn't help getting KDE up and running.
However, when I reinstall the previous version (190.53) everything is back to normal.
So what I want to know is am I the only one who gets this problem or there're others here having the same issue?
Because the first time I installed the nVidia driver (almost 3 months now) I used their own installer then used Arch packages afterwards, I suspect that perhaps their installer messed things up !?
For now the solution is to stick to the previous version.
I'm using Arch Linux 32bit and my GC is an nVidia 7300GT.
Regards,
Med
Last edited by stuntgp2000 (2010-03-08 00:17:10)

zero-giulio wrote:
I want to install the 190.53 version of nvidia driver, because it's the correct driver version for my video card, according to nvidia site (see http://www.nvidia.com/object/linux_disp … 0.53.html).
Also, in my prevoius arch system I installed that version and everything worked well. I don't want to try the newerr version. It doesn't matter if 190.53 are not the latest driver available. I'm self confident with the 190.53 version.
How can I install them? The problem is that pacman suggest me only the latest version :-(
You'll find them here http://schlunix.org/archlinux/extra/os/ after choose your system architecture.
if you want to know more about downgrading for more than a few packages read this guide http://wiki.archlinux.org/index.php/Dow … g_Packages
Assuming you have a recent nvidia graphic card and using a i686 system you should download these:
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
Good luck,

Just Cause 2 nvidia driver crash MSI GTX 580 OC SLI (video)

I found a bug that crashes the nvidia drivers when running the factory overclocked msi gtx 580's in SLI. I downclocked them to reference 772,1544,2004 and found the game runs perfectly for long periods without crashing.

Quote from: pacnow on 17-February-11, 07:23:31
I tested the first card I purchased the non stickered one, and running at factory overclock it crashed the driver about 20 minutes of gameplay.
What I did differently this time was I removed the Stickered card from the PCIE slot.
Wow amazing I didn't think it could be a single cards fault. I'll continue testing the stickered one too. What I did find strange was this non stickered card core values show 822 in MSI Afterburner and 823 in GPUZ.
What you mean by "stickered" and "non stickered" card?
Quote
What I did find strange was this non stickered card core values show 822 in MSI Afterburner and 823 in GPUZ.
that's suppose to be.
When you locate which one of your card is crashing.
Use/install this[latest] AB version 2.1.7:
http://event.msi.com/vga/afterburner/downloads/MSIAfterburnerSetup210Beta7.zip
then go to settings, and unlock voltage monitor and voltage control.
then restart the AB, and click on reset
then see and tell what's the vcore shown for it

CS5.0.2 causing graphics driver crash

Updated to Premiere 5.0.2 and Media Encoder 5.0.1 - when I export (inside Premiere as well as sending to Media Encoder, Premiere/Media Encoder freezes up and I get a Windows message to say that the Graphics driver has crashed and it has successfully recovered. Reverted back to Premiere 5.0.1 and can successfully export without issues. Anyone experiencing similar problems? I have latest WHQL release Nvidia driver which has not given any hassles.

Does your error message look like this?
http://dl.dropbox.com/u/1426292/share/PPRO_5.02_GPU_Crash_01.JPG
I have the same graphics card (GTS 250) and I have had some problem as well.
Here is a thread that I started when I found issue related to the GPU and large image files: http://forums.adobe.com/thread/673072?tstart=0
Here is another thread that I have been contributing to...the person that started the thread has the same graphic card as well: http://forums.adobe.com/message/3102758
I had mixed results from the update to 5.02, but the cons out weigh the pros when the hack is considered. So, I have since decided to wait until I can afford a supported card...hoping that will help. Below is what I posted on the last forum that I provided the link to. It illustrates my results with the update and different drivers. I would love to figure out how to make the GTS 250 reliable, please post any new findings that might be helpful. Thank you.
Quote:
I have found problems with the Nvidia driver 258.? on my machine. While I did gain some marginal ability to work with larger images using the GPU, I started to get frequent OpenGL error messages and crashing in After Effects with the updated driver, so I have reverted back to version 197.? and all seems to be well again.
It makes me worry using the "hack" on video jobs. The hack is fun to play with to see how well the playback can be using the GPU, but I don't want to work on time sensitive material always wondering if something I add to the timeline will cause it to crash, or worse, corrupt a project file. For me, I don't think the benefits out weigh the downside of the "hack".
I have considered using the "hack" on video only projects, but I don't know if the problems will eventually turn up on long projects or not. Most of my most recent projects have been fairly short. I do realize that my large images that have causing the crashes are huge (approx. 4300 x 2800), but in software only mode they are not a problem at all...really smooth. If I had more time, I would fine the maximum image size that I could work with without causing my system to crash, but I don't have that much time to play with it. It seems that the smaller the image, the longer it takes to make it crash, but eventually, I can always make it crash. So, I wonder if any image size could be a problem, but it just takes longer for the crash to occur?
I really wish that someone with a supported card would try some large images and run it through some testing. Once I get a supported card, my large images will be my first test. If it crashes with a supported card, I'm not going to be real happy. Some have suggested the problem may be the amount of RAM on my GTS 250, but my card has 1GB, which is about how much many of the supported cards have.
I am wondering if the GTS 250 just doesn't have enough muscle to work with the images? Anyone with a supported card want to give it a go? The time would be greatly appreciated.

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!

Is it true that current version of Mozilla Firefox including its updates can currently cause Windows 7 and/or Windows XP to crash?

I was advised in the first week of September 2013 by our IT contractor, that the current version of Mozilla FireFox (and its updates) is causing computers with Windows 7 to crash? (NB: specifically, we have Windows 7 Home Premium Service Pack 1, 64bit). Is this still the case, and if not, do we need to upgrade to a newer version of Win7 (if one exists). Also, is there currently a problem with using Mozilla Firefox on a computer with Windows XP Home Edition, version 2002, service pack 3? NB: We have a server and our computers are on a network.
Thanks heaps, as would really like to change back to FireFox when possible.

That shouldn't be the case but most likely what I can think of is the graphics driver conflicting with Firefox. We can troubleshoot this issue if you'd like to.

W510 problems with Nvidia driver recovery under Windows 7 (64 bit)?

Lenovo W510, Nvidia Qudardo FX 880M video, FHD:
What I'm seeing on occasion is a Windows 7 (64-bit) recovery, screen blanks out, goes 2-3 seconds, then recovers, things go back to normal, but a message displays saying that an error was detected in the video driver, and it has recovered. The new Firefox (4.0.1) seems to be one of the things that may be a contribution, hard to tell. Per System Update at least, I'm current on the Lenovo downloads. SIW shows the driver level as 8.17.12.5738 (2010-06-27). Nvidia web-site shows their current driver level on the wen-site as 270.61 (2011-04-18), which is a considerably newer date at least. So two questions:
Has anyone else seen Driver/Recovery issues on Win 7 (64)
Has anyone directly run the Nvidia video drivers and had them run OK?
Seems like it would be nice for Lenovo to update their drivers, if indeed this is a driver issue, they appear back-level.

I used to have this problem with my W510 running Windows 7 Enterprise 64-bit, especially Firefox 4 crashing the Nvidia display driver almost constantly. I googled and found that this is a known problem between older Nvidia driver and Firefox 4. Later on I downloaded the latest version of Nvidia driver from Lenovo website (it was not posted on the System Update server yet but was available on the regular download site). I clean-installed it (i.e., removing all files and settings created by the old driver) and I haven't experienced the problem since then.
Twitter @thitiv | Work | ThinkPad W520 (4270-CTO) Core i7-2960XM 2.7/3.7 GHz | 16GB Kingston HyperX PnP DDR3-1866
2 x 256GB Crucial M4 & C300 SSDs | Intel Centrino Ultimate-N 6300 | Ericsson F5521gw WWAN | Ultrabay Blu-ray Burner
NVIDIA Quadro 2000M | 15.6" FHD 1920x1080 | ThinkPad Battery 55++ (9-cell) & Battery 27++ (9-cell slice)

NVIDIA driver 6md647ww does not install on W701 with Windows 7 64 Bit

Hello,
I have downloaded the nvidia driver 6md647ww (311.00), 64 bit version, and can't install on a Windows 7 64-bit system. It says "no compatible device found". The strange thing is, although the decompression routine and the window asking to start installation both say that they are the 64 bit version, the text besides the check mark "install the driver now" says it will install the 32 bit version (after decompressing the window says 64 bit in the upper part, but 32 bit in the lower part).
So I guess there is an error in the installation routine which erronously wants to install the 32 bit version although it is DEFINITELY the 64 bit version I have downloaded. Also, I downloaded for testing the 32 bit version of the driver (5md647ww), and if I try to install that, I get exactly the same error as with the 64 bit version.
Could someone please look into the 6md647ww, there is something wrong with it. Also, I can install 6md640ww and 6md643ww without any problems and switch between these two versions without any error - the 6md647ww issue is definitely NOT a problem of my OS configuration.
I have a sporadic heavy crash issue with 6md643ww and need to upgrade badly.
Please help. Best regards, Michael
System: Lenovo W701, 16 GB Ram, Windows 7 64 Bit, NVIDIA Quadro FX 3800M

In the meanwhile Rev 04 of the driver was published. This version is binary different to Rev 03 and - surprise - it now says correctly after unpacking it will install the 64-bit version. But after that same problem as before, "no compatible device found".
I did some searching into the files of 6md647ww. I guess the file Display.Driver\NVLT.inf contains a list of compatible devices - in this file the sections labelled NVIDIA_SetA_Devices.NTamd64.* list a lot of device-ids, for example PCI\VEN_10DE&DEV_0A3C&SUBSYS_214517AA and many more. The device id of the graphics card for a system can be found in the hardware/device manager of windows, I obtained that for my card and this id doesn't show anywhere in NVLT.inf. So if my guess is correct, it is no wonder the installer says "no compatible device" since the device id of my card is not listed in NVLT.inf.
Please note again that all previous versions of lenovo drivers for my NVIDIA Quadro FX 3800M did and do install without absolutely any problem!
This is strange, readme of the current driver version definitely says NVIDIA Quadro FX 3800M is supported by this driver, but the driver doesn't seem to contain the device id for it. Looks almost like the wrong driver was used / bundled into 6md647ww.
And again the question to the board / administrators if lenovo technical support is reading here and is there another contact at lenovo where I could direct my problem to? I am still having the sporadic heavy crash issue which is very dangerous since it can happen any time if displaying whatever graphics in whatever software and which therefore has a high risk of data loss. Also, installing the plain NVIDIA driver directly in the current version still has the problem of flickering and color errors, so this isn't a solution either.
Best regards, Michael

Windows 8 bootup crash, cause NVIDIA Driver.

Similar Messages

Maybe you are looking for