BSOD plague .. currently d1


  1. Posts : 5
    Windows 7 Home Premium 64bit
       #1

    BSOD plague .. currently d1


    This box has had BSOD since I got it in Feb 10.

    I had installed dozens of drivers/software within a few days and tried eliminating many.

    There is an extra Q: drive on MY COMPUTER that doesn't open.. and logs seem to point to virtualizaiton and something of an old WORKGROUP name (no idea what brought that to the system)

    Check temp, removed external drives... never changed anything inside the case. Extensive memory tests.

    Gut tells me it's something I did, but what?

    ZIP attached per instructions.

    Acer Aspire with Win 7 64
    OS 6.1.7600.2.0.0.768.3
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    50 memory dumps from 10 Aug to the present (approx 3 months).
    From a quick look at MSOINFO32 there may be something to do with a program from the Roland Corporation - the driver is named rdwm1046.sys ( Roland U.S. - Downloads & Updates )

    More to follow once all 50 dump files are finished running....
      My Computer


  3. Posts : 5,705
    Win7 x64 + x86
       #3

    About 9 different BSOD errors and about 10 different causes in these BSOD's. I'd have to suspect a hardware problem if the above post doesn't fix things.

    Do you have a USB attached musical device? Perhaps one that is hooked up to the network/internet?

    Because of the large proportion of IRQL related errors, I'd wonder if there was a compatibility issue or a driver issue that's related to the hardware.

    It is possible that the following older drivers may be causing your problems.
    Please either REMOVE or Update the older drivers listed below.
    HOW TO FIND DRIVERS:
    DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
    Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

    The most common drivers are located on this page: Driver Reference
    If you can't find the driver, post back and we'll see what we can find.

    Here's the older drivers that were found in the memory dump files:
    Code:
    
    wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
     - Western Digital SCSI Arcitecture Model (SAM) WDM driver
     - Driver Reference
    
    pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
     - low level access layer for CD devices (A part of many different CD/DVD burning   programs)
      - Driver Reference
     
    dfmirage.sys Fri Jan 11 16:04:26 2008 (4787D9DA)
     - Mirage Driver by DemoForge, LLC. 
      - Driver Reference
     
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 08:28:29.355 2010 (UTC - 5:00)
    System Uptime: 0 days 20:51:51.088
    BugCheck D1, {4b, 2, 0, fffff88003a47438}
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+874 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    Bugcheck code 000000D1
    Arguments 00000000`0000004b 00000000`00000002 00000000`00000000 fffff880`03a47438
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Nov 13 11:36:09.161 2010 (UTC - 5:00)
    System Uptime: 0 days 1:20:53.894
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`001478f9 fffff880`0df5a1c0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Nov 13 05:20:11.891 2010 (UTC - 5:00)
    System Uptime: 0 days 11:28:50.499
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`000c78f9 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Nov 12 17:50:53.694 2010 (UTC - 5:00)
    System Uptime: 0 days 8:50:44.426
    Probably caused by : memory_corruption ( nt!MmGetSessionId+1b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  robotaskbarico
    Bugcheck code 00000050
    Arguments fffff880`0af76008 00000000`00000000 fffff800`02e5374f 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Nov 12 06:01:48.578 2010 (UTC - 5:00)
    System Uptime: 1 days 19:37:33.311
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  chrome.exe
    Bugcheck code 00000050
    Arguments fffff800`03aef1d2 00000000`00000008 fffff800`03aef1d2 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Nov 10 04:21:42.049 2010 (UTC - 5:00)
    System Uptime: 2 days 18:26:44.237
    *** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
    *** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
    Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+58c3 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  SearchIndexer.
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff880`0121d8b0 fffff880`0e618ce0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov  7 00:38:17.633 2010 (UTC - 5:00)
    System Uptime: 1 days 15:25:10.366
    Probably caused by : memory_corruption ( nt!MiAllocatePoolPages+24 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  SearchIndexer.
    Bugcheck code 00000050
    Arguments ffffffff`8b48d0e5 00000000`00000001 fffff800`02fa4434 00000000`00000005
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov  4 20:20:44.524 2010 (UTC - 5:00)
    System Uptime: 0 days 15:32:26.241
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+59c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    Bugcheck code 00000050
    Arguments fffff880`449eb998 00000000`00000001 fffff800`02e7e2ac 00000000`00000005
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov  1 15:25:42.037 2010 (UTC - 5:00)
    System Uptime: 0 days 5:57:06.753
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`001678f9 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov  1 00:02:04.045 2010 (UTC - 5:00)
    System Uptime: 0 days 22:57:11.499
    Probably caused by : win32k.sys ( win32k!TimersProc+142 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  csrss.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`00192f1e fffff880`08e120d0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 29 20:28:17.015 2010 (UTC - 5:00)
    System Uptime: 1 days 10:30:17.607
    Probably caused by : win32k.sys ( win32k!IsMessageAllowedAcrossILByReceiver+3a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  OUTLOOK.EXE
    Bugcheck code 00000050
    Arguments fffff900`c40dcb80 00000000`00000000 fffff960`001f9f2a 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Oct 26 14:25:32.432 2010 (UTC - 5:00)
    System Uptime: 0 days 5:32:58.149
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Skype.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`000c78f9 fffff880`0cb8e1c0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Oct 26 06:57:21.364 2010 (UTC - 5:00)
    System Uptime: 0 days 11:26:02.065
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`001878f9 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 22 16:19:00.062 2010 (UTC - 5:00)
    System Uptime: 1 days 23:30:22.795
    Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  SearchProtocol
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff960`002e03d6 00000000`00000000 00000349`00000008
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 18 21:31:36.916 2010 (UTC - 5:00)
    System Uptime: 0 days 4:45:17.633
    Probably caused by : hardware ( nt!IopQueueThreadIrp+6c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  audiodg.exe
    Bugcheck code 0000003B
    Arguments 00000000`c000001d fffff800`02ea1bcc fffff880`0ee4efe0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 18 16:31:10.918 2010 (UTC - 5:00)
    System Uptime: 0 days 23:34:05.635
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+53ad3 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xBE
    PROCESS_NAME:  System
    Bugcheck code 000000BE
    Arguments fffff880`103c5f1b 80000001`37786121 fffff880`04c53200 00000000`0000000a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 05:25:00.457 2010 (UTC - 5:00)
    System Uptime: 0 days 4:20:52.999
    Probably caused by : hardware ( win32k!RawInputThread+8ef )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  csrss.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`0013388f fffff880`08d32120 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 16 02:30:45.633 2010 (UTC - 5:00)
    System Uptime: 0 days 5:46:19.350
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  googletalk.exe
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`001778f9 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 15 10:15:40.266 2010 (UTC - 5:00)
    System Uptime: 0 days 0:21:34.999
    Probably caused by : win32k.sys ( win32k!PFEOBJ::bFilteredOut+18 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  agent.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`000f866c fffff880`0b2aab30 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 15 02:07:08.148 2010 (UTC - 5:00)
    System Uptime: 0 days 2:25:57.880
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`001278f9 fffff880`0d364120 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 22:54:03.198 2010 (UTC - 5:00)
    System Uptime: 0 days 14:10:09.930
    Probably caused by : win32k.sys ( win32k!PostMessageExtended+6c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments fffff201`84e1b930 00000000`00000001 fffff960`00180c90 00000000`00000007
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 05:22:01.636 2010 (UTC - 5:00)
    System Uptime: 2 days 15:58:05.368
    Probably caused by : win32k.sys ( win32k!HMFreeObject+136 )
    BUGCHECK_STR:  0x19_20
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  skypePM.exe
    Bugcheck code 00000019
    Arguments 00000000`00000020 fffff900`c01f9660 fffff900`c01f9660 00000000`25000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct  4 20:24:05.334 2010 (UTC - 5:00)
    System Uptime: 0 days 0:32:10.066
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  sidebar.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`00177649 fffff880`0b716120 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct  4 08:22:37.370 2010 (UTC - 5:00)
    System Uptime: 0 days 9:21:29.103
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  sidebar.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`00137649 fffff880`0b059120 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct  1 03:28:34.060 2010 (UTC - 5:00)
    System Uptime: 0 days 18:05:58.792
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    Bugcheck code 0000000A
    Arguments 00000000`00000000 00000000`0000000d 00000000`00000001 fffff800`02e7ce20
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep 30 08:33:55.876 2010 (UTC - 5:00)
    System Uptime: 0 days 3:15:28.609
    Probably caused by : ndis.sys ( ndis!ndisOidRequestComplete+3fb )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Rainmeter.exe
    Bugcheck code 0000007F
    Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`01449f9b
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Sep 29 00:18:44.876 2010 (UTC - 5:00)
    System Uptime: 0 days 2:08:35.593
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  sidebar.exe
    Bugcheck code 00000050
    Arguments fffff960`0055de88 00000000`00000000 fffff960`001a7649 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Sep 28 20:49:14.444 2010 (UTC - 5:00)
    System Uptime: 0 days 5:57:16.161
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Pamela.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`00187649 fffff880`0c0921c0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Sep 28 14:50:08.092 2010 (UTC - 5:00)
    System Uptime: 3 days 0:02:03.257
    Probably caused by : win32k.sys ( win32k!HMFreeObject+136 )
    BUGCHECK_STR:  0x19_20
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  skypePM.exe
    Bugcheck code 00000019
    Arguments 00000000`00000020 fffff900`c06f2ee0 fffff900`c06f2ee0 00000000`25000006
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Sep 25 14:47:35.584 2010 (UTC - 5:00)
    System Uptime: 5 days 19:29:41.316
    Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  csrss.exe
    Bugcheck code 0000000A
    Arguments fffff880`08fa1b00 00000000`00000002 00000000`00000000 fffff800`02ef6c5d
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Sep 18 11:38:53.329 2010 (UTC - 5:00)
    System Uptime: 2 days 1:07:13.062
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`000b7649 fffff880`0c448120 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep 16 10:30:21.856 2010 (UTC - 5:00)
    System Uptime: 0 days 1:00:25.448
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  robotaskbarico
    Bugcheck code 00000050
    Arguments fffff900`c4143c68 00000000`00000000 fffff960`00147649 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep 16 09:29:11.095 2010 (UTC - 5:00)
    System Uptime: 0 days 0:42:19.812
    Probably caused by : win32k.sys ( win32k!xxxBroadcastMessage+57b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  iexplore.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`0300090d fffff880`0b55cdd0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Sep 16 01:12:21.306 2010 (UTC - 5:00)
    System Uptime: 0 days 3:09:02.023
    Probably caused by : ndis.sys ( ndis!ndisOidRequestComplete+3fb )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Rainmeter.exe
    Bugcheck code 0000007F
    Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`014c8f9b
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Sep 15 21:29:20.970 2010 (UTC - 5:00)
    System Uptime: 0 days 16:11:16.687
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments fffff900`c5d3b3f8 00000000`00000000 fffff960`000e7649 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Sep 14 22:04:35.045 2010 (UTC - 5:00)
    System Uptime: 0 days 4:51:36.762
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  explorer.exe
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`000c7649 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Sep 14 17:12:28.055 2010 (UTC - 5:00)
    System Uptime: 1 days 4:24:51.772
    Probably caused by : win32k.sys ( win32k!QueueMouseEvent+4e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  csrss.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`0019734a fffff880`09837c60 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 12:37:28.094 2010 (UTC - 5:00)
    System Uptime: 0 days 3:11:02.702
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  chrome.exe
    Bugcheck code 00000050
    Arguments fffff900`c57ca478 00000000`00000000 fffff960`00137649 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 06:02:03.317 2010 (UTC - 5:00)
    System Uptime: 0 days 1:32:29.050
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`00167649 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 13 00:38:49.572 2010 (UTC - 5:00)
    System Uptime: 0 days 3:04:17.289
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments fffff960`00d1e168 00000000`00000000 fffff960`00157649 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 12 21:00:24.374 2010 (UTC - 5:00)
    System Uptime: 0 days 7:20:42.091
    Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+e7 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  googletalk.exe
    Bugcheck code 00000050
    Arguments fffff880`0c7e8530 00000000`00000000 fffff800`03178d47 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 12 09:46:51.272 2010 (UTC - 5:00)
    System Uptime: 0 days 5:50:57.988
    Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+409b4 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xBE
    PROCESS_NAME:  spoolsv.exe
    Bugcheck code 000000BE
    Arguments 00000000`77344280 84400001`3516c025 fffff880`0c6af970 00000000`0000000a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Sep 11 10:52:40.689 2010 (UTC - 5:00)
    System Uptime: 10 days 22:37:30.405
    Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  firefox.exe
    Bugcheck code 0000000A
    Arguments 00000000`0000002f 00000000`00000002 00000000`00000000 fffff800`02e7ec89
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Aug 30 23:49:33.666 2010 (UTC - 5:00)
    System Uptime: 0 days 12:31:42.156
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  chrome.exe
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`00137649 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Aug 30 11:17:03.818 2010 (UTC - 5:00)
    System Uptime: 2 days 1:38:06.534
    Probably caused by : win32k.sys ( win32k!RFONTOBJ::vDeleteRFONT+3a4 )
    BUGCHECK_STR:  0xc2_7
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    Bugcheck code 000000C2
    Arguments 00000000`00000007 00000000`00001097 00000000`00000000 fffff900`c400b380
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Aug 27 20:54:46.422 2010 (UTC - 5:00)
    System Uptime: 0 days 2:50:31.139
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  explorer.exe
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`001a7649 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Aug 27 13:49:59.286 2010 (UTC - 5:00)
    System Uptime: 0 days 0:47:17.862
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  TweetFriendAdd
    Bugcheck code 00000050
    Arguments ffffffff`ffffffb8 00000000`00000000 fffff960`00197649 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Aug 27 11:57:15.100 2010 (UTC - 5:00)
    System Uptime: 1 days 0:53:37.832
    Probably caused by : win32k.sys ( win32k!TimersProc+73 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  csrss.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`000e2b9f fffff880`08c600d0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Aug 16 12:59:32.153 2010 (UTC - 5:00)
    System Uptime: 4 days 7:38:08.869
    Probably caused by : win32k.sys ( win32k!TimersProc+73 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  csrss.exe
    Bugcheck code 00000050
    Arguments fffff900`c400bb68 00000000`00000000 fffff960`001b2b9f 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Tue Aug 10 05:46:53.205 2010 (UTC - 5:00)
    System Uptime: 0 days 17:09:11.031
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1ee )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  explorer.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02dfe07a fffff880`0adbd2d0 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  4. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    ROLAND sounds right


    I do own a Roland USB Mixer that was one of the first things I suspected

    After the initial round of "what's wrong with my new setup?" early this year, I removed it and haven't had it attached since.

    I thought I had removed all traces of it.

    I will look again now.

    Is there a "how to make sure it's gone' checklist here for the places I should be checking?

    Could this be the reason I get a Q: drive that doesn't exist?
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    15 Feb 2010 - 1 BSOD due to rdwm1046.sys (the Roland driver)
    13 Sep 2010 - 2 BSOD's due to rdwm1046.sys (the Roland driver)
    There was evidence of this in MSINFO32 - but no evidence of this in the memory dump files.
    I suspect that it's not an issue here, but have included it because I cannot be sure.

    If it's still there, search your system for it.
    In particular, go to C:\WIndows\System32\drivers and look for rdwm1046.sys there. If you find it, rename it to rdwm1046.BAK Reboot and check to be sure it hasn't respawned itself.
    It may not be there as it was not loaded in the November memory dumps (and you removed the program previously).

    A small side discussion here:
    If program A writes to a memory address owned by program B, nothing may happen if the address isn't currently being used.
    Then program A can exit/close and there will be no trace of it on the memory stack.
    Then program B finally gets around to accessing that address and it finds garbage there (the data from program A).
    That causes program B to crash - and there's no evidence left as to what caused the crash.

    I have no idea about how the Roland stuff works, but I have seen things like the Q: drive caused by CD/DVD programs that allow you to run programs without the CD/DVD being in the drive. I'd blame Nero, VSO, or XVid

    Good Luck!
      My Computer


  6. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Traced the roland file to a folder in ProgramFiles and deleted it.. nothing in Windows System so it's gone.

    Updated firmware and drivers (SCSI) for the WD external storage drive.. it's another piece I thought had caused damage early on and I skipped using it for months. However, it worked fine on the Acer laptop I bought the same day so I hooked it up again.. and pretty sure it's not the culprit.. Updated anyway.

    Removed the other two you listed.. and uninstalled VSO XVID and NERO just to be sure.

    The Q: drive remains.. and just had another BSOD. Checked the logs, and as usual, the last two events before the BSOD were "virtualization" related.

    The sequence is

    Application Virtualization Client has an error.. within a minute there are other errors, then two more Application Virtualization Client error and it goes to BSOD. Here't he details from the last error:

    - System

    - Provider

    [ Name] Application Virtualization Client

    - EventID 6096

    [ Qualifiers] 16384

    Level 2

    Task 37

    Keywords 0x80000000000000

    - TimeCreated

    [ SystemTime] 2010-11-14T19:03:13.000000000Z

    EventRecordID 28092

    Channel Application

    Computer julia

    Security


    - EventData

    {tid=144C}
    false
    07B01F0C-0000004A
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #7

    I'm not real strong on virtualization. Could you please post the latest memory dump files?

    I'll probably ask you to run Driver Verifier according to these directions (so you can get a head start if you'd like):
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  8. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Stiill getting error


    No error today. I think Driver verifier running. It froze the machine on first reboot.

    How do I verify that it is running?

    Attaching more DMP files.

    Q: driver is gone.. removed the virtualization software which I don't see I ever needed
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    To see if it's running, launch Driver Verifier and select "Display Existing Settings"

    Running the last 9 memory dumps (14 Nov to the present)
    5 different BSOD error codes, with at least 4 different causes blamed
    This is most likely a hardware problem.

    First tho', please rename this older file from .sys to .BAK ( pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
    You'll most likely find it in the C:\Windows\System32\drivers folder.
    Renaming it may break one of your CD/DVD programs - but leave it that way until we're done troubleshooting.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov 18 22:38:31.319 2010 (UTC - 5:00)
    System Uptime: 0 days 3:25:24.036
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  Skype.exe
    Bugcheck code 00000050
    Arguments fffff900`c2d23898 00000000`00000000 fffff960`001a78f9 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov 18 04:56:07.486 2010 (UTC - 5:00)
    System Uptime: 0 days 16:20:05.078
    Probably caused by : hardware ( Npfs!NpFsdClose+114 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  AVGIDSAgent.ex
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff880`017bd490 fffff880`0ee5d040 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Nov 17 00:48:45.231 2010 (UTC - 5:00)
    System Uptime: 0 days 8:47:09.948
    Probably caused by : win32k.sys ( win32k!DereferenceClass+1f )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  robotaskbarico
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff960`001a03df 00000000`00000001 00000000`00000050
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Nov 16 01:37:34.197 2010 (UTC - 5:00)
    System Uptime: 0 days 4:42:00.929
    Probably caused by : memory_corruption ( nt!MmGetSessionId+1b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  robotaskbarico
    Bugcheck code 00000050
    Arguments fffff880`08f9f008 00000000`00000000 fffff800`02e8b74f 00000000`00000001
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov 15 20:55:00.960 2010 (UTC - 5:00)
    System Uptime: 0 days 11:11:17.693
    Probably caused by : win32k.sys ( win32k!MsgLookupTableCleanUp+4f )
    BUGCHECK_STR:  0x19_20
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  ME3x64.exe
    Bugcheck code 00000019
    Arguments 00000000`00000020 fffff900`c273c260 fffff900`c273cb40 00000000`258e0018
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 22:14:55.401 2010 (UTC - 5:00)
    System Uptime: 0 days 1:27:10.118
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  WindowsLiveWri
    Bugcheck code 00000050
    Arguments fffff900`c4393c68 00000000`00000000 fffff960`001778f9 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 20:13:43.210 2010 (UTC - 5:00)
    System Uptime: 0 days 1:13:51.927
    Probably caused by : win32k.sys ( win32k!HMFreeObject+136 )
    BUGCHECK_STR:  0x19_20
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  skypePM.exe
    Bugcheck code 00000019
    Arguments 00000000`00000020 fffff900`c31a6a20 fffff900`c31a6a20 00000000`25000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 14:13:22.615 2010 (UTC - 5:00)
    System Uptime: 0 days 0:12:02.332
    Probably caused by : win32k.sys ( win32k!FindTimer+59 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  driverscanner.
    Bugcheck code 00000050
    Arguments fffffffa`ffffffb7 00000000`00000000 fffff960`001878f9 00000000`00000005
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Nov 14 08:28:29.355 2010 (UTC - 5:00)
    System Uptime: 0 days 20:51:51.088
    BugCheck D1, {4b, 2, 0, fffff88003a47438}
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+874 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    Bugcheck code 000000D1
    Arguments 00000000`0000004b 00000000`00000002 00000000`00000000 fffff880`03a47438
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
    Also, update the program associated with this driver: (dfmirage.sys Fri Jan 11 16:04:26 2008 (4787D9DA)
    It is a part of the Mirage Driver by DemoForge, LLC. ( Driver Reference )
    If you can't determine the program, please rename it from .sys to .BAK - it'll be located in the C:\Windows\System32\drivers folder also.

    Also, please use this free program to stop the above drivers from loading: Autoruns for Windows

    To rule out compatibility issues, please check your hardware and software against the list here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads
    Then, please remove all non-essential hardware and swap out the essential hardware with known good stuff to attempt to isolate the problem component(s). Here's an article that I wrote a while back about this: Hardware Troubleshooting Via System Stripdown
      My Computer


  10. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    No BSOD for 3 days


    longest continuous run in recent memory.

    I do get 100% CPU going from something.. hope it's driver verifier, which I've shut down now.

    logs with suspicious "virtualization" calls are now clear.. but noticing some BONJOUR entries and a screwy DRM piece install with Corel products.

    Drivers last questions were updated previously.. but I removed just in case.

    Thanks for all the help.. tools will come in handy too.

    My guess right now is that the extra virtualization software and the Roland box driver were most of my problem.. but I did get some BSOD after that... until the phantom Q: drive disappeared.

    Will post if I see another BSOD this week
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 07:29.
Find Us