Solution
Maybe we should start with AVG.
DUMP:
DUMP:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 0, fffff880044101d9}
Unable to load image \SystemRoot\system32\DRIVERS\avgtdia.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for...
Trouble
Noob Whisperer
- Joined
- Nov 30, 2009
- Messages
- 13,722
Got to admit, I'm a little stumped. This one is pointing at your Nvidia display driver software
I suppose it could be a corrupt driver and normally I would suggest getting the latest driver available (download again), from Nvidia.
And then use DriverSweeper in safe mode (very carefully) to remove it then perform a clean install just to be sure.
I did notice that your BIOS looks like it's dated.... 01/22/2008. I believe there is a more current version released 8/12/2011. Take a look here Link Removed you may want to consider an update.
Code:
.....
Unable to load image [U][B]nvlddmkm.sys[/B][/U], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B][U]nvlddmkm.sys[/U][/B]
*** ERROR: Module load completed but symbols could not be loaded for [B][U]nvlddmkm.sys[/U][/B]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800f469ec0, fffff880031f6858, fffff880031f60b0}
[B][U]Probably caused by : nvlddmkm.sys[/U][/B] ( nvlddmkm+207ec0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[U][B]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.[/B][/U] 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: fffff8800f469ec0, The address that the exception occurred at
Arg3: fffff880031f6858, Exception Record Address
Arg4: fffff880031f60b0, 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+207ec0
fffff880`0f469ec0 0000 add byte ptr [rax],al
EXCEPTION_RECORD: fffff880031f6858 -- (.exr 0xfffff880031f6858)
[U][B]ExceptionAddress: fffff8800f469ec0 (nvlddmkm+0x0000000000207ec0)[/B][/U]
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: fffff880031f60b0 -- (.cxr 0xfffff880031f60b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f469ec0 rsp=fffff880031f6a98 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=fffffa800701f680
r11=0000017664370010 r12=fffffa80087ce000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x207ec0:
fffff880`0f469ec0 0000 add byte ptr [rax],al 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 fffff800038b1100
0000000000000000
FOLLOWUP_IP:
nvlddmkm+207ec0
fffff880`0f469ec0 0000 add byte ptr [rax],al
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800f46a6cd to fffff8800f469ec0
STACK_TEXT:
fffff880`031f6a98 fffff880`0f46a6cd : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0f4477a3 : nvlddmkm+0x207ec0
fffff880`031f6aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`0f4477a3 00000000`00000000 : nvlddmkm+0x2086cd
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+207ec0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ecd9f33
STACK_COMMAND: .cxr 0xfffff880031f60b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+207ec0
BUCKET_ID: X64_0x7E_nvlddmkm+207ec0
Followup: MachineOwner
And then use DriverSweeper in safe mode (very carefully) to remove it then perform a clean install just to be sure.
I did notice that your BIOS looks like it's dated.... 01/22/2008. I believe there is a more current version released 8/12/2011. Take a look here Link Removed you may want to consider an update.
Trouble
Noob Whisperer
- Joined
- Nov 30, 2009
- Messages
- 13,722
Actually I was reading this page
Link Removed
MalwareBytes
SuperAntiSpyware
Once installed and updated, reboot into safemode and run a full scan using both simultaneously. ( just out of curiosity)
Good luck and keep us posted
Regards
Randy
Link Removed
While you're awaiting another Blue Screen (not), would you download the free versions, install and update bothDriver Version: P33
Release Date: 8/12/2011
Driver File: Link Removed
MalwareBytes
SuperAntiSpyware
Once installed and updated, reboot into safemode and run a full scan using both simultaneously. ( just out of curiosity)
Good luck and keep us posted
Regards
Randy
- Thread Author
-
- #26
Ha, that's weird. It's the same one I downloaded. On the search it's 09 but when you click on it it's '11. My pc info says 09 tho. I'll run those scans in a bit butttttt....after updating, my pc freezes on safe mode. On cnp something. I'm trying to fix that so I can uninstall nvidia display drivers in safe mode. Googling. XD
Similar threads
- Solved
- Replies
- 19
- Views
- 3K
- Solved
Windows 7
BSOD error: 0x0000003b. Help needed
- Replies
- 6
- Views
- 3K
- Replies
- 4
- Views
- 2K
- Solved
- Replies
- 15
- Views
- 4K
- Solved
Windows 7
help I get a Stop: 0x0000003b BSOD
- Replies
- 1
- Views
- 2K