Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD & Driver stop responding

03 Apr 2011   #1
Absurde

Windows 7 Ultimate SP1 x64
 
 
BSOD & Driver stop responding

Hello 1st time here, there is my dump file & html, any help will be appricieted:
my specs:
Mobo: Asus M4A785T-M
CPU: AMD Athlon II 240 2.8GHz
RAM: 2x2GB A-Data DDR3 1333MHz
GPU: Palit GTX 460 768MB
HDD: 2x WD 640GB & 1TB
PSU: Xigmatek 550W...
Don't use 3D...


My System SpecsSystem Spec
.
03 Apr 2011   #2
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Your Nvidia driver was the cause

Uninstall the driver, then use driver sweeper to remove leftover Nvidia display driver files
http://phyxion.net/Driver-Sweeper/Dr...Version-2-9-0/
Then install the latest drivers
http://www.nvidia.com/object/win7-wi...ql-driver.html

ASACPI.sys the 2005 version is a huge cause of BSODs

information   Information
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "
ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Code:
ASACPI.sys        fffff880`11df6000    fffff880`11dfe000    0x00008000    0x42476c4c    28/03/2005 06:30:36
Update any Razer driver, the one you use is seriously outdated, remove that device if no Windows7 certified drivers are found
http://www.razersupport.com/index.ph...nloads&_a=view
Code:
DB3G.sys        fffff880`038de000    fffff880`038e3280    0x00005280    0x436ef527    07/11/2005 10:33:11
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88769117750, 2, 1, fffff88011220d4e}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+121d4e )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88769117750, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88011220d4e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecd0e8
 fffff88769117750 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+121d4e
fffff880`11220d4e 4c891cd0        mov     qword ptr [rax+rdx*8],r11

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88004f6e370 -- (.trap 0xfffff88004f6e370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009b22000 rbx=0000000000000000 rcx=fffffa800455d668
rdx=00000000ebebeaea rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011220d4e rsp=fffff88004f6e500 rbp=0000000000000000
 r8=0000380f70f00000  r9=000000000000000f r10=0000000000000000
r11=0000380f70f00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x121d4e:
fffff880`11220d4e 4c891cd0        mov     qword ptr [rax+rdx*8],r11 ds:e9d0:fffff887`69117750=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c9bbe9 to fffff80002c9c640

STACK_TEXT:  
fffff880`04f6e228 fffff800`02c9bbe9 : 00000000`0000000a fffff887`69117750 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`04f6e230 fffff800`02c9a860 : 00000000`08000600 fffffa80`03b7e9d0 00000000`00000000 0000000f`70f00038 : nt!KiBugCheckDispatch+0x69
fffff880`04f6e370 fffff880`11220d4e : fffffa80`03b7eb48 fffffa80`040eb010 fffffa80`08000620 fffffa80`00007a88 : nt!KiPageFault+0x260
fffff880`04f6e500 fffffa80`03b7eb48 : fffffa80`040eb010 fffffa80`08000620 fffffa80`00007a88 fffffa80`1000f010 : nvlddmkm+0x121d4e
fffff880`04f6e508 fffffa80`040eb010 : fffffa80`08000620 fffffa80`00007a88 fffffa80`1000f010 fffff880`11220dca : 0xfffffa80`03b7eb48
fffff880`04f6e510 fffffa80`08000620 : fffffa80`00007a88 fffffa80`1000f010 fffff880`11220dca fffffa80`00000000 : 0xfffffa80`040eb010
fffff880`04f6e518 fffffa80`00007a88 : fffffa80`1000f010 fffff880`11220dca fffffa80`00000000 00000000`00000000 : 0xfffffa80`08000620
fffff880`04f6e520 fffffa80`1000f010 : fffff880`11220dca fffffa80`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`00007a88
fffff880`04f6e528 fffff880`11220dca : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`04b469e0 : 0xfffffa80`1000f010
fffff880`04f6e530 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`04b469e0 fffffa80`03b75000 : nvlddmkm+0x121dca
fffff880`04f6e538 00000000`00000000 : 00000000`00000000 fffffa80`04b469e0 fffffa80`03b75000 fffff880`1122196c : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+121d4e
fffff880`11220d4e 4c891cd0        mov     qword ptr [rax+rdx*8],r11

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+121d4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8d8d72

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+121d4e

BUCKET_ID:  X64_0xD1_nvlddmkm+121d4e

Followup: MachineOwner
---------
If BSODs still occur you should test your hardware with OCCT
http://downloads.guru3d.com/OCCT-(Ov...load-1880.html
My System SpecsSystem Spec
03 Apr 2011   #3
Absurde

Windows 7 Ultimate SP1 x64
 
 

I'm using v270.51 of nVidia drivers...
My System SpecsSystem Spec
.

03 Apr 2011   #4
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by Absurde View Post
I'm using v270.51 of nVidia drivers...
Use stable releases, not beta versions
My System SpecsSystem Spec
03 Apr 2011   #5
Absurde

Windows 7 Ultimate SP1 x64
 
 

Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by Absurde View Post
I'm using v270.51 of nVidia drivers...
Use stable releases, not beta versions
Same thing happens with 266.58...
My System SpecsSystem Spec
03 Apr 2011   #6
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by Absurde View Post
Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by Absurde View Post
I'm using v270.51 of nVidia drivers...
Use stable releases, not beta versions
Same thing happens with 266.58...
You should use driver sweeper before installing the Nvidia driver
Did you update ASACPI.sys?
Run the GPU test of OCCT

Remove that Razer software until you sort out the issue
My System SpecsSystem Spec
03 Apr 2011   #7
Absurde

Windows 7 Ultimate SP1 x64
 
 

Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by Absurde View Post
Quote   Quote: Originally Posted by yowanvista View Post
Use stable releases, not beta versions
Same thing happens with 266.58...
You should use driver sweeper before installing the Nvidia driver
Did you update ASACPI.sys?
Run the GPU test of OCCT

Remove that Razer software until you sort out the issue
I'm always using Driver Sweeper...
how can update asacpi.sys?
And the razer is the latest they are old but latest for x64 win7 diamondback 3g....
And now I will start OCCT test ...
My System SpecsSystem Spec
03 Apr 2011   #8
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by Absurde View Post
Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by Absurde View Post

Same thing happens with 266.58...
You should use driver sweeper before installing the Nvidia driver
Did you update ASACPI.sys?
Run the GPU test of OCCT

Remove that Razer software until you sort out the issue
I'm always using Driver Sweeper...
how can update asacpi.sys?
And the razer is the latest they are old but latest for x64 win7 diamondback 3g....
And now I will start OCCT test ...
See post #2 for asacpi.sys
My System SpecsSystem Spec
03 Apr 2011   #9
Absurde

Windows 7 Ultimate SP1 x64
 
 

I updated asacpi.sys to 2009 version. OCCT tell's me there is no errors... but the problem is still there... I will buy a new PSU next week smoething above 600W and more then 30A for the 12v rail...
My System SpecsSystem Spec
03 Apr 2011   #10
Absurde

Windows 7 Ultimate SP1 x64
 
 

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1026

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800665B4E0
BCP2: FFFFF880111C4354
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040311-33493-01.dmp
C:\Users\Absurde\AppData\Local\Temp\WER-51776-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Тhat is showing me... I tried 260.99WHQL 266.58WHQL 270.51 beta 266.77 from palit web site 263.14 266.35 beta... Everything... The only solution is to replace my nvidia with ADM 6000 card or my AMD cpu with Intel.....
My System SpecsSystem Spec
Reply

 BSOD & Driver stop responding




Thread Tools




Similar help and support threads
Thread Forum
Display driver stop responding and recovered Win7, what do?
So I seem to have been having a problem when playing 2 certain games. One is called Heroes of Newerth (HON), and the other Runescape. At random peak times when my memory usage increases a lot, my screen flickers off and flickers back on randomly. It stays on for quite awhile then, and may just...
Graphic Cards
BSOD and display driver stopped responding and has recovered
Hello, I'm CrazyKilla Recently i got black ops 2, it started crashing without giving me a reason, and i finally saw the "Display driver stopped respoding and has recovered" at the bottom right of my screen, i found out that disabling SLI fixes this, i completed the game... Now i installed...
Graphic Cards
Nvidia Driver Crashed/Not Responding, BSOD
Hi guys, the issue that I am facing is basically the screen going black at random times, before showing on the taskbar "Nvidia driver not responding", and this would happen a few more times before the system will crash with a BSOD about some nvidia driver file. This issue seem to surface after...
BSOD Help and Support
BSOD/GraphicCard Flickering/Stop responding
Windows 7 is. . . - x64 Ultimate - the original installed OS on the system? Nope. Self Built - an OEM or full retail version? I got it from college... - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? a year .... ...
BSOD Help and Support
display driver stop responding???
hi, i got problem.. sometimes appear message at bottom right "display driver stop responding, n windows can repair it" i noticed when i'm running DX10-dx11 applications i truly believe when run sisoft sandra benchmark,
Drivers
Driver not responding + bsod + failure to reboot
I purchased this computer from CyberPower PC, it worked fine the day I got it. On the second day I started getting some weird artifacting that progressively got worse for about 20 minutes followed by a Display Driver Not Responding Prompt, and concluded with a full lockup and a bsod. I was playing...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:55.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App