Random BSODs after SFC scannow


  1. tykon
    Posts : 4
    Windows 7 Pro 64bit
       New #1

    Random BSODs after SFC scannow


    Hi guys,
    I built this computer around 2 years ago, but haven't used it much since leaving for college. I installed Windows 7 Pro 64-bit OEM (from my school) on it during the summer, and it started having random crashes once in a while.
    System Specs:
    Q6600 @ stock
    ASUS P5k-E/WIFIAP
    2x1GB DDR2 800MHZ mushkin @ stock (dont know timings)
    X1900xtx @ stock
    I have sufficient cooling, its not the power supply because even if I unplug everything not essential it still crashes.
    Thanks for any help you guys can give!
    I ran the SFC scannow in command prompt and it said it was all clear.
    however, it still periodically crashes even when i just leave it idle.
    any other suggestions?
    thanks for the help!
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    tykon said:
    Hi guys,
    I built this computer around 2 years ago, but haven't used it much since leaving for college. I installed Windows 7 Pro 64-bit OEM (from my school) on it during the summer, and it started having random crashes once in a while.
    System Specs:
    Q6600 @ stock
    ASUS P5k-E/WIFIAP
    2x1GB DDR2 800MHZ mushkin @ stock (dont know timings)
    X1900xtx @ stock
    I have sufficient cooling, its not the power supply because even if I unplug everything not essential it still crashes.
    Thanks for any help you guys can give!
    I ran the SFC scannow in command prompt and it said it was all clear.
    however, it still periodically crashes even when i just leave it idle.
    any other suggestions?
    thanks for the help!

    These were caused by hardware, and I am betting it may be your yk62x64.sys Marvel Yukon driver. It is both suspect and released before win 7 was released. It needs to be updated.

    Code:
    yk62x64.sys        fffff880`04d87000    fffff880`04deb000    0x00064000    0x4a13bbce    5/20/2009 04:14:06

    Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

    Thanks


    Ken

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051310-21715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0281f000 PsLoadedModuleList = 0xfffff800`02a5ce50
Debug session time: Fri May 14 01:46:55.460 2010 (GMT-4)
System Uptime: 0 days 0:43:01.390
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002cd5028, b2000018, 2000e0f}

Probably caused by : hardware

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  4. jcgriff2
    Posts : 845
    Windows 7 - Vista
       New #3

    Hi -

    There were 10 dumps in all, two from May 2010; the rest October 8 & 9, 2010.

    The bugchecks -
    (2) 0x124 = WHEA
    (7) 0x1e = kernel threw an exception
    (1) 0x3b = system service exception

    You ATI Video drivers need to be updated -
    Code:
    atikmdag.sys Fri Apr 24 06:51:57 2009 (49F199CD)
    Radeon X1900 Series - Downloads


    Marvel Yukon Ethernet was updated after the second BSOD on 8 October -
    Code:
    yk62x64.sys  Wed Sep 15 10:31:29 2010 (4C90D8C1)
    I would advise that you run memtest86+ one stick at a time and alternate the slots.

    memtest86+ - Memtest86+ - Advanced Memory Diagnostic Tool

    Burn memtest86+ ISO to CD with ImgBurn - The Official ImgBurn Website

    Also be sure to review the 0x124 info that Ken mentioned - Stop 0x124 - what it means and what to try


    Windbg Logs
    --> http://jcgriff2.net/BSOD_Logs/_99-db..._jcgriff2_.txt
    --> http://jcgriff2.net/BSOD_Logs/_99-db...riff2_.txt.zip

    Regards. . .

    jcgriff2

    `

    BSOD BUGCHECK SUMMARY
    Code:
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  9 03:41:07.188 2010 (GMT-4)
System Uptime: 0 days 0:15:18.076
Probably caused by : memory_corruption ( nt!MiResolveDemandZeroFault+3b9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  BlizzardDownlo
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`0289b109 00000000`00000000 00000000`00001100
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct  9 03:25:14.244 2010 (GMT-4)
System Uptime: 0 days 10:49:52.132
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+3bb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  Blizzard Updat
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`028a110b 00000000`00000000 00000000`00006500
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 16:34:26.133 2010 (GMT-4)
System Uptime: 0 days 0:47:06.022
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`028f1028 00000000`b2000000 00000000`00060151
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 15:45:27.570 2010 (GMT-4)
System Uptime: 0 days 0:03:04.459
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+3bb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  tracerpt.exe
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`0289e10b 00000000`00000000 00000000`00001100
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 15:41:20.646 2010 (GMT-4)
System Uptime: 0 days 0:26:16.128
Probably caused by : memory_corruption ( nt!MiResolveDemandZeroFault+3b9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  WmiPrvSE.exe
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`028ab109 00000000`00000000 00000000`00001700
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 15:14:01.008 2010 (GMT-4)
System Uptime: 0 days 0:01:27.491
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+3bb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  winlogon.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`028a810b fffff880`035cf820 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 03:22:53.055 2010 (GMT-4)
System Uptime: 0 days 0:11:11.537
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+3bb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  mscorsvw.exe
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`0289810b 00000000`00000000 00000000`00000900
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 03:10:38.610 2010 (GMT-4)
System Uptime: 0 days 0:10:47.092
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+3bb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  mscorsvw.exe
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`028a610b 00000000`00000000 00000000`00001900
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 14 18:44:41.715 2010 (GMT-4)
System Uptime: 0 days 0:03:26.198
Probably caused by : ntkrnlmp.exe ( nt!KiSaveDebugRegisterState+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  SC2.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000096 fffff800`028d23c7 00000000`00000000 fffffa80`01a3f000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri May 14 01:46:55.460 2010 (GMT-4)
System Uptime: 0 days 0:43:01.390
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  BlizzardDownlo
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`02cd5028 00000000`b2000018 00000000`02000e0f
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
 
by jcgriff2     
 
        J. C. Griffith, Microsoft MVP   
 
          https://mvp.support.microsoft.com/profile/Griffith   
 
          www.jcgriff2.com 
 
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
      My Computer
    Quote Quote

 

  Related Discussions
Getting random BSODS from 5 times a week to 2 times a week to 0 times a week its really random and i hope the files can describe the issue.
Hi all, first off, thanks for reading this. Basically, my current build is about 2-3 years old, the newest thing being my PSU (which I replaced after several issues with the GPU drivers constantly crashing, turns out it wasn't the power anyway...) For the past few weeks, I've been having...
I searched the forums, but I have not managed to find anything dealing with my specific issues and I'm not sure how to interpret the results. I have attached my sfcdetails.txt and system specs. Any help would be greatly appreciated.
Since 16 Feb 2013 to today 22 Feb 2013 I've been getting Blue Screens; these appear to be completely random each time with different stop codes and (according to Blue Screen Veiw) are caused by different files. For example; Caused by ntkrnlpa.exe or atikmdag.exe, or ks,sys, or USBPORT.SYS, or...
Hey folks. Acer AS4830TG-6808 Win7 Home Premium x64 Acer OEM Machine is less than a month old Added 4GB Ram stick (PNY, now total of 8GB) Have been getting random BSODs over the last week or so. I'm not sure of the reasoning, however I suspect it may be gaming related. Errors began while...
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 00:46.
Find Us