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: Random BSOD's

12 Jan 2011   #1
Twister1089

Windows 7 Premuim 64bit
 
 
Random BSOD's

I have recently had a lot of random BSOD's, actually while typing this post it triggered a chain of 4 or 5.... Each one always gives a different error message, I have run memtest in the past with 8 passes showing full success, could someone please help me?


My System SpecsSystem Spec
12 Jan 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Twister1089 View Post
I have recently had a lot of random BSOD's, actually while typing this post it triggered a chain of 4 or 5.... Each one always gives a different error message, I have run memtest in the past with 8 passes showing full success, could someone please help me?

Your video driver and asacpi.sys

1-asacpi.sys

ASACPI.sys Sun Mar 27 22:30:36 2005
Quote:
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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).
2- your video driver remove and re-install using these directions

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\122810-13868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Tue Dec 28 22:05:25.513 2010 (GMT-5)
System Uptime: 0 days 0:00:21.074
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880047964d9, fffff880043bda78, fffff880043bd2e0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1874d9 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880047964d9, The address that the exception occurred at
Arg3: fffff880043bda78, Exception Record Address
Arg4: fffff880043bd2e0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+1874d9
fffff880`047964d9 48832000        and     qword ptr [rax],0

EXCEPTION_RECORD:  fffff880043bda78 -- (.exr 0xfffff880043bda78)
ExceptionAddress: fffff880047964d9 (nvlddmkm+0x00000000001874d9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT:  fffff880043bd2e0 -- (.cxr 0xfffff880043bd2e0)
rax=0000000000000000 rbx=fffffa8005973000 rcx=fffffa80054f6910
rdx=00000000dff67000 rsi=0000000000000000 rdi=00000000dff67000
rip=fffff880047964d9 rsp=fffff880043bdcb0 rbp=fffffa8005346730
 r8=fffff880043bdd00  r9=fffff880043bdcf0 r10=0000000000000007
r11=fffffa80053bd000 r12=fffffa8006452d60 r13=fffff880043bdfa0
r14=0000000000000001 r15=00000000c1d00570
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x1874d9:
fffff880`047964d9 48832000        and     qword ptr [rax],0 ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
 0000000000000000 

FOLLOWUP_IP: 
nvlddmkm+1874d9
fffff880`047964d9 48832000        and     qword ptr [rax],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa8005346730 to fffff880047964d9

STACK_TEXT:  
fffff880`043bdcb0 fffffa80`05346730 : 00000000`00000000 fffffa80`06452d60 fffffa80`05973000 fffffa80`05973000 : nvlddmkm+0x1874d9
fffff880`043bdcb8 00000000`00000000 : fffffa80`06452d60 fffffa80`05973000 fffffa80`05973000 fffff880`04adb053 : 0xfffffa80`05346730


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+1874d9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c5f8066

STACK_COMMAND:  .cxr 0xfffff880043bd2e0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+1874d9

BUCKET_ID:  X64_0x7E_nvlddmkm+1874d9

Followup: MachineOwner
---------
My System SpecsSystem Spec
13 Jan 2011   #3
Twister1089

Windows 7 Premuim 64bit
 
 
quick question about hgraphics driver

When I run Guru3D, I also see I have NVIDIA audio drivers and 3D Drivers (possibly provided by the same card) because it has an HDMI out, I have an NVIDIA GeForce GT 430, do I only need to wipe out what appears under graphics? Thank you for all your help thus far (I updated my ASUS driver like you recommended.
My System SpecsSystem Spec
Reply

 Random BSOD's




Thread Tools




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 12:07 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App