RANDOM and continous BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by citrix, Oct 2, 2010.

  1. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    my PC start have random blue screen, each time a different error code, different system file. it could happen anytime.

    I have checked memory with memtest, and windows memory test, no error found, I have checked all drivers, cleaned spyware.

    the problem still exist. I have to pray for my pc not to shut down.

    can anybody help ?~o)
     
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hey...

    Yeah, not a problem. We'll fix this up for ya.

    C:\Windows\Minidmup

    Copy the files in there to any other folder, zip them, then attach the zip to a post.

    We'll check 'em out.
     
  3. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    You say you have cleaned spyware,

    cmd -> sfc /scannow
    cmd -> chkdsk /r


    Attach the crash files, C:\Windows\Minidump -> .dmp's.
     
  4. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    I have done sfc scan, chkdsk. each time i do sfc, it says if found error and fixed, fix will happen at next restart.

    I uploaded the lastest minidump here. there are about 20 in last few days, I cleanup hard drive so they are erased. each time it happend at ntsf 05x000, ntskrnol,
     

    Attached Files:

  5. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    I would expect blue screens from your build:
    Windows 7 Kernel Version 7601 (Service Pack 1.178)


    100210-37393-01.dmp
    BugCheck 3B

    100210-37471-01.dmp
    BugCheck 19

    100110-40716-01.dmp
    BugCheck 3B

    093010-40872-01.dmp
    NTFS_FILE_SYSTEM (24)

    (http://hddscan.com/)


    These drivers need to be updated:

    lmimirr.sys Wed Apr 11 01:32:45 2007
    lmimirr2.dll Wed Apr 11 01:32:46 2007
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    https://secure.logmein.com/US/home.aspx

    000.fcl Fri Sep 26 16:11:22 2008
    Cyberlink
    Video editing software, Multimedia Software and Blu-ray playback software by CyberLink

    Rt64win7.sys Thu Feb 26 11:04:13 2009
    Realtek 8136/8168/8169
    Realtek

    AsUpIO.sys Mon Jul 06 05:21:38 2009
    Asus Probe/AsIO/some ASUS utility
    www.support.asus.com

    intelsmb.sys Wed May 13 10:31:00 2009
    Intel(R) SMBus Controller, System Management Bus 2.0
    http://downloadcenter.intel.com/


    Code:
    
    fffff800`00bbc000 fffff800`00bc6000   kdcom    kdcom.dll    Tue Jul 14 04:31:07 2009 (4A5BDFDB)
    fffff800`03415000 fffff800`039f6000   nt       ntoskrnl.exe Fri Jun 04 08:38:22 2010 (4C08914E)
    fffff800`039f6000 fffff800`03a3f000   hal      hal.dll      Fri Jun 04 11:19:14 2010 (4C08B702)
    fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  unavailable (00000000)
    fffff880`00c68000 fffff880`00cb2000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Fri Jun 04 11:21:05 2010 (4C08B771)
    fffff880`00cb2000 fffff880`00cc6000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
    fffff880`00cc6000 fffff880`00d24000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`00d24000 fffff880`00de4000   CI       CI.dll       Fri Jun 04 11:24:41 2010 (4C08B849)
    fffff880`00de4000 fffff880`00df8000   winhv    winhv.sys    Fri Jun 04 08:27:42 2010 (4C088ECE)
    fffff880`00e00000 fffff880`00e3c000   vmbus    vmbus.sys    Fri Jun 04 08:55:03 2010 (4C089537)
    fffff880`00e3c000 fffff880`00ee0000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
    fffff880`00ee0000 fffff880`00eef000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
    fffff880`00eef000 fffff880`00f46000   ACPI     ACPI.sys     Fri Jun 04 08:27:32 2010 (4C088EC4)
    fffff880`00f46000 fffff880`00f4f000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
    fffff880`00f4f000 fffff880`00f59000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
    fffff880`00f59000 fffff880`00f8c000   pci      pci.sys      Fri Jun 04 08:27:25 2010 (4C088EBD)
    fffff880`00f8c000 fffff880`00f99000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
    fffff880`00f99000 fffff880`00fae000   partmgr  partmgr.sys  Fri Jun 04 08:27:43 2010 (4C088ECF)
    fffff880`00fae000 fffff880`00fc3000   volmgr   volmgr.sys   Fri Jun 04 08:27:43 2010 (4C088ECF)
    fffff880`00fc3000 fffff880`00fca000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
    fffff880`00fca000 fffff880`00fda000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
    fffff880`00fda000 fffff880`00fdbe80   AiCharger AiCharger.sys Wed May 05 11:37:36 2010 (4BE12E50)
    fffff880`00fdc000 fffff880`00ff6000   mountmgr mountmgr.sys Fri Jun 04 08:27:35 2010 (4C088EC7)
    fffff880`00ff6000 fffff880`00fff000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`01000000 fffff880`0100b000   amdxata  amdxata.sys  Fri Mar 19 18:18:18 2010 (4BA3A3CA)
    fffff880`0100b000 fffff880`01057000   fltmgr   fltmgr.sys   Fri Jun 04 08:27:42 2010 (4C088ECE)
    fffff880`01057000 fffff880`0106b000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
    fffff880`0106b000 fffff880`010c9000   msrpc    msrpc.sys    Fri Jun 04 08:29:35 2010 (4C088F3F)
    fffff880`010c9000 fffff880`010f3000   ataport  ataport.SYS  Fri Jun 04 08:27:32 2010 (4C088EC4)
    fffff880`010f3000 fffff880`0113a000   mv61xx   mv61xx.sys   Thu Aug 06 06:20:12 2009 (4A7A4BEC)
    fffff880`0113a000 fffff880`01169000   SCSIPORT SCSIPORT.SYS Fri Jun 04 09:19:46 2010 (4C089B02)
    fffff880`01169000 fffff880`011f6000   mv91xx   mv91xx.sys   Wed Mar 17 09:53:06 2010 (4BA08A62)
    fffff880`011f6000 fffff880`011fe000   mvxxmm   mvxxmm.sys   Wed Mar 17 09:52:37 2010 (4BA08A45)
    fffff880`0120b000 fffff880`013ae000   Ntfs     Ntfs.sys     Fri Jun 04 08:29:35 2010 (4C088F3F)
    fffff880`013ae000 fffff880`013c9000   ksecdd   ksecdd.sys   Fri Jun 04 08:28:41 2010 (4C088F09)
    fffff880`0148d000 fffff880`0149e000   Npfs     Npfs.SYS     Tue Jul 14 02:19:48 2009 (4A5BC114)
    fffff880`0149e000 fffff880`014bc000   tdx      tdx.sys      Fri Jun 04 08:28:54 2010 (4C088F16)
    fffff880`014bc000 fffff880`014c9000   TDI      TDI.SYS      Fri Jun 04 08:28:52 2010 (4C088F14)
    fffff880`014e9000 fffff880`0155b000   cng      cng.sys      Fri Jun 04 09:03:47 2010 (4C089743)
    fffff880`0155b000 fffff880`0156c000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
    fffff880`0156c000 fffff880`01576000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
    fffff880`01576000 fffff880`015ff000   afd      afd.sys      Fri Jun 04 08:29:40 2010 (4C088F44)
    fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Fri Jun 04 08:29:52 2010 (4C088F50)
    fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Tue Jul 14 02:50:34 2009 (4A5BC84A)
    fffff880`0168b000 fffff880`0169b000   watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F)
    fffff880`0169b000 fffff880`016a4000   rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62)
    fffff880`016a4000 fffff880`016ad000   rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63)
    fffff880`016b2000 fffff880`017a3000   ndis     ndis.sys     Fri Jun 04 08:30:02 2010 (4C088F5A)
    fffff880`017a3000 fffff880`017cd000   cdrom    cdrom.sys    Fri Jun 04 08:27:37 2010 (4C088EC9)
    fffff880`017cd000 fffff880`017f2000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B)
    fffff880`017f2000 fffff880`017fd000   Msfs     Msfs.SYS     Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`01800000 fffff880`01809000   hwpolicy hwpolicy.sys Fri Jun 04 08:27:10 2010 (4C088EAE)
    fffff880`01809000 fffff880`01843000   fvevol   fvevol.sys   Fri Jun 04 08:30:00 2010 (4C088F58)
    fffff880`01843000 fffff880`01859000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`01859000 fffff880`01889000   CLASSPNP CLASSPNP.SYS Fri Jun 04 08:27:48 2010 (4C088ED4)
    fffff880`018a1000 fffff880`018a9000   dump_mvxxmm dump_mvxxmm.sys Wed Mar 17 09:52:37 2010 (4BA08A45)
    fffff880`018bc000 fffff880`018c5000   Null     Null.SYS     Tue Jul 14 02:19:37 2009 (4A5BC109)
    fffff880`018c5000 fffff880`018cc000   Beep     Beep.SYS     Tue Jul 14 03:00:13 2009 (4A5BCA8D)
    fffff880`018cc000 fffff880`018da000   vga      vga.sys      Tue Jul 14 02:38:47 2009 (4A5BC587)
    fffff880`018da000 fffff880`018e3000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:16:34 2009 (4A5BCE62)
    fffff880`018e3000 fffff880`01ae5000   tcpip    tcpip.sys    Fri Jun 04 08:32:23 2010 (4C088FE7)
    fffff880`01ae5000 fffff880`01b2f000   fwpkclnt fwpkclnt.sys Fri Jun 04 08:28:51 2010 (4C088F13)
    fffff880`01b2f000 fffff880`01b3f000   vmstorfl vmstorfl.sys Fri Jun 04 08:54:57 2010 (4C089531)
    fffff880`01b3f000 fffff880`01b8b000   volsnap  volsnap.sys  Fri Jun 04 08:27:56 2010 (4C088EDC)
    fffff880`01b8b000 fffff880`01b93000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
    fffff880`01b93000 fffff880`01bb0000   sbp2port sbp2port.sys Fri Jun 04 08:27:35 2010 (4C088EC7)
    fffff880`01bb0000 fffff880`01bea000   rdyboost rdyboost.sys Fri Jun 04 08:44:16 2010 (4C0892B0)
    fffff880`01bea000 fffff880`01bfc000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
    fffff880`04200000 fffff880`04256000   USBPORT  USBPORT.SYS  Fri Jun 04 09:26:45 2010 (4C089CA5)
    fffff880`04256000 fffff880`04257f00   USBD     USBD.SYS     Tue Jul 14 03:06:23 2009 (4A5BCBFF)
    fffff880`04258000 fffff880`04260000   ASACPI   ASACPI.sys   Thu Jul 16 06:31:29 2009 (4A5E9F11)
    fffff880`04260000 fffff880`0426c000   serenum  serenum.sys  Tue Jul 14 03:00:33 2009 (4A5BCAA1)
    fffff880`0426c000 fffff880`0427b000   kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116)
    fffff880`0427b000 fffff880`0427c480   swenum   swenum.sys   Tue Jul 14 03:00:18 2009 (4A5BCA92)
    fffff880`0427d000 fffff880`04371000   dxgkrnl  dxgkrnl.sys  Fri Jun 04 08:50:19 2010 (4C08941B)
    fffff880`04371000 fffff880`043b7000   dxgmms1  dxgmms1.sys  Tue Jul 14 02:38:32 2009 (4A5BC578)
    fffff880`043b7000 fffff880`043db000   HDAudBus HDAudBus.sys Fri Jun 04 09:26:21 2010 (4C089C8D)
    fffff880`043db000 fffff880`043ec000   HECIx64  HECIx64.sys  Thu Sep 17 22:54:16 2009 (4AB293E8)
    fffff880`043ec000 fffff880`043fd000   usbehci  usbehci.sys  Fri Jun 04 09:26:44 2010 (4C089CA4)
    fffff880`04400000 fffff880`0441b000   raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9)
    fffff880`0441b000 fffff880`0443c000   raspptp  raspptp.sys  Fri Jun 04 09:31:35 2010 (4C089DC7)
    fffff880`0443c000 fffff880`04456000   rassstp  rassstp.sys  Tue Jul 14 03:10:25 2009 (4A5BCCF1)
    fffff880`0445d000 fffff880`044a2000   netbt    netbt.sys    Fri Jun 04 08:28:58 2010 (4C088F1A)
    fffff880`044a2000 fffff880`044ab000   wfplwf   wfplwf.sys   Tue Jul 14 03:09:26 2009 (4A5BCCB6)
    fffff880`044ab000 fffff880`044d1000   pacer    pacer.sys    Fri Jun 04 09:30:42 2010 (4C089D92)
    fffff880`044d1000 fffff880`044e0000   netbios  netbios.sys  Tue Jul 14 03:09:26 2009 (4A5BCCB6)
    fffff880`044e0000 fffff880`044fd000   serial   serial.sys   Tue Jul 14 03:00:40 2009 (4A5BCAA8)
    fffff880`044fd000 fffff880`04518000   wanarp   wanarp.sys   Fri Jun 04 09:31:41 2010 (4C089DCD)
    fffff880`04518000 fffff880`0452c000   termdd   termdd.sys   Fri Jun 04 09:38:54 2010 (4C089F7E)
    fffff880`0452c000 fffff880`0457d000   rdbss    rdbss.sys    Fri Jun 04 08:32:06 2010 (4C088FD6)
    fffff880`0457d000 fffff880`04589000   nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E)
    fffff880`04589000 fffff880`04594000   mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE)
    fffff880`04594000 fffff880`045b2000   ISODrv64 ISODrv64.sys Fri Jan 29 05:39:02 2010 (4B625856)
    fffff880`045b2000 fffff880`045c1000   discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E)
    fffff880`045c1000 fffff880`045f0000   ndiswan  ndiswan.sys  Fri Jun 04 09:31:22 2010 (4C089DBA)
    fffff880`045f0000 fffff880`045ff000   mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116)
    fffff880`04600000 fffff880`04647000   atikmpag atikmpag.sys Wed Aug 04 04:15:45 2010 (4C58BF41)
    fffff880`04647000 fffff880`04685000   1394ohci 1394ohci.sys Fri Jun 04 09:27:25 2010 (4C089CCD)
    fffff880`04685000 fffff880`04694880   intelsmb intelsmb.sys Wed May 13 10:31:00 2009 (4A0A7734)
    fffff880`04695000 fffff880`046a5000   CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1)
    fffff880`046a5000 fffff880`046bb000   AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0)
    fffff880`046bb000 fffff880`046df000   rasl2tp  rasl2tp.sys  Fri Jun 04 09:31:20 2010 (4C089DB8)
    fffff880`046e9000 fffff880`0476c000   csc      csc.sys      Fri Jun 04 08:32:34 2010 (4C088FF2)
    fffff880`0476c000 fffff880`0478a000   dfsc     dfsc.sys     Fri Jun 04 08:31:39 2010 (4C088FBB)
    fffff880`0478a000 fffff880`0479b000   blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF)
    fffff880`0479b000 fffff880`047a1000   AsUpIO   AsUpIO.sys   Mon Jul 06 05:21:38 2009 (4A515FB2)
    fffff880`047a1000 fffff880`047a7000   AsIO     AsIO.sys     Thu Apr 22 14:18:03 2010 (4BD0306B)
    fffff880`047a7000 fffff880`047cd000   tunnel   tunnel.sys   Fri Jun 04 09:30:40 2010 (4C089D90)
    fffff880`047cd000 fffff880`047e3000   intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
    fffff880`047e3000 fffff880`047ef000   ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8)
    fffff880`047ef000 fffff880`047fa000   rdpbus   rdpbus.sys   Tue Jul 14 03:17:46 2009 (4A5BCEAA)
    fffff880`05600000 fffff880`05623000   mrxsmb20 mrxsmb20.sys Fri Jun 04 08:31:53 2010 (4C088FC9)
    fffff880`05623000 fffff880`0562d000   IOCBIOS  IOCBIOS.SYS  Thu Jul 09 20:47:22 2009 (4A562D2A)
    fffff880`0562d000 fffff880`05634000   RaInfo   RaInfo.sys   Fri Jan 04 20:57:14 2008 (477E818A)
    fffff880`05634000 fffff880`05647000   LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 19:26:56 2008 (487B7E50)
    fffff880`0567d000 fffff880`05745000   HTTP     HTTP.sys     Fri Jun 04 08:29:59 2010 (4C088F57)
    fffff880`05745000 fffff880`05763000   bowser   bowser.sys   Tue Jul 14 02:23:50 2009 (4A5BC206)
    fffff880`05763000 fffff880`0577b000   mpsdrv   mpsdrv.sys   Tue Jul 14 03:08:25 2009 (4A5BCC79)
    fffff880`0577b000 fffff880`057a8000   mrxsmb   mrxsmb.sys   Fri Jun 04 08:31:51 2010 (4C088FC7)
    fffff880`057a8000 fffff880`057f6000   mrxsmb10 mrxsmb10.sys Fri Jun 04 08:31:57 2010 (4C088FCD)
    fffff880`05800000 fffff880`05832000   Rt64win7 Rt64win7.sys Thu Feb 26 11:04:13 2009 (49A65B0D)
    fffff880`05832000 fffff880`05850000   i8042prt i8042prt.sys Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`05850000 fffff880`05859000   wmiacpi  wmiacpi.sys  Tue Jul 14 02:31:02 2009 (4A5BC3B6)
    fffff880`0585a000 fffff880`05fc8000   atikmdag atikmdag.sys Wed Aug 04 04:39:08 2010 (4C58C4BC)
    fffff880`05fc8000 fffff880`05ff8000   nusb3xhc nusb3xhc.sys Fri Jan 22 05:22:21 2010 (4B5919ED)
    fffff880`05ff8000 fffff880`05fff000   lmimirr  lmimirr.sys  Wed Apr 11 01:32:45 2007 (461C108D)
    fffff880`06015000 fffff880`06058000   ks       ks.sys       Fri Jun 04 09:18:53 2010 (4C089ACD)
    fffff880`06058000 fffff880`0606a000   umbus    umbus.sys    Fri Jun 04 09:27:11 2010 (4C089CBF)
    fffff880`0606a000 fffff880`060c4000   usbhub   usbhub.sys   Fri Jun 04 09:27:23 2010 (4C089CCB)
    fffff880`060c4000 fffff880`060dc000   nusb3hub nusb3hub.sys Fri Jan 22 05:22:18 2010 (4B5919EA)
    fffff880`060dc000 fffff880`060f1000   NDProxy  NDProxy.SYS  Fri Jun 04 09:31:10 2010 (4C089DAE)
    fffff880`060f1000 fffff880`0614d000   HdAudio  HdAudio.sys  Fri Jun 04 09:27:13 2010 (4C089CC1)
    fffff880`0614d000 fffff880`0618a000   portcls  portcls.sys  Tue Jul 14 03:06:27 2009 (4A5BCC03)
    fffff880`0618a000 fffff880`061ac000   drmk     drmk.sys     Tue Jul 14 04:01:25 2009 (4A5BD8E5)
    fffff880`061ac000 fffff880`061b1200   ksthunk  ksthunk.sys  Tue Jul 14 03:00:19 2009 (4A5BCA93)
    fffff880`06c00000 fffff880`06c19000   HIDCLASS HIDCLASS.SYS Fri Jun 04 09:26:35 2010 (4C089C9B)
    fffff880`06c19000 fffff880`06c21080   HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9)
    fffff880`06c22000 fffff880`06c2f000   mouhid   mouhid.sys   Tue Jul 14 03:00:20 2009 (4A5BCA94)
    fffff880`06c2f000 fffff880`06c3b000   Dxapi    Dxapi.sys    Tue Jul 14 02:38:28 2009 (4A5BC574)
    fffff880`06c3b000 fffff880`06c49000   monitor  monitor.sys  Tue Jul 14 02:38:52 2009 (4A5BC58C)
    fffff880`06c49000 fffff880`06c6c000   luafv    luafv.sys    Tue Jul 14 02:26:13 2009 (4A5BC295)
    fffff880`06c6c000 fffff880`06c8d000   WudfPf   WudfPf.sys   Fri Jun 04 09:25:40 2010 (4C089C64)
    fffff880`06c8d000 fffff880`06ca2000   lltdio   lltdio.sys   Tue Jul 14 03:08:50 2009 (4A5BCC92)
    fffff880`06ca2000 fffff880`06cba000   rspndr   rspndr.sys   Tue Jul 14 03:08:50 2009 (4A5BCC92)
    fffff880`06cc3000 fffff880`06f1ed80   RTKVHD64 RTKVHD64.sys Fri Sep 03 11:02:27 2010 (4C80AB93)
    fffff880`06f1f000 fffff880`06f2d000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
    fffff880`06f2d000 fffff880`06f37000   dump_diskdump dump_diskdump.sys Fri Jun 04 09:19:35 2010 (4C089AF7)
    fffff880`06f37000 fffff880`06fc4000   dump_mv91xx dump_mv91xx.sys Wed Mar 17 09:53:06 2010 (4BA08A62)
    fffff880`06fc4000 fffff880`06fd7000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
    fffff880`06fd7000 fffff880`06fe1000   usb8023x usb8023x.sys Tue Jul 14 03:09:50 2009 (4A5BCCCE)
    fffff880`06fe1000 fffff880`06ff0000   RNDISMPX RNDISMPX.SYS Tue Jul 14 03:09:47 2009 (4A5BCCCB)
    fffff880`06ff0000 fffff880`06ffe000   hidusb   hidusb.sys   Tue Jul 14 03:06:22 2009 (4A5BCBFE)
    fffff880`07800000 fffff880`0786b000   srv2     srv2.sys     Fri Jun 04 08:32:41 2010 (4C088FF9)
    fffff880`078a2000 fffff880`07948000   peauth   peauth.sys   Tue Jul 14 04:01:19 2009 (4A5BD8DF)
    fffff880`07948000 fffff880`07953000   secdrv   secdrv.SYS   Wed Sep 13 16:18:38 2006 (4508052E)
    fffff880`07953000 fffff880`07980000   srvnet   srvnet.sys   Fri Jun 04 08:32:24 2010 (4C088FE8)
    fffff880`07980000 fffff880`07992000   tcpipreg tcpipreg.sys Fri Jun 04 09:30:49 2010 (4C089D99)
    fffff880`07992000 fffff880`079bd000   000      000.fcl      Fri Sep 26 16:11:22 2008 (48DCDF7A)
    fffff880`07e1a000 fffff880`07eb2000   srv      srv.sys      Fri Jun 04 08:32:56 2010 (4C089008)
    fffff880`07f23000 fffff880`07f54000   WUDFRd   WUDFRd.sys   Fri Jun 04 09:26:14 2010 (4C089C86)
    fffff960`00060000 fffff960`00370000   win32k   win32k.sys   Fri Jun 04 08:52:18 2010 (4C089492)
    fffff960`00540000 fffff960`0054a000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff960`00710000 fffff960`00737000   cdd      cdd.dll      Tue Jul 14 04:25:40 2009 (4A5BDE94)
    fffff960`00890000 fffff960`0089c000   lmimirr_fffff96000890000 lmimirr.dll  Wed Apr 11 01:32:45 2007 (461C108D)
    fffff960`00b40000 fffff960`00b48000   lmimirr2 lmimirr2.dll Wed Apr 11 01:32:46 2007 (461C108E)
    
    
    
     
    #5 cybercore, Oct 2, 2010
    Last edited: Oct 2, 2010
  6. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    how can you tell the problem come from those ?
     
  7. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321

    All those drivers were released before Windows 7 final. Especially 2007 and 2008, as well as early 2009. I'd also check the hard disk with hdd scan.
     
  8. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    I personally would clean install 7 without SP 1 (until it's final build).
     
  9. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    so SP1 could cause blue screen ? what exactly in SP1 could cause blue screen, and do you recommend I unstall it, would that fix this? how?

    and how did you find those dates? I recently did a clean install of windows 7 then put SP1 on top of it. then reinstalled those applications without clean old files, maybe that why the dates are old. could it be?
     
  10. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    SP1 is fine as I run it here on 3 machines very well.

    Pleas update those drivers shown. The Cyberlink one is fine and latest.

    Uninstall LogMeIn completely.
     
  11. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Correction to my previous post. You don't have LogMeIn, you have RemotelyAnywhere:

    RaInfo RaInfo.sys Fri Jan 04 13:57:14 2008

    Software must be uninstalled.
     
  12. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    yes I do have logmein, with latest software. so logmein is not good?

    I have just updated ATI software, Asus software, all latest available. I could not find latest intel software, reaktek should be latest.
     
  13. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Correct, LogMeIn crashes Win7. It's too old with outdated, incompatible drivers.
     
  14. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    I used latest logmein software. so you mean I should not use logmein? can you recommend a alternative free program to replace it?
     
  15. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    I was clear with my previous post. No, I don't know what else you can use.
     
  16. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    blue screen again, logmein completely uninstalled, cyberlink software uninstalled.
     

    Attached Files:

  17. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Did bsod's occur before SP 1 was installed?




    Attach more BSOD's, this one shows only this - your build is beta and is not read correctly:

    Code:
    BugCheck 3B, {c0000005, fffff80003495f70, fffff88009ba7110, 0}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+7cf70 )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80003495f70, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88009ba7110, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    
    
     
  18. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    I had about 15-20 minidump during last week, those were erase during disk cleanup. the ones attached are from last 2 days.

    blue screen occured before SP1 installed, and did not happen this often at first few day after SP1 installed, it just get more requrently lately. i could not find a reason for this.

    is it possible that memory module hace problem even memtest did not find error?
     
  19. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Update this NEC USB 3.0 driver from motherboard manufacturer's site for your board:

    nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010

    ---------

    Uninstall this driver and/or related software:

    ISODrv64 ISODrv64.sys Thu Jan 28 22:39:02 2010

    ----------

    Yes, ,RAM can still be defective after long testing. Suggest to test one module at a time while others removed.
     
  20. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    new blue screen today.

    what could be the problem?
     

    Attached Files:

Share This Page

Loading...