BSOD, help please

[CarlTR6]

You will have to ask the hardware guys that question. I will be buying a new motherboard this fall and I'll ask them for their advice. I will caution you that if you are planning on using your current RAM sticks, make sure the motherboard you buy is compatible with the RAM.

 

[Jonathan_King]

That board looks good to me. Compatible with your current RAM and CPU, a major plus.

 

[kuleee]

current status:
i have dual boot windows xp and windows 7 (3 hard drives, one is separated into 2 partitions of 40gb, on each is one operating system). 2 days ago i installed vista and all of my software including all drivers, and system crashed a few times so i formatted this vista partition from xp and have decided to continue use my xp in peace before i buy new motherboard. then yesterday just in curiosity i AGAIN installed windows 7 but i did not install any update or any driver and windows works fine for 13 hours for now! only thing that i installed on win7 now is: winrar, mozilla (+flash player), microsoft security essentials, easybcd (software for boot options), winamp and msn. result is that windows are now stable, i will let them run until they crash... if they dont crash for 48 hours then i will install one driver at a time (first for gpu) and test computer when it crashes... also im so crippled without any of my usual programs (its probably noobish of me, but i didn't even install MS office, adobre reader, video codecs or any media player, just in case they could be responsible for my bsod's). please reply, i would really like to see what you think of this. thanks!

 

[CarlTR6]

That is the way to troubleshoot when you suspect a third party driver or software is causing conflicts. If you create a restore point just before you install something, you can easily revert back if that installation causes problems. Good indicative on your part. You are on a good track.

There are some free alternatives to Adobe Reader that are more secure, less intrusive, and use less resources, Foxit Reader being one.

 

[kuleee]

i know for foxit, but that program is frustrating me, i am adobe fan well i will make restore point now, good point, and thank you!

 

[CarlTR6]

You are welcome. Good luck and keep us updated.

 

[kuleee]

36 hours still without any bsod! i have installed some software 12 hours ago, they obviously not in the system's way of normal work. still not a single driver or any microsoft update installed

http://img827.imageshack.us/img827/8558/44424244.jpg

 

[Tews]

Sounds like you have it all in order...

 

[CarlTR6]

36 hours still without any bsod! i have installed some software 12 hours ago, they obviously not in the system's way of normal work. still not a single driver or any microsoft update installed

http://img827.imageshack.us/img827/8558/44424244.jpg

That is GREAT news! Let's keep the thread open for a few more days as you install more programs. Please keep us updated.

 

[Jonathan_King]

My advice to you, create a system image now.

Also, create a restore point.

Then install all of the updates. If it goes bad again, first, try restoring from the restore point, using the system image if that doesn't work.

 

[kuleee]

i had bsod 1min ago!!!! finally right?
also, my windows gadgets (only default clock) have stopped working for 2-3 times already, and i need to restart them... any reason why is that happening? btw i still didn't install any drivers, so bsod is caused by some of my software probably? if any more bsod's happen i will go to that last restore point before installing adobe reader, skype, utorrent and some other stuff.. btw here are the files so take a look and reply

 

[Jonathan_King]

No dump was in that report. When I investigated, I saw that it was saved in F:\ instead.

In fact, the Windows directory was F, so that means you ran the tool from a different OS than the crash?

Now the bugcheck was 0x50; very rarely does that point to a specific third-party driver. It usually means bad memory (RAM or video card) or other hardware.

Test RAM again, this time leaving it for 7 passes or more.

Where did you get your copy of Windows 7?

Event[73]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2010-09-25T10:42:18.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: kule-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffffb, 0x00000000, 0x82917f03, 0x00000000). A dump was saved in: F:\Windows\MEMORY.DMP. Report Id: .

 

[CarlTR6]

I really did not want to see you have another BSOD. There was no dump file in your upload; but one was generated. I did look at an error report and found this about your crash:

Faulting application name: sidebar.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc613
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdadb
Exception code: 0xc0000005

The code, 0xc0000005, refers to memory corruption. This does not necessarily mean bad RAM; but that could be the case. A conflict could be corrupting memory. The problem was triggered by sidebar.exe which is part of running your gadgets. Keep in mind that installing software does install drivers. Some software includes its own drivers. Adobe definitely installs drivers as do Skype and Utorrent.

There is an alternative to Adobe Reader which is not nearly as invasive to your system and uses less resources, Foxit Reader. Run msconfig and stop Adobe Reader Speed Launch and the other Adobe program from running at startup.

 

[kuleee]

i "steal" all of my operating system discs from my brothers office, he runs his own business in our house, and have all os's in one place. hey, at least im honest! he has 50.000$ software worth, including autocad, office 1997 and 2003 and so on, so please give me a break. and btw i have dual boot, as i said before, so my XP is installed on c:, and win7 is on f:... i tried to manage it through my computer but i cannot reassign hard drives or change their names... should i restore computer to last point or just turn sidebar and gadgets off?

 

[CarlTR6]

I would restore the computer and try the gadgets again.

 

[zigzag3143]

Smart idea Carl.


That memory exception is often caused by a poorly written software, and gadgets would be a perfect example. Especially gadgets that constantly update like time or cpu/ram. They sometimes have a memory leak.

 

[Jonathan_King]

Do me a favor, and open an elevated command prompt and enter sfc /scannow.

On an installation so new, we should not see any errors.

 

[CarlTR6]

Smart idea Carl.


That memory exception is often caused by a poorly written software, and gadgets would be a perfect example. Especially gadgets that constantly update like time or cpu/ram. They sometimes have a memory leak.

Thanks for the backup and the additional information. I learned as I'm sure the OP will.

Do me a favor, and open an elevated command prompt and enter sfc /scannow.

On an installation so new, we should not see any errors.

That is another smart idea. Thanks, Lancaster.

 

[kuleee]

i woke up this morning and have something to see... there was a bsod over night, when i looked into minidump folder i saw 2 files, so 2 bsods :S anyway, i have restored my system to earlier point and turned off clock gadget
sfc scan have just ended also, "windows resource protection did not find any integrity violations"

 

[CarlTR6]

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usual causes are Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS. This dump blames a Windows system core file (very likely not the cause) and references memory.

Error code 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED - usually caused by 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. The dump blames fltmgr.sys and points to memory corruption. Fltmgr.sys is a Windows system driver and most likely not the cause; it was probably affected by something else.

Kernel base = 0x82848000 PsLoadedModuleList = 0x82987570
Debug session time: Sun Sep 26 04:33:37.002 2010 (GMT-4)
System Uptime: 0 days 6:50:20.002
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffb, 0, 8295ff03, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+466 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffb, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8295ff03, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 829a7700
Unable to read MiSystemVaType memory at 829870c0
 fffffffb 

FAULTING_IP: 
nt!ExFreePoolWithTag+466
8295ff03 0fb74ffa        movzx   ecx,word ptr [edi-6]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  80e57b94 -- (.trap 0xffffffff80e57b94)
ErrCode = 00000000
eax=00000000 ebx=00000dc6 ecx=00000000 edx=00000000 esi=00000001 edi=00000001
eip=8295ff03 esp=80e57c08 ebp=80e57c60 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!ExFreePoolWithTag+0x466:
8295ff03 0fb74ffa        movzx   ecx,word ptr [edi-6]     ds:0023:fffffffb=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82880968 to 828a6c46

STACK_TEXT:  
80e57b7c 82880968 00000000 fffffffb 00000000 nt!MmAccessFault+0xbf
80e57b7c 8295ff03 00000000 fffffffb 00000000 nt!KiTrap0E+0xdc
80e57c60 82aa79ec 00000001 e24e4d43 80e57cec nt!ExFreePoolWithTag+0x466
80e57c90 82ad7e32 829a5440 8520cd48 82979d7c nt!CmpFreeKeyControlBlock+0x57
80e57d00 828a3043 00000000 00000000 8520cd48 nt!CmpDelayCloseWorker+0x297
80e57d50 82a2fd16 00000001 b0d020fe 00000000 nt!ExpWorkerThread+0x10d
80e57d90 828d1159 828a2f36 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+466
8295ff03 0fb74ffa        movzx   ecx,word ptr [edi-6]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ExFreePoolWithTag+466

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbffc

FAILURE_BUCKET_ID:  0x50_nt!ExFreePoolWithTag+466

BUCKET_ID:  0x50_nt!ExFreePoolWithTag+466

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

Debug session time: Sat Sep 25 21:42:21.938 2010 (GMT-4)
System Uptime: 0 days 0:26:55.939
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8c778885, 9d36aa20, 0}

Probably caused by : fltmgr.sys ( fltmgr!TreeFindNodeOrParent+11 )

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

1: 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: 8c778885, The address that the exception occurred at
Arg3: 9d36aa20, 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: 
fltmgr!TreeFindNodeOrParent+11
8c778885 8b4110          mov     eax,dword ptr [ecx+10h]

TRAP_FRAME:  9d36aa20 -- (.trap 0xffffffff9d36aa20)
ErrCode = 00000000
eax=86e2b644 ebx=86e2b644 ecx=00000001 edx=ffffffff esi=85fcd7bc edi=86e2b624
eip=8c778885 esp=9d36aa94 ebp=9d36aa94 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
fltmgr!TreeFindNodeOrParent+0x11:
8c778885 8b4110          mov     eax,dword ptr [ecx+10h] ds:0023:00000011=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8c7788ed to 8c778885

STACK_TEXT:  
9d36aa94 8c7788ed 86e2b644 85316840 ffffffff fltmgr!TreeFindNodeOrParent+0x11
9d36aaac 8c778993 86e2b644 85316840 ffffffff fltmgr!TreeLookup+0x17
9d36aad0 8c778b18 86e2b644 85316840 ffffffff fltmgr!TreeUnlinkMultiDoWalk+0x21
9d36aaf0 8c78c208 86e2b644 85316840 ffffffff fltmgr!TreeUnlinkMulti+0x46
9d36ab10 8c78c6d9 86e2b5f0 00004000 85316840 fltmgr!DeleteNameCacheNodes+0x84
9d36ab30 8c770cd8 85fcd3e8 85316840 86e2b5f0 fltmgr!FltpRemoveAllNamesCachedForFileObject+0x3f
9d36ab9c 8c7739f0 9d36abf0 855a0408 855a05e0 fltmgr!FltpPerformPreCallbacks+0x53a
9d36abb4 8c773f01 9d36abf0 00000000 85fcd928 fltmgr!FltpPassThroughInternal+0x40
9d36abd8 8c7743ba 0236abf0 85fcd928 85316840 fltmgr!FltpPassThrough+0x203
9d36ac08 82849f44 85fcd928 855a0408 86020024 fltmgr!FltpDispatch+0xb4
9d36ac20 82a337ff 851ef770 85316828 00000000 nt!IofCallDriver+0x63
9d36ac64 82a6321f 85316840 85316840 85316828 nt!IopDeleteFile+0x10c
9d36ac7c 8287136a 00000000 85442d48 85316828 nt!ObpRemoveObjectRoutine+0x59
9d36ac90 828712da 85316840 82a33ebc 822fc598 nt!ObfDereferenceObjectWithTag+0x88
9d36ac98 82a33ebc 822fc598 85442d48 000004e0 nt!ObfDereferenceObject+0xd
9d36acdc 82a5edd9 822fc598 822ff9c0 86b21800 nt!ObpCloseHandleTableEntry+0x21d
9d36ad0c 82a5ef7f 86b21800 85442d01 0166f99c nt!ObpCloseHandle+0x7f
9d36ad28 8285079a 000004e0 0166f9a0 76fc64f4 nt!NtClose+0x4e
9d36ad28 76fc64f4 000004e0 0166f9a0 76fc64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0166f9a0 00000000 00000000 00000000 00000000 0x76fc64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fltmgr!TreeFindNodeOrParent+11
8c778885 8b4110          mov     eax,dword ptr [ecx+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  fltmgr!TreeFindNodeOrParent+11

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf11

FAILURE_BUCKET_ID:  0x8E_fltmgr!TreeFindNodeOrParent+11

BUCKET_ID:  0x8E_fltmgr!TreeFindNodeOrParent+11

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

1: kd> lmtsmn
start    end        module name
8c614000 8c65c000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8cf8c000 8cfe6000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
93a78000 93a8a000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8c765000 8c76e000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8c739000 8c742000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c742000 8c765000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
9342b000 9387f000   atikmdag atikmdag.sys Fri Apr 24 06:50:20 2009 (49F1996C)
8cef8000 8ceff000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
92ca3000 92cb1000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8c4a0000 8c4a8000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
92e46000 92e5f000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
98c40000 98c5e000   cdd      cdd.dll      unavailable (00000000)
8ceaf000 8cece000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
8c4ea000 8c595000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8ce58000 8ce7d000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8c4a8000 8c4ea000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8c97b000 8c9d8000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
93a6b000 93a78000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
93400000 9340d000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
92c27000 92c8b000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
92c8b000 92ca3000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8cbec000 8cbf8000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8ce47000 8ce58000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
93be7000 93c00000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
93418000 93421000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
9340d000 93418000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
92d34000 92d45000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
92d6e000 92d78000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
9387f000 93936000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:26:15 2009 (4A5BC297)
93936000 9396f000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
8c7a2000 8c7b3000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8c76e000 8c7a2000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8c9e6000 8c9ef000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8ce15000 8ce47000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8cd4f000 8cd80000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82c1b000 82c52000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
9396f000 9398e000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
92ce4000 92d34000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
92d50000 92d63000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
93421000 93427480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
92d45000 92d50000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
92dc1000 92e46000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8ce0d000 8ce15000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
93a2f000 93a47000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
92cd2000 92ce4000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
93a47000 93a54000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80ba0000 80ba8000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
93b21000 93b55000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709)
8c968000 8c97b000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8cae4000 8cb09000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468)
92d9e000 92dae000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
92d83000 92d9e000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8c417000 8c48f000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
92d78000 92d83000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
93a54000 93a61000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
92d63000 92d6e000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8c723000 8c739000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8cece000 8cef1000   MpFilter MpFilter.sys Sat Mar 20 00:03:26 2010 (4BA4490E)
9c937000 9c93fe00   MpNWMon  MpNWMon.sys  Sat Mar 20 00:03:24 2010 (4BA4490C)
92e5f000 92e71000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
92e71000 92e94000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:14:24 2009 (4A5BBFD0)
92e94000 92ecf000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA)
92ecf000 92eea000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5)
8cf51000 8cf5c000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8c665000 8c66d000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8c93d000 8c968000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8cbe2000 8cbec000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8cdfd000 8ce0d000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8c9ef000 8caa6000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
93aa2000 93aad000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
93aad000 93acf000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
93ba7000 93bb8000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8cfed000 8cffb000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8cb09000 8cb3b000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8caa6000 8cae4000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8cf5c000 8cf6a000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8cbd8000 8cbe2000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
8281b000 82c1b000   nt       ntkrnlmp.exe Mon Jul 13 19:15:08 2009 (4A5BBFFC)
8c80e000 8c93d000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8cef1000 8cef8000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
8cb3b000 8cb5a000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
93a17000 93a2f000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
8c6a2000 8c6b3000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
92eea000 92ef1000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
8c66d000 8c697000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8c70e000 8c715000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8c715000 8c723000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c9d8000 8c9e6000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
92ef1000 92f88000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
93bb8000 93be7000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8c48f000 8c4a0000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
93a8a000 93aa2000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
93acf000 93ae7000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
93ae7000 93afe000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
93afe000 93b15000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8cb97000 8cbd8000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
93b15000 93b1f000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8cf39000 8cf41000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8cf41000 8cf49000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8cf49000 8cf51000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8cdd0000 8cdfd000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
92dae000 92dc1000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
9398e000 939b3000   Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
92f88000 92f92000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
93a61000 93a6b000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8cb5a000 8cb74000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8cdc8000 8cdd0000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
9c87c000 9c8cd000   srv      srv.sys      Mon Jul 13 19:15:10 2009 (4A5BBFFE)
9c82d000 9c87c000   srv2     srv2.sys     Mon Jul 13 19:14:52 2009 (4A5BBFEC)
92f92000 92fb3000   srvnet   srvnet.sys   Mon Jul 13 19:14:45 2009 (4A5BBFE5)
93b1f000 93b20380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8cc06000 8cd4f000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
92fb3000 92fc0000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8cf81000 8cf8c000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8cf6a000 8cf81000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8cb87000 8cb97000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
98c10000 98c19000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
92cb1000 92cd2000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
93b55000 93b63000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
93428000 93429700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
93a08000 93a17000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
93b63000 93ba7000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
939b3000 939bd000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
939bd000 93a08000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
8c697000 8c6a2000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8ceff000 8cf0b000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8cf0b000 8cf2c000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8cd80000 8cd88380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8c6b3000 8c6c3000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8c6c3000 8c70e000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8cd89000 8cdc8000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8cb74000 8cb87000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8cf2c000 8cf39000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8c595000 8c606000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8c606000 8c614000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8cfe6000 8cfed000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
98db0000 98ffa000   win32k   win32k.sys   Mon Jul 13 19:26:26 2009 (4A5BC2A2)
8c65c000 8c665000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)

Unloaded modules:
9c8cd000 9c937000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8ce7d000 8ce8a000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8ce8a000 8ce95000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8ce95000 8ce9e000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8ce9e000 8ceaf000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

You still have a couple of outdated drivers.

atikmdag.sys Fri Apr 24 06:50:20 2009 - This one is known to cause problems. ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)Global Provider of Innovative Graphics, Processors and Media Solutions | AMD.

Rt86win7.sys Thu Feb 26 04:04:22 2009 - Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver, Realtek. Update this driver. Outdated network adapter drivers can and do cause problems.

Let's see if updating these two drivers solves your problem.