Persistent BSOD's at desktop


  1. Posts : 2
    Windows 7 Home Premium 64
       #1

    Persistent BSOD's at desktop


    Is Windows 7 . . .
    - Windows 7 Home Premium 64 Bit
    - It is a Windows 7 upgrade. I upgraded from XP, thus its a fresh Windows 7 install because you have to format your drive in order to install Windows 7 over windows XP.
    - Its my own copy of Windows 7 because I built the PC myself.

    - Was built last year.
    - I've always had problems with the ASUS 5870 drivers. I've been able to fix some symptoms like artifacts at desktop, but there still seems to be some underlying problems here. Its been suggested that I flash the 5870 BIOS to something else and that might fix it, but I'll reserve final judgement until you guys generously take a peek at these dumps.

    All of these DMPs are from a fresh windows install, literally installed it 1/9/11 after I felt I wanted to re-optimize my SSD.

    The ASUS 5870 has a power saving feature that has variable clock speeds and voltages depending on the activity on the GPU. Its a known problem that on some 5870 cards that there are problems with the idle clocks going to low for the system to handle it. Symptoms are usually just artifacting at desktop, this is fixable with modifying a Profile's clock settings and voltages and those symptoms are not cropping up.

    All of my crashes happen at desktop or if a game is windowed, I can't recall ever crashing while at full screen gaming.

    Crashing typically happen during installing something, either programs or windows updates or just at random, like if I mouse over a video and right as the drop down information begins to appear, the computer will crash. Crashes also happen quite frequently with this latest install when bringing the computer back from sleep mode or when the screen greys out when asking for administrative abilities to open a program. They are all locale 1033.



    Also, Slightly related to all of this... Recently I took out some parts to my computer to dust them (don't worry, these BSOD's were happening before I did this, so I don't think I messed anything up here) and then when I put them back in, my BIOS refused to boot my harddrives. At the time I had Windows 7 Installed on 2 different harddrives, a SSD which I had recently got, and then an older state of Windows 7 on my older drive. The BIOS could detect both drives and it would list them under the SATA connections, but it wouldn't list them under boot options, even under various storage configuration settings. This is why I reinstalled Windows 7 yesterday, but I was curious if I could still somehow find a way to boot from the other drive. All the information is still on the harddrive, I can access all the files and such but BIOS just refuses to see it as a bootable drive, I even did a windows boot repair through the install CD on both drives an nothing came of it. Either way, this isn't my main concern, though if you have spare time, I'm curious as to how this could happen and how to possibly fix it
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Hello,

    It appears your JMicron SATA drivers may be the cause here. Please install these updated ones: ftp://driver.jmicron.com.tw/SATA_Con...17.62_WHQL.zip

    Also test your hard drive, with SeaTools.

    If the BSODs persist, upload a new report.

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Jan 10 21:53:23.313 2011 (UTC - 5:00)
    System Uptime: 0 days 0:09:26.343
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+4b4e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_jraid+4b4e
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Jan 10 21:43:02.613 2011 (UTC - 5:00)
    System Uptime: 0 days 1:02:01.644
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  PhoenixViewer.
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+100
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan 10 20:24:05.895 2011 (UTC - 5:00)
    System Uptime: 0 days 2:24:56.925
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+15fea )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    FAILURE_BUCKET_ID:  X64_0x7E_jraid+15fea
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan 10 17:59:16.802 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:07.832
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_GenuineIntel
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan 10 16:24:52.494 2011 (UTC - 5:00)
    System Uptime: 0 days 8:49:33.525
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+15fea )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    FAILURE_BUCKET_ID:  X64_0x7E_jraid+15fea
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan 10 07:33:59.515 2011 (UTC - 5:00)
    System Uptime: 0 days 5:41:50.545
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+15fea )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    FAILURE_BUCKET_ID:  X64_0x7E_jraid+15fea
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Jan 10 01:31:06.129 2011 (UTC - 5:00)
    System Uptime: 0 days 4:00:35.160
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+15fea )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    FAILURE_BUCKET_ID:  X64_0x7E_jraid+15fea
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jan  9 21:29:39.293 2011 (UTC - 5:00)
    System Uptime: 0 days 3:06:11.324
    *** WARNING: Unable to verify timestamp for jraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys ( jraid+15fea )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    FAILURE_BUCKET_ID:  X64_0x7E_jraid+15fea
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jan  9 18:08:56.079 2011 (UTC - 5:00)
    System Uptime: 0 days 0:25:19.110
    Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  taskhost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1dd
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64
    Thread Starter
       #3

    Ahh yes, now that you mention it, I had posted on some other forum probably about a year ago and they recommended the same thing..

    Why can't windows auto driver update do things right

    Thanks for pointing this out to me, this is probably the fix. I remember a few months after I first built my machine I ran into these problems and updating those drivers fixed the issue.

    Gunna be dropping this into my essential 'installer folder' now
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    Good luck!

    Windows Update can't find all the 3rd-party drivers, but at least it finds working drivers 9/10 times.
      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 18:58.
Find Us