Help identified BSOD

Hi im New here..
i was searching google and found this site.. i think you folks could help me solved the BSOD im getting..
Recently i did Reformat on my OS and had a little run down with my Formating (having trouble installing) my SSD and in the end i Solved it. but after i did all the installing drivers and updates i would get the blue screen.. especially when i log back on from Screen Saver or when i run MSE.. those the 2 time i remember.
i uploaded Dump files maybe you folks could help me with this problem.. TIA and appreciate it. :)

-Matt

idk if this info helps.. but, when im playing CSS i notice its Choppy and it didnt do that before.

k1msta said:

Hi im New here..
i was searching google and found this site.. i think you folks could help me solved the BSOD im getting..
Recently i did Reformat on my OS and had a little run down with my Formating (having trouble installing) my SSD and in the end i Solved it. but after i did all the installing drivers and updates i would get the blue screen.. especially when i log back on from Screen Saver or when i run MSE.. those the 2 time i remember.
i uploaded Dump files maybe you folks could help me with this problem.. TIA and appreciate it. :)

-Matt

Love to help but no DMP files included in upload try this method.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

ty you for your fast response and appreciate helping me
i followed your instruction here's the file as requested

k1msta said:

ty you for your fast response and appreciate helping me
i followed your instruction here's the file as requested

Nope sorry;

The file uploaded is an event viewer log. I/we are looking for files that end with .DMP

if you cant find them you may not be creating them

check to enable DMPs in my post

zigzag3143 said:

k1msta said:

ty you for your fast response and appreciate helping me
i followed your instruction here's the file as requested

Nope sorry;

The file uploaded is an event viewer log. I/we are looking for files that end with .DMP

if you cant find them you may not be creating them

check to enable DMPs in my post

ok i think i got it.. please try again ty

k1msta said:

zigzag3143 said:

k1msta said:

ty you for your fast response and appreciate helping me
i followed your instruction here's the file as requested

Nope sorry;

The file uploaded is an event viewer log. I/we are looking for files that end with .DMP

if you cant find them you may not be creating them

check to enable DMPs in my post

ok i think i got it.. please try again ty

You got it. These were both Related to nvhda64v.sys HDMI Audio Driver from NVIDIA Corporation.

I would re-install the driver with the newest version available.

Just for some added info (and it doesnt take long) you can run a system file check to verify and repair your OS files.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

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\060911-9297-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03649650
Debug session time: Fri Jun 10 02:42:52.470 2011 (GMT-4)
System Uptime: 0 days 0:56:18.282
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CE, {fffff88005b02429, 8, fffff88005b02429, 0}

Probably caused by : nvhda64v.sys ( nvhda64v+b429 )

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

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

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen.
Arguments:
Arg1: fffff88005b02429, memory referenced
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation
Arg3: fffff88005b02429, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, Mm internal code.

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b3100
 fffff88005b02429 

FAULTING_IP: 
nvhda64v+b429
fffff880`05b02429 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005deb750 -- (.trap 0xfffff88005deb750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005b02429 rsp=fffff88005deb8e0 rbp=00000000000000f4
 r8=0000000000000000  r9=000000000032d49e r10=000000000000001d
r11=fffffa800b1dec68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
<Unloaded_nvhda64v.sys>+0xb429:
fffff880`05b02429 ??              ???
Resetting default scope

IP_MODULE_UNLOADED: 
nvhda64v+b429
fffff880`05b02429 ??              ???

LAST_CONTROL_TRANSFER:  from fffff8000342fa0c to fffff80003483d00

STACK_TEXT:  
fffff880`05deb5e8 fffff800`0342fa0c : 00000000`00000050 fffff880`05b02429 00000000`00000008 fffff880`05deb750 : nt!KeBugCheckEx
fffff880`05deb5f0 fffff800`03481e2e : 00000000`00000008 fffff880`05b02429 00000080`00000000 fffffa80`08b1c8f0 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`05deb750 fffff880`05b02429 : fffffa80`08aff720 00000000`00000001 fffff880`05deb960 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`05deb8e0 fffffa80`08aff720 : 00000000`00000001 fffff880`05deb960 00000000`00000000 00000000`00000000 : <Unloaded_nvhda64v.sys>+0xb429
fffff880`05deb8e8 00000000`00000001 : fffff880`05deb960 00000000`00000000 00000000`00000000 fffff880`00000000 : 0xfffffa80`08aff720
fffff880`05deb8f0 fffff880`05deb960 : 00000000`00000000 00000000`00000000 fffff880`00000000 fffff880`44427a00 : 0x1
fffff880`05deb8f8 00000000`00000000 : 00000000`00000000 fffff880`00000000 fffff880`44427a00 fffff880`05b102b5 : 0xfffff880`05deb960


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvhda64v+b429
fffff880`05b02429 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvhda64v+b429

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvhda64v

IMAGE_NAME:  nvhda64v.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0xCE_nvhda64v+b429

BUCKET_ID:  X64_0xCE_nvhda64v+b429

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

ok redid driver now its the waiting game.. i'll update in couple days see if it helped thx ZZ