New Mobo/CPU/RAM - > BSOD followed by missing/corrupt error on startup

tautology · 17 Jan 2011

Hey guys, I recently purchased a new motherboard/cpu/ram and did a fresh install of windows 7 to make sure I didn't have any driver problems. Shortly after installing however, I would get random BSOD followed by 2 different errors, either that "windows/system32/ntkrnlpa.exe is missing or corrupt, or that fvevol.sys critical system driver is missing or corrupt".

I've also had smaller errors, like sound randomly not working, and videos having very low FPS, which would fix itself upon restarting the computer.

I've ran a memory test using memtest86, which yielded no errors.

My specs:

Operating System
MS Windows 7 Ultimate 32-bit (retail)
CPU
AMD Phenom II X4 905
RAM
4.0GB Dual-Channel DDR3 @ 666MHz
Motherboard
MSI 870-G45
Graphics
NVIDIA GeForce 7900 GS (Microsoft Corporation - WDDM) (BFG Tech)
Hard Drives
488GB Seagate ST3500418AS ATA Device (SATA)

Everything is brand new except my video card (3 years old) and hard drive (2 years old).

edit: added BSOD dump
Attachment 132687

Any help would be greatly appreciated.

CarlTR6 · 17 Jan 2011

Hi, and welcome to the forum. I looked at your three latest dumps. All three indicate memory corruption.

Bugcheck A (2X), IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Bugcheck 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Out of date drivers can cause memory corruption and BSOD's. Update your video driver through the link provided. To remove any left over driver remnants, especially from graphics cards, use driver sweeper Guru3D - Driver Sweeper.

nvlddmkm.sys Thu May 14 16:32:27 2009 - nVidia Video drivers. Drivers - Download NVIDIA Drivers.

Update this driver and see if this improves your system's stability. Post back and let us know. If you get another BSOD, please upload it and we will go from there.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e02000 PsLoadedModuleList = 0x82f4a810
Debug session time: Mon Jan 17 15:29:47.867 2011 (GMT-5)
System Uptime: 0 days 0:03:25.225
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {393fe43, 1b, 1, 82e9a188}

Probably caused by : ntkrpamp.exe ( nt!KeFlushProcessWriteBuffers+135 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0393fe43, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e9a188, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f6a718
Unable to read MiSystemVaType memory at 82f4a160
 0393fe43 

CURRENT_IRQL:  1b

FAULTING_IP: 
nt!KeFlushProcessWriteBuffers+135
82e9a188 f390            pause

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8f8c77f8 -- (.trap 0xffffffff8f8c77f8)
ErrCode = 00000002
eax=00000007 ebx=8dd37940 ecx=000c00e1 edx=00000000 esi=00000001 edi=8dd36120
eip=82e9a188 esp=8f8c786c ebp=8f8c7890 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!KeFlushProcessWriteBuffers+0x135:
82e9a188 f390            pause
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e9a188 to 82e4882b

STACK_TEXT:  
8f8c77f8 82e9a188 badb0d00 00000000 8f8c7824 nt!KiTrap0E+0x2cf
8f8c7890 830378ed 00000001 a343619a 00000053 nt!KeFlushProcessWriteBuffers+0x135
8f8c7d00 8303850c 00000053 8f8c7d24 00000002 nt!ExpQuerySystemInformation+0x2516
8f8c7d1c 82e4544a 00000000 00313a88 00000020 nt!NtQuerySystemInformation+0x76
8f8c7d1c 777464f4 00000000 00313a88 00000020 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0079f434 00000000 00000000 00000000 00000000 0x777464f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeFlushProcessWriteBuffers+135
82e9a188 f390            pause

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeFlushProcessWriteBuffers+135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0xA_nt!KeFlushProcessWriteBuffers+135

BUCKET_ID:  0xA_nt!KeFlushProcessWriteBuffers+135

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

Debug session time: Mon Jan 17 15:25:24.769 2011 (GMT-5)
System Uptime: 0 days 0:12:42.502
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 970e3d94, 956bfad0, 0}

Probably caused by : win32k.sys ( win32k!GreSetSolidBrushLight+55 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 970e3d94, The address that the exception occurred at
Arg3: 956bfad0, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
win32k!GreSetSolidBrushLight+55
970e3d94 0305a09c1b97    add     eax,dword ptr [win32k!gpentHmgr (971b9ca0)]

TRAP_FRAME:  956bfad0 -- (.trap 0xffffffff956bfad0)
ErrCode = 00000000
eax=00017280 ebx=00000000 ecx=00000000 edx=00000001 esi=fd608c00 edi=00000001
eip=970e3d94 esp=956bfb44 ebp=956bfb70 iopl=0         nv up ei pl nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
win32k!GreSetSolidBrushLight+0x55:
970e3d94 0305a09c1b97    add     eax,dword ptr [win32k!gpentHmgr (971b9ca0)] ds:0023:971b9ca0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 97061168 to 970e3d94

STACK_TEXT:  
956bfb70 97061168 fd608c00 00000000 00000000 win32k!GreSetSolidBrushLight+0x55
956bfbc4 97061423 fe4c5728 4c101728 02718b1e win32k!GreDCSelectBrush+0x13b
956bfc54 97061704 956bfce8 0000f0f0 019cf150 win32k!GrePolyPatBltInternal+0xf9
956bfd18 82e5d44a 010113b4 00f00021 019cf150 win32k!NtGdiPolyPatBlt+0x1bc
956bfd18 773864f4 010113b4 00f00021 019cf150 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
019cf12c 00000000 00000000 00000000 00000000 0x773864f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!GreSetSolidBrushLight+55
970e3d94 0305a09c1b97    add     eax,dword ptr [win32k!gpentHmgr (971b9ca0)]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!GreSetSolidBrushLight+55

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cbe5b31

FAILURE_BUCKET_ID:  0x8E_win32k!GreSetSolidBrushLight+55

BUCKET_ID:  0x8E_win32k!GreSetSolidBrushLight+55

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

3: kd> lmtsmn
start    end        module name
8ba18000 8ba60000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
90c3f000 90c99000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
90dab000 90dbd000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
914d4000 914e5000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07)
8bb69000 8bb72000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8bb3d000 8bb46000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bb46000 8bb69000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8c011000 8c019000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:16 2009 (4A005480)
8bc17000 8bc1e000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
914a5000 914b3000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8b858000 8b860000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
93400000 93419000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
96e30000 96e4e000   cdd      cdd.dll      Mon Jul 13 21:04:18 2009 (4A5BD992)
8be11000 8be30000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
8b8a2000 8b94d000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8bfaf000 8bfd4000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8b860000 8b8a2000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8bd96000 8bdf3000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
91416000 91423000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
934ee000 934fb000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
91429000 9148d000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
9148d000 914a5000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
90d9f000 90dab000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8c000000 8c011000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
96bdd000 96bf6000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
93506000 9350f000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
934fb000 93506000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
9350f000 93520000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
934e4000 934ee000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
914e5000 9159c000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
9456d000 945a6000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
8bba6000 8bbb7000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8bb72000 8bba6000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8bc0e000 8bc17000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8bf7d000 8bfaf000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8c167000 8c198000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8322a000 83261000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
945d7000 945f6000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
96a0b000 96a1e000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
96bf6000 96bfc480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
96a00000 96a0b000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
93569000 935ee000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8c1f8000 8c200000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
915e7000 915ff000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
91400000 9140d000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80ba0000 80ba8000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
93437000 9346b000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
8bd83000 8bd96000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8bf2b000 8bf50000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
945a6000 945b8000   L1C62x86 L1C62x86.sys Fri Nov 27 02:48:10 2009 (4B0F843A)
93546000 93556000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
9352b000 93546000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8b83c000 8b847000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
93520000 9352b000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
93428000 93435000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
934ce000 934d9000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8bb27000 8bb3d000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8bbb7000 8bbdd680   MpFilter MpFilter.sys Tue Sep 14 17:23:59 2010 (4C8FE7EF)
935ee000 93600000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
a120f000 a1232000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
a1232000 a126d000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
a126d000 a1288000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
8b9d4000 8b9df000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8ba69000 8ba71000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8bd58000 8bd83000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
90d95000 90d9f000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8c1e8000 8c1f8000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8be36000 8beed000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
90dd5000 90de0000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
90c00000 90c22000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
934bd000 934ce000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
90cf1000 90cff000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
90c99000 90ccb000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8beed000 8bf2b000   NETIO    NETIO.SYS    Thu Apr 08 22:32:21 2010 (4BBE91B5)
9986e000 99879c00   NisDrvWFP NisDrvWFP.sys Tue Sep 14 17:24:12 2010 (4C8FE7FC)
8b9df000 8b9ed000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
90d8b000 90d95000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82e1a000 8322a000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
8bc29000 8bd58000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8bff5000 8bffc000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
93c07000 9456c940   nvlddmkm nvlddmkm.sys Thu May 14 16:32:27 2009 (4A0C7FDB)
90cd2000 90cf1000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
8baa6000 8bab7000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8ba71000 8ba9b000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8bb12000 8bb19000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8bb19000 8bb27000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bc00000 8bc0e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
a12a0000 a1337000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
96bae000 96bdd000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8b847000 8b858000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
90dbd000 90dd5000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
90c22000 90c3a000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
90de0000 90df7000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
8b822000 8b839000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
90d4a000 90d8b000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8b9ed000 8b9f7000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8bc1e000 8bc26000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8ba0d000 8ba15000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8b9cc000 8b9d4000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8bf50000 8bf7d000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
93556000 93569000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
90d3c000 90d49a60   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:44:34 2010 (4BC2DD72)
a1337000 a1341000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
945f6000 94600000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
90cff000 90d19000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8c1e0000 8c1e8000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
9981d000 9986e000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
a136f000 a13be000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
a1341000 a1362000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
93435000 93436380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8c01e000 8c167000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
a1362000 a136f000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8b817000 8b822000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8b800000 8b817000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
90d2c000 90d3c000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
96e00000 96e09000   TSDDD    TSDDD.dll    unavailable (00000000)
914b3000 914d4000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
9346b000 93479000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
96bfd000 96bfe700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
945c8000 945d7000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
945c2000 945c7c80   usbfilter usbfilter.sys Tue Dec 22 03:26:07 2009 (4B30829F)
93479000 934bd000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
945b8000 945c2000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
9159c000 915e7000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
934d9000 934e4000   usbprint usbprint.sys Mon Jul 13 20:17:06 2009 (4A5BCE82)
8ba9b000 8baa6000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8bdf3000 8bdff000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
96a23000 96bae000   viahduaa viahduaa.sys Sat May 15 06:20:43 2010 (4BEE757B)
8bbde000 8bbff000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8c198000 8c1a0380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8bab7000 8bac7000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8bac7000 8bb12000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c1a1000 8c1e0000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
90d19000 90d2c000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8ba00000 8ba0d000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8b94d000 8b9be000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8b9be000 8b9cc000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
90ccb000 90cd2000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
96fa0000 971eb000   win32k   win32k.sys   Tue Oct 19 23:00:01 2010 (4CBE5B31)
9140d000 91416000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:19:16 2009 (4A5BC0F4)
8ba60000 8ba69000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)

Unloaded modules:
9987a000 998e4000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a1288000 a12a0000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bfd4000 8bfe1000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bfe1000 8bfec000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bfec000 8bff5000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8be00000 8be11000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

tautology · 18 Jan 2011

Thanks for responding Carl. I did actually update those drivers quite recently from the NVIDIA website, but now that I look at my current driver version, it doesn't match. It says that my current driver is from 2009, where as the latest driver online is from 2010. So I guess this means that for some reason it didn't install the driver properly from before. This time around however it worked, the date on my drivers matches the one online, so this definitely could have been the problem. Hopefully this was the issue.

Thanks for the help.

CarlTR6 · 18 Jan 2011

You are welcome. I hope the solution to your problem is this easy. :)

tautology · 19 Jan 2011

Unfortunately it looks like the problem came back.

At first I had crashes inside a video game, followed by an error, which led me to believe that my problem was my old graphics card, but then I also got several BSODs, and then constant crashes of various windows programs (like Windows Explorer, Windows Live Communications Platform, etc) , along with firefox, skype, msn messenger, and flash player constantly crashing.

I reformatted my C drive and reinstalled Windows 7 once again, but I had literally the same problems come up once again; random BSOD, critical system driver missing or corrupt errors on startup, programs crashing, and even weird sound tears from time to time. I'm really starting to think that something is wrong with the motherboard, even though it is brand new.

edit: another interesting fact, the interface for the taskbar and firefox sometimes looks like it is in safemode for a minute or so (looking like windows 2000) , before returning back to the windows 7 style. Also the keyboard has randomly stopped working for a short amount of time on several occasions.

Well this just keeps getting worse and worse. Now the sound randomly disappears and videos slow down.

tautology · 21 Jan 2011

Ran Prime95 and got a bunch of errors.

Got errors on 2/4 tests after a few hours for the FFT option, and got instant errors on all four tests with the Blend option.

Has to be defective CPU or motherboard at this point?

CarlTR6 · 21 Jan 2011

It also could be RAM. Have you run Memtest? If not, run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for a minimum of seven passes; this will take 6-8 hours. Follow the instructions in this tutorial and post back with your results: RAM - Test with Memtest86+

tautology · 23 Jan 2011

Ran memtest, the problem appears to be the second stick of RAM (first stick passed 7 times with no errors, second had errors on first pass). Also ran my computer on each stick separately to be sure, no problems with stick 1 and BSOD with stick 2. Going to RMA it now. Thanks for the help!

CarlTR6 · 23 Jan 2011

You are very welcome for the help. Thank you for reporting back. I am glad you were able to isolate the problem. Good job! Let us know when you get your replacement stick and how your system runs.