BSOD's

yellowpc · Jul 3, 2010

i'm not understanding contents all the posts here but i do get BSOD every now and then (error seems to vary but the latest one is this one per the post). i reinstalled my win7 quite a few times in the past but after a month or so BSOD came back. i also tried rolling back to certain restore points and it again only worked for a while.
pls see the attached dump files and the msinfo32 file and let me know how this can be fixed? appreciate it.

CarlTR6 · Jul 3, 2010

Hi yellowpc, I will look at these. It will take a few minutes as there are seven dumps. I'll be back shortly.

While I am reviewing the dumps, I recommend that you runs chkdsk and check you hard drive.

CHKDSK /R /F:

[FONT=&quot]
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP). [/FONT][FONT=&quot]
Copy/paste the results into your next post.[/FONT]

I am also going to ask the moderators to move your post and this post into a new thread so that we don't get confused working with two different situations.

[FONT=&quot] [/FONT]

CarlTR6 · Jul 3, 2010

I looked at you six most recent dumps. Four of them reported stop error F4 and two reported stop error 7A

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

Usual causes: Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

These errors point to a hardware problem. Three of the dumps pointed to your hard drive as the cause and a fourt indicated a hard drive problem.

Three of the dump files are included below.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump.zip\dump\070310-20358-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Sat Jul  3 19:11:19.445 2010 (GMT-4)
System Uptime: 0 days 8:37:10.006
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800752cb30, fffffa800752ce10, fffff80002f97540}

Probably caused by : hardware_disk

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800752cb30, Terminating object
Arg3: fffffa800752ce10, Process image file name
Arg4: fffff80002f97540, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800752cb30

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff880026eab78 -- (.exr 0xfffff880026eab78)
ExceptionAddress: 00000000773151df
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000007fefd27d8a8
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefd27d8a8, due to I/O error 00000000c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000007fefd27d8a8

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR:  0xc0000006_c000000e

FAULTING_IP: 
+23a
00000000`773151df ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000000E

FOLLOWUP_IP: 
+5de4952f01fcdb64
000007fe`fd27d8a8 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

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

0: kd> lmtsmn
start             end                 module name
fffff880`03f0e000 fffff880`03f4c000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00fa3000 fffff880`00ffa000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c76000 fffff880`02d00000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`041d4000 fffff880`041ea000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00dd8000 fffff880`00de3000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`058b2000 fffff880`058bd000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e20000 fffff880`00e29000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00c76000 fffff880`00ca0000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`00910000 fffff960`00971000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`019d8000 fffff880`019df000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03eba000 fffff880`03ecb000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`022c8000 fffff880`022e6000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006c0000 fffff960`006e7000   cdd      cdd.dll      unavailable (00000000)
fffff880`01978000 fffff880`019a2000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e30000 fffff880`00ef0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01910000 fffff880`01940000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d02000 fffff880`00d60000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010ce000 fffff880`01141000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`040cb000 fffff880`040db000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`011d8000 fffff880`011e6000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03e19000 fffff880`03e9c000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`053f1000 fffff880`053fd000   dc3d     dc3d.sys     Tue Nov 03 21:55:41 2009 (4AF0ED2D)
fffff880`03e9c000 fffff880`03eba000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02db2000 fffff880`02dc1000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`018fa000 fffff880`01910000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`045b9000 fffff880`045db000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`01236000 fffff880`01242000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00de3000 fffff880`00df6000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`011e6000 fffff880`011f1000   dump_msahci dump_msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`044a7000 fffff880`044b3000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`040e0000 fffff880`041d4000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04000000 fffff880`04046000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04046000 fffff880`0408d000   e1k62x64 e1k62x64.sys Wed Sep 23 20:11:00 2009 (4ABAB914)
fffff880`022f2000 fffff880`02328000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`0105c000 fffff880`01070000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01010000 fffff880`0105c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01211000 fffff880`0121b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`018c0000 fffff880`018fa000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`02dc1000 fffff880`02dde380   GemCCID  GemCCID.sys  Mon Aug 10 08:07:39 2009 (4A800D8B)
fffff800`031f7000 fffff800`03240000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0409e000 fffff880`040c2000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04400000 fffff880`0445c000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`04473000 fffff880`0448c000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`0445c000 fffff880`04464080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04465000 fffff880`04473000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`02200000 fffff880`022c8000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015f3000 fffff880`015fc000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04822000 fffff880`04f9cce0   igdkmd64 igdkmd64.sys Wed Feb 10 19:56:24 2010 (4B7355B8)
fffff880`03ef8000 fffff880`03f0e000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`03fda000 fffff880`03fe9000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`03e00000 fffff880`03e0e000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb4000 fffff800`00bbe000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`044b8000 fffff880`044fb000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013e6000 fffff880`01400000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015ae000 fffff880`015d9000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`053eb000 fffff880`053f0200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`0236c000 fffff880`02381000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`02328000 fffff880`0234b000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00caa000 fffff880`00cee000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`019ed000 fffff880`019fb000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`03fe9000 fffff880`03ff8000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0448c000 fffff880`04499000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c5c000 fffff880`00c76000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`019a2000 fffff880`019cf000   MpFilter MpFilter.sys Thu Oct 01 22:36:31 2009 (4AC5672F)
fffff880`05831000 fffff880`05841000   MpNWMon  MpNWMon.sys  Thu Oct 01 22:36:22 2009 (4AC56726)
fffff880`02399000 fffff880`023b1000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`023b1000 fffff880`023de000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`03a68000 fffff880`03ab6000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`03ab6000 fffff880`03ad9000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00dbd000 fffff880`00dc8000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`01850000 fffff880`0185b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e09000 fffff880`00e13000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01070000 fffff880`010ce000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02c5d000 fffff880`02c68000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015e1000 fffff880`015f3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0145c000 fffff880`0154e000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`041ea000 fffff880`041f6000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`03f70000 fffff880`03f9f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04567000 fffff880`0457c000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d74000 fffff880`02d83000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d00000 fffff880`02d45000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0154e000 fffff880`015ae000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0185b000 fffff880`0186c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c1b000 fffff800`031f7000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01243000 fffff880`013e6000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`03e0e000 fffff880`03e17000   NuidFltr NuidFltr.sys Fri May 08 04:53:31 2009 (4A03F30B)
fffff880`019cf000 fffff880`019d8000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02c68000 fffff880`02c75000   nx6000   nx6000.sys   Wed Jan 27 18:36:09 2010 (4B60CDE9)
fffff880`02d4e000 fffff880`02d74000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00d93000 fffff880`00da8000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d60000 fffff880`00d93000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00dc8000 fffff880`00dd8000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01200000 fffff880`01211000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`03ad9000 fffff880`03b7f000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04499000 fffff880`044a7000   point64k point64k.sys Tue Nov 03 21:55:38 2009 (4AF0ED2A)
fffff880`0457c000 fffff880`045b9000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cee000 fffff880`00d02000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`03f4c000 fffff880`03f70000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04800000 fffff880`0481b000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`03f9f000 fffff880`03fc0000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`03fc0000 fffff880`03fda000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04ff3000 fffff880`04ffe000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`01835000 fffff880`0183e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03ef1000 fffff880`03ef8000   rdpdispm rdpdispm.sys Fri Mar 21 01:06:22 2008 (47E3424E)
fffff880`0183e000 fffff880`01847000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01847000 fffff880`01850000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0118d000 fffff880`011c7000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02381000 fffff880`02399000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05205000 fffff880`053ea400   RTKVHD64 RTKVHD64.sys Wed Sep 02 06:12:56 2009 (4A9E4528)
fffff880`02deb000 fffff880`02df9000   scfilter scfilter.sys Mon Jul 13 19:50:17 2009 (4A5BC839)
fffff880`03b7f000 fffff880`03b8a000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`02ddf000 fffff880`02deb000   SMCLIB   SMCLIB.SYS   Mon Jul 13 20:00:35 2009 (4A5BCAA3)
fffff880`015d9000 fffff880`015e1000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`05841000 fffff880`058b2000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`05962000 fffff880`059fa000   srv      srv.sys      Tue Dec 08 03:32:55 2009 (4B1E0F37)
fffff880`058f9000 fffff880`05962000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`03b8a000 fffff880`03bb7000   srvnet   srvnet.sys   Tue Dec 08 03:32:26 2009 (4B1E0F1A)
fffff880`041f6000 fffff880`041f7480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`03bb7000 fffff880`03bc9000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0188a000 fffff880`01897000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0186c000 fffff880`0188a000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02d9e000 fffff880`02db2000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00540000 fffff960`0054a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03ecb000 fffff880`03ef1000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`044fb000 fffff880`0450d000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`0121b000 fffff880`01235c00   usbaudio usbaudio.sys Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`045db000 fffff880`045f8000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`053fd000 fffff880`053fef00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0408d000 fffff880`0409e000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0450d000 fffff880`04567000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04f9d000 fffff880`04ff3000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`018b2000 fffff880`018be000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`011c7000 fffff880`011d8000   usbscan  usbscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`01897000 fffff880`018b2000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`01940000 fffff880`0196d100   usbvideo usbvideo.sys Mon Jul 13 20:07:00 2009 (4A5BCC24)
fffff880`00e13000 fffff880`00e20000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019df000 fffff880`019ed000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01800000 fffff880`01825000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0144a000 fffff880`0145a000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00da8000 fffff880`00dbd000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01141000 fffff880`0118d000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d83000 fffff880`02d9e000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01825000 fffff880`01835000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ef0000 fffff880`00f94000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f94000 fffff880`00fa3000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d45000 fffff880`02d4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00010000 fffff960`0031f000   win32k   win32k.sys   unavailable (00000000)
fffff880`040c2000 fffff880`040cb000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00e00000 fffff880`00e09000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0234b000 fffff880`0236c000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`05800000 fffff880`05831000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`058bd000 fffff880`058c9000   hiber_pciide
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058c9000 fffff880`058d4000   hiber_msahci
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058d4000 fffff880`058e7000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058e7000 fffff880`058f3000   hiber_pciide
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`05841000 fffff880`0584c000   hiber_msahci
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0584c000 fffff880`0585f000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058bd000 fffff880`058c9000   hiber_pciide
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058c9000 fffff880`058d4000   hiber_msahci
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`058d4000 fffff880`058e7000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`05841000 fffff880`058b2000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01940000 fffff880`0194e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0194e000 fffff880`0195a000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0195a000 fffff880`01965000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01965000 fffff880`01978000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
------------------------------------------------------


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump.zip\dump\062810-33368-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Mon Jun 28 03:54:52.880 2010 (GMT-4)
System Uptime: 0 days 10:26:04.163
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8007ba0078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c620 )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8007ba0078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002cb22dc to fffff80002c7a600

STACK_TEXT:  
fffff880`03308828 fffff800`02cb22dc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`07ba0078 : nt!KeBugCheckEx
fffff880`03308830 fffff800`02c64507 : fffffa80`07ba0010 00000000`c000009d 00000000`00000000 fffffa80`07ba00a8 : nt! ?? ::FNODOBFM::`string'+0x4c620
fffff880`033088f0 fffff800`02c56fcf : fffffa80`05510530 fffffa80`05510580 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03308920 fffff800`02c8195d : fffffa80`05510530 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033089a0 fffff800`02c7dc4b : 00000103`0757fd01 00000000`00000000 fffffa80`00000000 fffff880`03308a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a30 fffff800`02c14a8f : fffffa80`00000002 fffff880`03308d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03308ce0 fffff800`02f1fa86 : fffffa80`05510530 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`02c58b06 : fffff880`009e7180 fffffa80`05510530 fffff880`009f1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c620
fffff800`02cb22dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c620

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c620

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c620

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump.zip\dump\062210-25599-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50
Debug session time: Tue Jun 22 17:12:37.278 2010 (GMT-4)
System Uptime: 0 days 21:35:52.823
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80075ec060, fffffa80075ec340, fffff80002f9a540}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80075ec060, Terminating object
Arg3: fffffa80075ec340, Process image file name
Arg4: fffff80002f9a540, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80075ec060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff88002050b78 -- (.exr 0xfffff88002050b78)
ExceptionAddress: 00000000775d5785
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000b80ff8
Attempt to write to address 0000000000b80ff8

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000b80ff8

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec60e0
 0000000000b80ff8 

FOLLOWUP_IP: 
+5de4952f00dcddc4
00000000`775d5785 ??              ???

FAULTING_IP: 
+5de4952f00dcddc4
00000000`775d5785 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+5de4952f00dcddc4
00000000`775d5785 ??              ???

BUGCHECK_STR:  0xF4_C0000005

STACK_TEXT:  
fffff880`020500f8 fffff800`0301ac72 : 00000000`000000f4 00000000`00000003 fffffa80`075ec060 fffffa80`075ec340 : nt!KeBugCheckEx
fffff880`02050100 fffff800`02fc80a3 : ffffffff`ffffffff fffffa80`07672060 fffffa80`075ec060 fffffa80`075ec060 : nt!PspCatchCriticalBreak+0x92
fffff880`02050140 fffff800`02f4c69c : ffffffff`ffffffff 00000000`00000001 fffffa80`075ec060 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17936
fffff880`02050190 fffff800`02c8d853 : fffffa80`075ec060 fffff800`c0000005 ffffe434`ea82a28c fffffa80`07672060 : nt!NtTerminateProcess+0x20c
fffff880`02050210 fffff800`02c89df0 : fffff800`02cc8cac fffff880`02050b78 fffff880`020508e0 fffff880`02050c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`020503a8 fffff800`02cc8cac : fffff880`02050b78 fffff880`020508e0 fffff880`02050c20 00000000`00b822a0 : nt!KiServiceLinkage
fffff880`020503b0 fffff800`02c8dc42 : fffff880`02050b78 00000000`000116e4 fffff880`02050c20 00000000`00b81d78 : nt!KiDispatchException+0x53b
fffff880`02050a40 fffff800`02c8c7ba : 00000000`00000001 00000000`000116e4 00000000`00000001 00000000`776dde28 : nt!KiExceptionDispatch+0xc2
fffff880`02050c20 00000000`775d5785 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00b81000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775d5785


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump.zip\dump\062010-19453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02e9fe50
Debug session time: Sun Jun 20 22:03:56.683 2010 (GMT-4)
System Uptime: 1 days 22:12:49.228
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8006ef6078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c620 )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8006ef6078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002d0a2dc to fffff80002cd2600

STACK_TEXT:  
fffff880`03308828 fffff800`02d0a2dc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`06ef6078 : nt!KeBugCheckEx
fffff880`03308830 fffff800`02cbc507 : fffffa80`06ef6010 00000000`c000009d 00000000`00000000 fffffa80`06ef60a8 : nt! ?? ::FNODOBFM::`string'+0x4c620
fffff880`033088f0 fffff800`02caefcf : fffffa80`05510530 fffffa80`05510580 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03308920 fffff800`02cd995d : fffffa80`05510530 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033089a0 fffff800`02cd5c4b : 00000103`06eb9f01 00000000`00000000 fffffa80`00000000 fffff880`03308a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a30 fffff800`02c6ca8f : fffffa80`00000002 fffff880`03308d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03308ce0 fffff800`02f77a86 : fffffa80`05510530 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`02cb0b06 : fffff880`009e7180 fffffa80`05510530 fffff880`009f1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c620
fffff800`02d0a2dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c620

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c620

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c620

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

I have already suggested chkdsk and I hope you have run that. I also suggest that you go to the website of you hard drive manufacturer and download the their diagnostic tool.

Please report your results.

I also found the following obsolete drivers on your system. Windows 7 does not like obsolete drivers and they can cause instability of your system.

amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
NuidFltr.sys Fri May 08 04:53:31 2009 (4A03F30B)
rdpdispm.sys Fri Mar 21 01:06:22 2008 (47E3424E)

I recommend that you update these drivers.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

yellowpc · Jul 3, 2010

Thank you CarlTR6. Just ran the chkdsk and I got a blank screen saying volume is clean. I'm looking at the application entries for today and there are several winlogon but no wininit. I'm on Windows 7.The last 2 winlogon I see are:

The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
Windows license validated.

Is this what you need?
I'll go through the rest you mentioned next.

CarlTR6 · Jul 3, 2010

Did you run chkdisk from an elevated command prompt? If so, that is good to go. Go to the manufacture's site of your hard drive, download and run their diagnostic tool. Let's make sure your hard drive is OK. Since so many of the dumps point to hard drive error, we have to thoroughly check it.

After that you need to update your drivers. Do not use Windows Update nor Device Manager for this. Let us know if you need assistance in finding these drivers.

yellowpc · Jul 3, 2010

i'm getting a bit nervous due to the lack of knowledge, pls bear w/ me. i started with amdxata.sys where search results are pointing me to an "AMD storage filter driver" which i've no idea what it is. a search of this file or the term 'storage filter driver' on amd site returns nothing. and looking at my machine - Gateway Official Site: Shop - Desktops - SX2840 01 Desktop Product Details things are pretty much intel... any chance this is any external device?
(btw, i'm not very familiar with how to appropriate post replies to thread, if i did anything wrong, please advise)

yellowpc · Jul 3, 2010

i missed your post regarding diagnostic tool and i'm looking for it now. should my hard drive model be listed under device manager / disk drives? i'm looking at something called WDC WD10EADS-00M2B0 ATA device assuming this is the one. i'll do some searches on drivers/diagnostic tool and report back. if i'm not on the right track, pls let me know. thanks!

CarlTR6 · Jul 4, 2010

Yellowpc, don't feel bad; I haven't been able to find any more on this driver than you have. I will ask some of the real experts and see if they can shed some light on it. It is interesting this driver has suddenly be popping up over the last few days.

Ignore it for now and start with the rdpdispm.sys driver. That one is the most obsolete. It is a Microsoft driver. Rdpbus.sys is a Microsoft RDP Bus Device driver from Microsoft Corporation belonging to product Microsoft® Windows® Operating System.

NuidFltr.sys is a Filter Driver for Microsoft Hardware HID Non-User Input Data belongs to the software Microsoft IntelliType Pro / IntelliPoint by Microsoft Corporation (www.microsoft.com). See if you can update the software through Microsoft.

These older Microsoft drivers prompt me to ask you if you did a clean install of Win 7, formatting your hard drive first, or did you do an upgrade install from Vista?

CarlTR6 · Jul 4, 2010

yellowpc said:
i missed your post regarding diagnostic tool and i'm looking for it now. should my hard drive model be listed under device manager / disk drives? i'm looking at something called WDC WD10EADS-00M2B0 ATA device assuming this is the one. i'll do some searches on drivers/diagnostic tool and report back. if i'm not on the right track, pls let me know. thanks!

You are on the right track. You have a western Digital hard drive. Go to the WD site and look for the diagnostic tool for your model.

I am about to sign off for the night; but post back. Others on the BSOD team will likely step in and offer suggestions and help. Feel free to ask any questions; the only stupid questions is the one not asked.

See you tomorrow. Good luck.

reventon · Jul 4, 2010

Hi,

The hard drive diagnostics for your drive can be found here: WD Support > Downloads > SATA & SAS > WD Caviar Green / GP (it is called Data Lifeguard Diagnostics)

yellowpc · Jul 4, 2010

Thanks.

*sigh* I'm still unable to find the exact model from WD site for their WDC WD10EADS-00M2B0 ATA device (triple check the code), so no driver or diagnostic tool yet.

So what do I do with the rdpbus.sys file?
IntelliType Pro - this is likely my keyboard and mouse, I'll see if I can update.

I have a clean install of Win 7 and had ignored the gateway OEM one. I did clean install a fair number of times as I did get some blue screen very soon after I installed. For a time it was probably related to Update - Restart Issues After Installing MS10-015 and the Alureon Rootkit - The Microsoft Security Response Center (MSRC) - Site Home - TechNet Blogs and later I went through the pain of installing 1 windows update at time, or just a handful to see if any update messes things up. By then the blue screen from that problem could easily be reproducible by setting machine to sleep after 1 minute, because it went blue screen right after each sleep (incident around feb-mar).

Later system became stable until sometime last month. This time the blue screen is unpredictable and is unrelated to sleep.

I'm not sure if this relates or if it is too much information. I'll post again after I check on the intellipoint update.

yellowpc · Jul 4, 2010

many thanks reventon! i'll run the extended test and return w/ results.

yellowpc · Jul 4, 2010

test passed:

Test Option: EXTENDED TEST
Model Number: WDC WD10EADS-00M2B0
Unit Serial Number: WD-WMAV50412378
Firmware Number: 01.00A01
Capacity: 1000.20 GB
SMART Status: PASS
Test Result: PASS
Test Time: 01:23:29, July 04, 2010

i also installed intellipro again for my keyboard and mouse. now how do i confirm that those sys files were now updated?

i believe i didn't have the keyboard drive installed in the past but now i did. a potential concern is that Microsoft uses same software for all of their keyboard and mouse and by installing that software it seems to update 1 of my mouse only and not both. note that 1 mouse isn't being used (it comes in a set with the keyboard). see attached. 2 of them have a drive date of 11/3/09, where as the HID one don't get updated. not sure if that matters.

on the other hand, there is a warning under PCI which i don't know what component it is and whether i should fix it in order to resolve the bigger problem.

appreciated all the help indeed!

CarlTR6 · Jul 4, 2010

Thanks, reventon.

yellowpc, it looks like you successfully updated your MS keyboard and mouse drivers. Anything dated July 13, 2009 and later should be fine. I suggest that you uninstall that HID mouse driver. That is an extremely old driver. Use your other mouse while we are troubleshooting. Try going to the mouse manufacturer's website and see if there is a newer driver. You can also simply get a new mouse. If you do so, make sure to uninstall the HID mouse

After you have uninstalled the HID mouse or updated, reboot and run your system. Let's see what happens.

Yes, the PCI Communications Controller can be a problem. Post the properties of that (right click on it and select Properties).

It looks as though you HD is OK; that is a good thing.

yellowpc · Jul 4, 2010

status on mouse drivers & PCI properties

happy 4th CarlTR6!

i think i uninstall the wrong mouse but will fix it soon. the HID one is actually the one that goes with the keyboard set but unforunately don't have a driver for win 7. attached reference. i believe since it comes in a set (using the same infrared transmitter), after i uninstall, it came back automatically. let me try again to make sure.

i'm attaching the PCI properties for your reference.

btw, i know why i had the amd driver, it was another video i tried installing at one point. how do i get rid of this driver? simply delete?

fyi - something screwy did happen after a reboot. one display seems to have rolled back or something. i'll have to check this driver also.

thanks thanks thanks.

yellowpc · Jul 4, 2010

verified. the HID compliant mouse will automatically come back up after reboot after an uninstall. should i simply - disable it?

yellowpc · Jul 4, 2010

fyi. pls ignore the video problem i branched out into earlier. already fixed.

CarlTR6 · Jul 4, 2010

happy 4th CarlTR6!

Thank you very much and right back to you.

think i uninstall the wrong mouse but will fix it soon. the HID one is actually the one that goes with the keyboard set but unforunately don't have a driver for win 7. attached reference. i believe since it comes in a set (using the same infrared transmitter), after i uninstall, it came back automatically. let me try again to make sure.

As long as the mouse is installed, it will find the driver and load it. Disable that mouse in Device Manager. Then navigate to c:\windows\system32\drivers and see if the driver is still there. If it is, rename it from XXXX.sys to XXXX.bak. That way you can always activate it again easily.

You can try this same approach for the amd driver. Rename it to .bak. If you find something is not working, you can go back and rename it to .sys and reboot.

The PCI Simple Communications Controller is disabled because there is not driver installed. From what I found on this device, I think it pertains to dialup modems. I suggest if you don't have a dialup modem, don't worry about it. I suspect that is why it is disabled; Win 7 did not find a dialup modem on your system. Since it is disabled, I doubt it is causing any system problems. Someone better versed in this area may come along and correct me. If I am am off base here, I hope they do.

After doing the disabling and renaming, reboot and let's see how your system does.

reventon · Jul 4, 2010

I do not believe the HID device is an issue, especially as it is an OS driver. Attached is a screenshot of my stable system.

The second screenshot shows where you can find the Hardware ID of the unknown PCI device - upload a screenshot of the same window of the PCI device if possible.

yellowpc · Jul 4, 2010

PCI simple communications controller properties

reventon - here it is

BSOD's

New member

My Computer

Antique Senior Member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Antique Senior Member

My Computer

BSOD Squad

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

BSOD Squad

My Computer

New member

My Computer