Random BSOD Daily

I have a new Windows 7 Premium 64bit system, the computer has almost nothing on it but it is bluescreening, I can't find anything in particular that sets the BSOD off, it just happens usually one per day and there is no consistency in the error code, I will attach all of the minidump files that have occured on the system thus far. Could someone please give me a hand with this?

Some notes:

I use a 700W power supply, it is a no-name power supply which I have heard can cause problems.

I let memtest run for 8 passes and it came out clean

Also ran a syscheck /scannow which showed no issues

I use an old TV with VGA input for a monitor at the moment until I get a real computer monitor

I have not tried reloading the OS although I can do so if someone thinks it would be in my best interest to give it a try.

Please let me know your thoughts, and thank you for your time.

Twister1089 said:

I have a new Windows 7 Premium 64bit system, the computer has almost nothing on it but it is bluescreening, I can't find anything in particular that sets the BSOD off, it just happens usually one per day and there is no consistency in the error code, I will attach all of the minidump files that have occured on the system thus far. Could someone please give me a hand with this?

Some notes:

I use a 700W power supply, it is a no-name power supply which I have heard can cause problems.

I let memtest run for 8 passes and it came out clean

Also ran a syscheck /scannow which showed no issues

I use an old TV with VGA input for a monitor at the moment until I get a real computer monitor

I have not tried reloading the OS although I can do so if someone thinks it would be in my best interest to give it a try.

Please let me know your thoughts, and thank you for your time.

5 of nine caused by your video driver

Please re-install and follow these

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:

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

Symbol search path is: C:\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`02e61000 PsLoadedModuleList = 0xfffff800`0309ee50
Debug session time: Mon Nov 29 19:18:15.704 2010 (GMT-5)
System Uptime: 0 days 0:05:28.281
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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, {ffffffff80000004, fffff88004844316, fffff880035bdae8, fffff880035bd350}

Probably caused by : nvlddmkm.sys ( nvlddmkm+3c316 )

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

1: 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: ffffffff80000004, The exception code that was not handled
Arg2: fffff88004844316, The address that the exception occurred at
Arg3: fffff880035bdae8, Exception Record Address
Arg4: fffff880035bd350, Context Record Address

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


EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

FAULTING_IP: 
nvlddmkm+3c316
fffff880`04844316 0f5ec2          divps   xmm0,xmm2

EXCEPTION_RECORD:  fffff880035bdae8 -- (.exr 0xfffff880035bdae8)
ExceptionAddress: fffff88004844316 (nvlddmkm+0x000000000003c316)
   ExceptionCode: 80000004 (Single step exception)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880035bd350 -- (.cxr 0xfffff880035bd350)
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000002
rdx=0000000000000001 rsi=fffffa8007079d40 rdi=fffffa8003c079a0
rip=fffff88004844316 rsp=fffff880035bdd20 rbp=fffff880035beb00
 r8=fffff880035beb00  r9=fffff880035be840 r10=fffff88004f787a0
r11=fffff88004f786e0 r12=fffff880035be840 r13=fffffa80048eac00
r14=fffffa800590e0e0 r15=fffff880035bec90
iopl=0         nv up ei pl nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000217
nvlddmkm+0x3c316:
fffff880`04844316 0f5ec2          divps   xmm0,xmm2
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0x80000004 - {EXCEPTION}  Single Step  A single step or trace operation has just been completed.

LAST_CONTROL_TRANSFER:  from fffff880035be800 to fffff88004844316

STACK_TEXT:  
fffff880`035bdd20 fffff880`035be800 : fffffa80`072111a0 fffffa80`072111a0 00000000`00000000 00000000`00008000 : nvlddmkm+0x3c316
fffff880`035bdd28 fffffa80`072111a0 : fffffa80`072111a0 00000000`00000000 00000000`00008000 fffff880`00000000 : 0xfffff880`035be800
fffff880`035bdd30 fffffa80`072111a0 : 00000000`00000000 00000000`00008000 fffff880`00000000 fffff880`00000000 : 0xfffffa80`072111a0
fffff880`035bdd38 00000000`00000000 : 00000000`00008000 fffff880`00000000 fffff880`00000000 fffff880`04980e30 : 0xfffffa80`072111a0


FOLLOWUP_IP: 
nvlddmkm+3c316
fffff880`04844316 0f5ec2          divps   xmm0,xmm2

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+3c316

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4caecb0c

STACK_COMMAND:  .cxr 0xfffff880035bd350 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+3c316

BUCKET_ID:  X64_0x7E_nvlddmkm+3c316

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

Ken J

Is there anyway you could give me a quick walkthrough? The directions are prettyy vague

I did what you recommended, I deleted only my display drivers (keep in mind my nvidia drivers also contained physX and HDAudio drivers) and wiped it clean with the driver sweeper. I then went to NVIDIA and downloaded the most up to date version of the drivers I could find. I'll let you know if I have any more trouble or if that was it