computer freezes in game (10 to 15min in the game)

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by calmpitbull, Sep 18, 2012.

  1. calmpitbull

    calmpitbull New Member

    Joined:
    Sep 17, 2012
    Messages:
    10
    Likes Received:
    0
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033


    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA8006966038
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1


    Files that help describe the problem:
    C:\Windows\Minidump\091112-21359-01.dmp
    C:\Users\calmpitbull\AppData\Local\Temp\WER-44453-0.sysdata.xml



    I have updated drivers, clean registry and still nothing? pls help
    thx
     

    Attached Files:

  2. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    HotSpotShield is known to cause BSOD's in some Win7 systems. Please uninstall it.

    Win 7 doesn't like wireless USB devices. Here's my rant on the subject:
    Only 2% free space on your C: drive
    Only 9% free space on your E: drive
    Please free up enough space to make 15% free space on all of your hard drives.
    The system needs this to operate properly and ensure good performance.

    You have both Comodo Internet Security and Avira antivirus installed. Please uninstall the Comodo Internet Security (it has had BSOD problems in the past) and ensure that your Windows Firewall is enabled. Please only run one antivirus (this includes Internet Security applications) and one firewall at a time.

    Update Intel storage drivers and JMicron RAID drivers (all date from 2009):

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
    PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
    Sonic CD/DVD driver (used by many different CD/DVD programs)
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    Not essential to remove this - but it is advisable for testing purposes

    intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
    Intel IDE storage driver
    http://www.carrona.org/drivers/driver.php?id=intelide.sys

    jraid.sys Mon Nov 23 01:43:32 2009 (4B0A2F14)
    JMicron RAID Driver
    http://www.carrona.org/drivers/driver.php?id=jraid.sys

    If this doesn't stop the BSOD's, then start with these free hardware diagnstics: Hardware Diagnostics

    Analysis:
    The following is for information purposes only.
    Code:
    [FONT=lucida console]**************************Tue Sep 11 06:01:54.437 2012 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091112-21359-01.dmp]
    Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
    Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
    System Uptime:[B]0 days 0:00:08.453[/B]
    BugCheck Code: [B]BugCheck 124, {0, fffffa8006966038, 0, 0}[/B]
    Probably caused by :[B]GenuineIntel[/B]
    BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
    BUGCHECK_STR:  0x124_GenuineIntel
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel__UNKNOWN_PRV[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Sep 10 05:03:28.562 2012 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091012-15187-01.dmp]
    Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
    Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
    System Uptime:[B]0 days 0:00:07.625[/B]
    BugCheck Code: [B]BugCheck 124, {0, fffffa8004c9b8f8, 0, 0}[/B]
    Probably caused by :[B]GenuineIntel[/B]
    BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
    BUGCHECK_STR:  0x124_GenuineIntel
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel__UNKNOWN_PRV[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Sep 10 04:22:51.140 2012 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091012-16250-01.dmp]
    Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
    Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
    System Uptime:[B]0 days 0:00:08.203[/B]
    BugCheck Code: [B]BugCheck 124, {0, fffffa800504a8f8, 0, 0}[/B]
    Probably caused by :[B]GenuineIntel[/B]
    BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
    BUGCHECK_STR:  0x124_GenuineIntel
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel__UNKNOWN_PRV[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Sep  5 08:22:15.015 2012 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090512-14218-01.dmp]
    Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
    Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
    System Uptime:[B]0 days 0:00:07.156[/B]
    BugCheck Code: [B]BugCheck 124, {0, fffffa80067da478, 0, 0}[/B]
    Probably caused by :[B]GenuineIntel[/B]
    BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
    BUGCHECK_STR:  0x124_GenuineIntel
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel__UNKNOWN_PRV[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/FONT]

    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    [FONT=lucida console]**************************Tue Sep 11 06:01:54.437 2012 (UTC - 4:00)**************************
    [COLOR=RED][B]PxHlpa64.sys       Tue Jun 23 19:16:35 2009 (4A416253)[/B][/COLOR]
    [COLOR=RED][B]intelide.sys       Mon Jul 13 19:19:48 2009 (4A5BC114)[/B][/COLOR]
    [COLOR=#ff0000][B]jraid.sys          Mon Nov 23 01:43:32 2009 (4B0A2F14)
    [/B][/COLOR]amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    johci.sys          Tue Aug 24 07:25:58 2010 (4C73AC46)
    iusb3hcs.sys       Mon May 21 03:23:42 2012 (4FB9ED7E)
    [/FONT]
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    http://www.carrona.org/drivers/driver.php?id=jraid.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=johci.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
     
    #2 usasma, Sep 18, 2012
    Last edited: Sep 18, 2012
    1 person likes this.
  3. calmpitbull

    calmpitbull New Member

    Joined:
    Sep 17, 2012
    Messages:
    10
    Likes Received:
    0
    thx for info ill start with first set of what to do and i will report back
     
  4. calmpitbull

    calmpitbull New Member

    Joined:
    Sep 17, 2012
    Messages:
    10
    Likes Received:
    0
    still fighting with error

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033


    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA80064994F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
     

    Attached Files:

  5. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 124, {0, fffffa80067da478, 0, 0}
    
    
    Probably caused by : hardware
    
    
    Followup: MachineOwner
    ---------
    
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80067da478, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    [COLOR=#FF0000]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/COLOR]
    
    
    [COLOR=#FF0000]PROCESS_NAME:  System[/COLOR]
    
    
    CURRENT_IRQL:  0
    
    
    STACK_TEXT:  
    fffff880`033696f0 fffff800`030c4ca9 : fffffa80`067da450 fffffa80`055a0040 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03369c10 fffff800`02fa5547 : fffffa80`067da450 fffff800`0301f2d8 fffffa80`055a0040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03369c40 fffff800`02f0c945 : fffff800`03080ae0 00000000`00000001 fffffa80`06504820 fffffa80`055a0040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03369c80 fffff800`02e8b841 : fffff880`0113fe00 fffff800`02f0c920 fffffa80`055a0000 fffff800`030712d8 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03369cb0 fffff800`03118e6a : 177b177b`0a7f0a7f fffffa80`055a0040 00000000`00000080 fffffa80`05507040 : nt!ExpWorkerThread+0x111
    fffff880`03369d40 fffff800`02e72ec6 : fffff880`03186180 fffffa80`055a0040 fffff880`031910c0 25e768af`9b316563 : nt!PspSystemThreadStartup+0x5a
    fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`033690a0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: hardware
    
    
    IMAGE_NAME:  hardware
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    [COLOR=#FF0000]FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV[/COLOR]
    
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    
    Followup: MachineOwner
    ---------
    
    
    
    Code:
    4: kd> rrax=fffffa8005023000 rbx=fffffa8004c9b8f8 rcx=fffff88003362730
    rdx=fffff88002f70000 rsi=0000000000000000 rdi=fffffa8005023000
    rip=fffff800035179cc rsp=fffff880033626f0 rbp=0000000000000001
     r8=000000000000f1e0  r9=00000000000007ff r10=000000000000060c
    r11=0000000000000000 r12=fffff800032e4b40 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
    [COLOR=#FF0000]nt!WheapCreateLiveTriageDump+0x6c:[/COLOR]
    fffff800`035179cc 48897c2438      mov     qword ptr [rsp+38h],rdi ss:0018:fffff880`03362728=fffffa8000000910
    
    
    
    Code:
    fffff800`0301e000 fffff800`03067000   hal        (pdb symbols)          c:\symbols\hal.pdb\A085D08B9C5D4BFDBA48AC285BDA03F22\hal.pdb    Loaded symbol image file: hal.dll
        Mapped memory image file: c:\symbols\hal.dll\4CE7C66949000\hal.dll
        Image path: hal.dll
        Image name: hal.dll
        Timestamp:        Sun Nov 21 00:00:25 2010 (4CE7C669)
        CheckSum:         000404C3
        ImageSize:        00049000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     hal.dll
        OriginalFilename: hal.dll
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  Hardware Abstraction Layer DLL
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    
    
    Code:
    fffff800`03067000 fffff800`0364f000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\ABD176D2C7AE41B88BBF2837A09A462C2\ntkrnlmp.pdb    Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: c:\symbols\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Fri May 04 18:18:59 2012 (4FA390F3)
        CheckSum:         00555F80
        ImageSize:        005E8000
        File version:     6.1.7601.17835
        Product version:  6.1.7601.17835
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7601.17835
        FileVersion:      6.1.7601.17835 (win7sp1_gdr.120503-2030)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    
    
    Code:
    fffff880`00c51000 fffff880`00c65000   PSHED      (pdb symbols)          c:\symbols\pshed.pdb\F1B5874289B044199CE35519D256D3E32\pshed.pdb    Loaded symbol image file: PSHED.dll
        Mapped memory image file: c:\symbols\PSHED.dll\4A5BE02714000\PSHED.dll
        Image path: PSHED.dll
        Image name: PSHED.dll
        Timestamp:        Tue Jul 14 11:32:23 2009 (4A5BE027)
        CheckSum:         0000F762
        ImageSize:        00014000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     pshed.dll
        OriginalFilename: pshed.dll
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  Platform Specific Hardware Error Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved
    Are just examples of the drivers used at the time - most of them from windows update.
    Could you open Windows Update and see if there are any updates available?
    http://www.carrona.org/drivers/driver.php?id=hal.dll
    http://www.carrona.org/drivers/driver.php?id=ntoskrnl.exe
    http://www.carrona.org/drivers/driver.php?id=PSHED.dll
    relating to the three problems I said above.
    Also try updating these:
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    http://www.carrona.org/drivers/driver.php?id=jraid.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
    http://www.carrona.org/drivers/driver.php?id=johci.sys

    take note of the first code box - WHEA_UNCORRECTABLE_ERROR (0x124)
    According to this file: Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
    First, download and install all of the new drivers.
    This means drivers from Windows Update, from the Driver Site, etc etc.

    Second, use a good Antivirus (Microsoft Security Essentials, McAfee, Norton) and do a FULL SCANof your system.

    Third, check your hard disk and memory for problems.
    Hardware problems -
    Hard Disk:
    hdtune.com
    install and test it


    CPU Test #1
    Free Software - GIMPS
    Skip to step 2 (of the website), and download the appropriate file.
    Open the .zip file, and run the Prime95.exe file. (Click Yes if prompted to do so)
    Open the Advanced tab, and select "Round Off Checking".
    Select "Just Stress Testing" and then "Small FFTs".
    Leave it for about 2 or 3 hours, keeping an eye on your computer - if it starts to overheat or you hear a strange meowing sound inside the case, close Prime 95. Otherwise, finish it, take a screenshot and post back.
    RAM
    Memtest86+ - Advanced Memory Diagnostic Tool
    Download the Pre-compiled Boot ISO .zip file.
    Open the .zip file and drag the ISO file somewhere for easy access (My Documents, Desktop whatever)
    Right-click the file and select "Open with <cd driver>"
    Insert a blank CD into your CD reader, select the correct disk burner and then click "Burn".
    Reboot your computer - if Memtest runs automatically, good (if not, reboot your computer, enter BIOS through F2 and make sure your CD Drive is the first in the boot order).
    Let it run for about several hours (overnight) - Don't touch it (the longer you run it for, the better).
    If you get errors:
    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.
    NOTE: Be careful when installing/uninstalling your RAM - you could potentially damage the sticks and/or your motherboard - check to see if your warranty has expired or if it won't void the warranty.

    Processor:
    Download IntelBurnTest 2.54 Free - Stress your computer to find out how stable it is - Softpedia
    Real Temp - CPU temperature monitoring
    Download those two files and install them.
    Now, this is to check if your processor is the problem.
    First, ARK | Your source for information on Intel® products select the processor you're using. Let's use my computer as an example.
    I have an i7-860, so I'll select Previous Generation Intel Core i7 (Desktop)
    Now, I select my processor, which is at the bottom.
    I scroll down until I see TCase, which is the temperature. Mine is suppsoed to be at 72.7C MAX
    So now that I know my max temperature, I open REALTEMP.
    Make sure that the cores' temperatures are AT LEAST 25C lower than the MAX SPECIFICATIONS. (NOTE: If the temperatures are at the MAX and you aren't running any big programs, you've found the culprit).
    So, my temperatures are about 30C lower. Time to start the IntelBurnTest.
    Place the IntelBurnTest Box and RealTemp Box next to eachother.
    Make the "Time to run" about 6 or so, and the Threads to test all.
    Run a few burn tests on "Standard" and record the temperatures. See anything out of the ordinary (really high temperatures - standard test shouldn't let you fall within 20C of MAX)
    Repeat with High, Very High and so on, recording the results, and post them back here.

    :)
     
    #5 GeneralHiningII, Oct 20, 2012
    Last edited: Oct 21, 2012
  6. calmpitbull

    calmpitbull New Member

    Joined:
    Sep 17, 2012
    Messages:
    10
    Likes Received:
    0
    i need help with drivers, i have slim driver to scan for new drivers that i need and there is no new ones. and how do i know which one do i need from jmicron site and how to manual install them?
    THX

    oh i have free avira anitivirus i hope it is good enough
     
  7. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Speccy - System Information - Free Download
    Download speccy and run it, see what devices you have.
    Google each one, and they should have the automatic driver for it (remember to also use Windows Update)
    Avira is a good one, but you have to run the full scan.
     
  8. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Are you using the JMicron RAID controller?
    If so, please provide the exact make and model of your mobo (or make and model of your system if it's an OEM system - like an HP or a Dell)
    If not, don't worry about it for right now. The driver was singled out simply because it was older - not because there are any known problems with it.

    In short, it's much more likely that the other things I suggested will identify the issue - and then you won't have to worry about the issue.

    Just FYI - this is the most recent one that I could find: ftp://driver.jmicron.com.tw/SATA_Controller/Windows/JMB36X_WinDrv_R1.17.63_WHQL.zip (dates from 2011)
     

Share This Page

Loading...