BlueScreen - BCCode 23

[Joshatdot]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 23
BCP1: 00000000000E0107
BCP2: FFFFF8800314D318
BCP3: FFFFF8800314CB80
BCP4: FFFFF80002CEC137
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092410-18704-01.dmp
C:\Users\Josh\AppData\Local\Temp\WER-25685814-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

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

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
- the original installed OS on the system?
- an OEM or full retail version?
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
- What is the age of OS installation (have you re-installed the OS?)

W7 Pro x64
Original
Retail Upgrade
1 year, 10 months old hardware
Nearly 10 months since last W7 install.


I think it had to do something with my USB HD, when I logged back in W7 asked me to CHKDSK it. It started to do the test, then I heard the drive go 'twang' pause 'twang' pause 'twang' .. kinda like a lil spring going twang. The USB HD was hooked up to the back on a standard USB mini cable. I then tried the USB mini Y cable (2 USB jacks to a single mini plug), and ran CHKDSK again. Found some file errors, and no twanging.

I just use the USB HD for light storage .. so I don't see why this would create a BSOD.

It's a Oyen Digital model UN2-54-160-S, 160GB External USB Powered 2.5" Mini Portable Hard Drive

 

[Joshatdot]

I enabled the Driver Verifier thing, and after reboot I got a BSOD .. didnt see it long enuff to see what happened. After auto-reboot, W7 booted in to Repair mode, and asked me to do a Restore.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: f7
BCP1: FFFFF88003176F98
BCP2: 00002B992DDFA232
BCP3: FFFFD466D2205DCD
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092410-17409-01.dmp
C:\Users\Josh\AppData\Local\Temp\WER-49998-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

 

[Lemur]

Correction. Your system is: V2-M3N8200

Have you OC'd your video card? If you have, undo that. That may solve it in itself.

 

[CarlTR6]

Error code F7, DRIVER_OVERRAN_STACK_BUFFER - usual causes are a driver or malware.

This is a Driver Verifier enabled dump. When enabled, Driver Verifier will trigger a BSOD when it encounters a faulty driver. Hopefully, the resulting dump points out the offending driver. Your dump blames nvlddmkm.sys which is an Nvidia video driver. Itonically, the is the second BSOD I've looked at today blaming nvlddmkm.sys. Check this post for a possible solution: http://www.sevenforums.com/crashes-debugging/113476-bsod-when-watching-bluray.html#post977337

I found an almost guaranteed cause of BSOD's. Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.

Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Fri Sep 24 21:33:42.373 2010 (GMT-4)
System Uptime: 0 days 0:00:12.370
Loading Kernel Symbols
...............................................................
.....................................
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {fffff88003176f98, 2b992ddfa232, ffffd466d2205dcd, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+16d3a6 )

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

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

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: fffff88003176f98, Actual security check cookie from the stack
Arg2: 00002b992ddfa232, Expected security check cookie
Arg3: ffffd466d2205dcd, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

SECURITY_COOKIE:  Expected 00002b992ddfa232 found fffff88003176f98

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xF7

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880100673a6 to fffff80002ccf740

STACK_TEXT:  
fffff880`03175df8 fffff880`100673a6 : 00000000`000000f7 fffff880`03176f98 00002b99`2ddfa232 ffffd466`d2205dcd : nt!KeBugCheckEx
fffff880`03175e00 00000000`000000f7 : fffff880`03176f98 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000 : nvlddmkm+0x16d3a6
fffff880`03175e08 fffff880`03176f98 : 00002b99`2ddfa232 ffffd466`d2205dcd 00000000`00000000 fffff800`02cfc4eb : 0xf7
fffff880`03175e10 00002b99`2ddfa232 : ffffd466`d2205dcd 00000000`00000000 fffff800`02cfc4eb fffff880`1075158c : 0xfffff880`03176f98
fffff880`03175e18 ffffd466`d2205dcd : 00000000`00000000 fffff800`02cfc4eb fffff880`1075158c fffff880`100656ab : 0x2b99`2ddfa232
fffff880`03175e20 00000000`00000000 : fffff800`02cfc4eb fffff880`1075158c fffff880`100656ab fffff880`10b2e5c4 : 0xffffd466`d2205dcd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+16d3a6
fffff880`100673a6 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvlddmkm+16d3a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c37918e

FAILURE_BUCKET_ID:  X64_0xF7_VRF_MISSING_GSFRAME_nvlddmkm+16d3a6

BUCKET_ID:  X64_0xF7_VRF_MISSING_GSFRAME_nvlddmkm+16d3a6

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

2: kd> lmtsmn
start             end                 module name
fffff880`0119f000 fffff880`011f6000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d21000 fffff880`02dab000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0364f000 fffff880`03664000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00ec0000 fffff880`00ecb000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`03671000 fffff880`03679000   ASACPI   ASACPI.sys   Wed May 13 21:25:17 2009 (4A0B72FD)
fffff880`03622000 fffff880`03629000   AsIO     AsIO.sys     Mon Dec 17 04:11:49 2007 (47663D55)
fffff880`00e8d000 fffff880`00e96000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e96000 fffff880`00ec0000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`03600000 fffff880`03622000   avipbb   avipbb.sys   Mon Feb 22 05:08:50 2010 (4B8257B2)
fffff880`019e0000 fffff880`019e7000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`037db000 fffff880`037ec000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`00c00000 fffff880`00c2a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cc2000 fffff880`00d82000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01971000 fffff880`019a1000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c64000 fffff880`00cc2000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01407000 fffff880`0147a000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`019a1000 fffff880`019af000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0373a000 fffff880`037bd000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`037bd000 fffff880`037db000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`0372b000 fffff880`0373a000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`0195b000 fffff880`01971000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`03f2b000 fffff880`03f4d000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`019bb000 fffff880`019c4000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`019af000 fffff880`019bb000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`019c4000 fffff880`019d7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0fe00000 fffff880`0fef4000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`10b8e000 fffff880`10bd4000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`03ec6000 fffff880`03eed500   Envy24HF Envy24HF.sys Wed Apr 06 06:07:18 2005 (4253B4D6)
fffff880`03664000 fffff880`03671000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`00d82000 fffff880`00d96000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00fb3000 fffff880`00fff000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0148b000 fffff880`01495000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01921000 fffff880`0195b000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01817000 fffff880`01861000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c16000 fffff800`02c5f000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03ea2000 fffff880`03ec6000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`01918000 fffff880`01921000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bb2000 fffff800`00bbc000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03f4d000 fffff880`03f90000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013de000 fffff880`013f8000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01200000 fffff880`0122b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`03f90000 fffff880`03f95200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`00c43000 fffff880`00c50000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00e73000 fffff880`00e8d000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02cda000 fffff880`02ce5000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`011f6000 fffff880`01200000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00da2000 fffff880`00e00000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03720000 fffff880`0372b000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01906000 fffff880`01918000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01495000 fffff880`01587000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c26000 fffff880`02c35000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02dab000 fffff880`02df0000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01587000 fffff880`015e7000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02ce5000 fffff880`02cf6000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03714000 fffff880`03720000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c5f000 fffff800`0323b000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0123b000 fffff880`013de000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`019d7000 fffff880`019e0000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`10b8c000 fffff880`10b8d180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`0fefa000 fffff880`10b8be00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`03f96000 fffff880`03fe7500   nvmf6264 nvmf6264.sys Thu Jul 30 19:48:18 2009 (4A723142)
fffff880`03679000 fffff880`03684000   nvsmu    nvsmu.sys    Mon Jun 29 03:36:37 2009 (4A486F05)
fffff880`02c00000 fffff880`02c26000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00f89000 fffff880`00f9e000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`0100d000 fffff880`01040000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e63000 fffff880`00e73000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0147a000 fffff880`0148b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`03eee000 fffff880`03f2b000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c50000 fffff880`00c64000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00d96000 fffff880`00da1ae0   PxHlpa64 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D)
fffff880`036c3000 fffff880`03714000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02cbf000 fffff880`02cc8000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02cc8000 fffff880`02cd1000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02cd1000 fffff880`02cda000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`018cc000 fffff880`01906000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01170000 fffff880`0119f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`018c5000 fffff880`018cc000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`018bd000 fffff880`018c5000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01041000 fffff880`01167000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`02d14000 fffff880`02d21000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02cf6000 fffff880`02d14000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02c50000 fffff880`02c64000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03629000 fffff880`0364f000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`03e91000 fffff880`03ea2000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`03684000 fffff880`0368f000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`03e3b000 fffff880`03e91000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`01000000 fffff880`0100d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019e7000 fffff880`019f5000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02c8a000 fffff880`02caf000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01861000 fffff880`01871000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f9e000 fffff880`00fb3000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01871000 fffff880`018bd000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02c35000 fffff880`02c50000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02caf000 fffff880`02cbf000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ed6000 fffff880`00f7a000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f7a000 fffff880`00f89000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02df0000 fffff880`02df9000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`01167000 fffff880`01170000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

While you are troubleshooting, I suggest that you uninstall Avira using this uninstall tool: Info > Tool. Avira is known to cause BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place. When you get your system stabilized, you can try Avira again; but I don't recommend it.

I find outdated drivers on your system. Some are really obsolete. Older drivers can and do cause conflicts, memory corruption and crashes.

AsIO.sys Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility ASUSTeK Computer Inc.-Support-

Envy24HF.sys Wed Apr 06 06:07:18 2005 - This is an XP driver. Envy24 Family Audio Controller WDM by VIA/IC Ensemble VIA Vinyl Audio - VIA Technologies, Inc.. This is very obsolete. If there is no updated driver, uninstall the software/hardware.


nvmf6264.sys Thu Jul 30 19:48:18 2009 - nVidia Networking Controller Driver (nForce chipset driver)Drivers - Download NVIDIA Drivers

nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers

PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK This will break your CD/DVD program, but can easily be renamed after we've finished. For best results, I suggest that you uninstall the program.

Update your NVidia chipset drivers. Next update the 2005 and 2007 drivers. If updated drivers are not available, uninstall the software/hardware these drivers are related to.

After you accomplish the above, reboot and run your system. Let's see how it does. If you get another BSOD upload it. Post back and update us on how your system is doing.

 

[Joshatdot]

Correction. Your system is: V2-M3N8200

Have you OC'd your video card? If you have, undo that. That may solve it in itself.

It came from MSI OC'd .. I haven't had any problems with it at all (hopefully its not dieing now)

 

[Lemur]

Correction. Your system is: V2-M3N8200

Have you OC'd your video card? If you have, undo that. That may solve it in itself.

It came from MSI OC'd .. I haven't had any problems with it at all (hopefully its not dieing now)

If you have another card you could swap out temporarily, that would be interesting to see the results.

 

[Joshatdot]

Error code F7, DRIVER_OVERRAN_STACK_BUFFER - usual causes are a driver or malware.

I did notice on my USB HDD some random numbers & letters Folder I don't remember seeing before, and I deleted it.

This is a Driver Verifier enabled dump. When enabled, Driver Verifier will trigger a BSOD when it encounters a faulty driver. Hopefully, the resulting dump points out the offending driver. Your dump blames nvlddmkm.sys which is an Nvidia video driver. Itonically, the is the second BSOD I've looked at today blaming nvlddmkm.sys. Check this post for a possible solution: http://www.sevenforums.com/crashes-debugging/113476-bsod-when-watching-bluray.html#post977337

Will check that out

I found an almost guaranteed cause of BSOD's. Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.

Been using Daemon Tools for years, never had a BSOD using it before.

While you are troubleshooting, I suggest that you uninstall Avira using this uninstall tool: Info > Tool. Avira is known to cause BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place. When you get your system stabilized, you can try Avira again; but I don't recommend it.

Again, I've been using Avira for years, and over 18 months with W7 x64since RC1.

I find outdated drivers on your system. Some are really obsolete. Older drivers can and do cause conflicts, memory corruption and crashes.

AsIO.sys Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility ASUSTeK Computer Inc.-Support-

Envy24HF.sys Wed Apr 06 06:07:18 2005 - This is an XP driver. Envy24 Family Audio Controller WDM by VIA/IC Ensemble VIA Vinyl Audio - VIA Technologies, Inc.. This is very obsolete. If there is no updated driver, uninstall the software/hardware.


nvmf6264.sys Thu Jul 30 19:48:18 2009 - nVidia Networking Controller Driver (nForce chipset driver)Drivers - Download NVIDIA Drivers

nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers

PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK This will break your CD/DVD program, but can easily be renamed after we've finished. For best results, I suggest that you uninstall the program.

Update your NVidia chipset drivers. Next update the 2005 and 2007 drivers. If updated drivers are not available, uninstall the software/hardware these drivers are related to.

After you accomplish the above, reboot and run your system. Let's see how it does. If you get another BSOD upload it. Post back and update us on how your system is doing.

Asus Probe, heh, haven't used that in months, will get rid of it.

Newer Envy24 drivers wont let me activate/use the HQ Alt Outs, will not update.

Nvidia NForce Chipset drivers are the newest offered, can't update.

PxHlpa64.sys .. Hmm...not sure what that came from.

 

[Joshatdot]

Correction. Your system is: V2-M3N8200

Have you OC'd your video card? If you have, undo that. That may solve it in itself.

It came from MSI OC'd .. I haven't had any problems with it at all (hopefully its not dieing now)

If you have another card you could swap out temporarily, that would be interesting to see the results.

No other vid card .. besides the onboard GF8200 .. but I don't want to use it. When I first built this system, I used the onboard .. and with in weeks the GF8200 fried itself, and had to RMA the Barebones.

 

[Joshatdot]

for S&G's I did the Driver Verifier thing again .. no BSOD on this reboot.

 

[CarlTR6]

You may have been using Daemon Tools for years; but you haven't been using it for years on a Win 7 system. It is a nearly guaranteed BSOD maker with Win 7. The driver, sptd.sys, is not compatible with Win 7. Even the latest version of this driver causes crashes.

Troubleshooting is often a process of elimination. You eliminate the known possible causes of BSOD's right off the bat. And that includes Avira. We have no way of knowing if Avira is causing instability on your system. But we do know Avira has caused problems on some, not all, Win 7 systems. Once you get your system running smoothly, you can reinstall Avira and Daemon Tools. If you start getting crashes again, you will know that one or the other, or both, triggered the crashes.

When you enable Driver Verifier, you should use your system normally for about 36 hours (not a straight 36 hours ) with Driver Verifier enabled. This gives it time to encounter the various drivers you system uses. When Driver Verifier triggers a BSOD during booting or shortly thereafter, it means it found a faulty driver loading during your startup. Not all drivers load during the boot process. Some only load when they are needed.

 

[Joshatdot]

No BSODs today. I still have the Driver Verifier going. I rarely have stuff mounted in Daemon Tools, or even have it running. Avira is always updated.

So far still stable ..

 

[CarlTR6]

Good news. After about 36 hours of use, you can turn driver verifier off it you get no BSOD's. Keep us posted.

 

[Joshatdot]

PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK This will break your CD/DVD program, but can easily be renamed after we've finished. For best results, I suggest that you uninstall the program.

Weird .. I must have really needed that file. I just noticed my DVD drive wasn't showing anymore. I have no idea what program installed it, and why when it's renamed, my DVD drive doesn't show anymore.

PxHlpa64.sys - Px Engine Device Driver for 64-bit Windows, PxHelp64, (c) Sonic Solutions


edit: Is it normal for my system to be sluggish when that Driver Verifier Enabled?

 

[CarlTR6]

Yes, it is normal for Driver Verifier to slow your system down some.

Renaming that driver will definitely break the program. After you get your system running smoothly, you can rename it again. We are just eliminating one potential cause of BSOD's.