irql_not_less_or_equal-stop-0x0000000a at startup

Page 1 of 6 123 ... LastLast

  1. Posts : 53
    Windows 7 Ultimate x64
       #1

    irql_not_less_or_equal-stop-0x0000000a at startup


    Hi! I had a BSOD about a month ago and then another one a few days ago, those are the only BSOD's I have had on my PC since I built it about 6 months ago, the only change I did after I built it was I installed a new SSD and reinstalled windows. I have tried testing my RAM and it went just fine. I attached the .dmp files, five of them. Would really appreciate help!

    Oh and I have had random minimizing in games as well, sometimes it will minimize at lot, like every few minutes, or goes fine for several weeks...

    BTW I only had BSOD's after I installed the new SSD and reinstalled windows. and I think (might be wrong) they happened even before my BIo's posted.

    OK... the .dmp files fail to upload... suggestions?

    011413-19531-01.dmp:
    Invalid File
    012313-19858-01.dmp:
    Invalid File
    022713-19266-01.dmp:
    Invalid File
    032913-19406-01.dmp:
    Invalid File
    100412-22510-01.dmp:
    Invalid File
      My Computer


  2. Posts : 53
    Windows 7 Ultimate x64
    Thread Starter
       #2

    Here are the files.
      My Computer


  3. Posts : 53
    Windows 7 Ultimate x64
    Thread Starter
       #3

    So any idea's?
      My Computer


  4. Posts : 4,161
    Windows 7 Pro-x64
       #4

    Wow! Don't know what this is all about. Looks like Windows is missing a bunch of updates. You might start there first.

    Code:
     
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    *** WARNING: Unable to verify timestamp for AiChargerPlus.sys
    *** ERROR: Module load completed but symbols could not be loaded for AiChargerPlus.sys
    *** WARNING: Unable to verify timestamp for iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    *** WARNING: Unable to verify timestamp for asahci64.sys
    *** ERROR: Module load completed but symbols could not be loaded for asahci64.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for iaStorF.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
    *** WARNING: Unable to verify timestamp for AsIO.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsIO.sys
    *** WARNING: Unable to verify timestamp for AsUpIO.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsUpIO.sys
    *** WARNING: Unable to verify timestamp for HECIx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    *** WARNING: Unable to verify timestamp for asmtxhci.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
    *** WARNING: Unable to verify timestamp for ICCWDT.sys
    *** ERROR: Module load completed but symbols could not be loaded for ICCWDT.sys
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *** WARNING: Unable to verify timestamp for nvhda64v.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys
    *** WARNING: Unable to verify timestamp for btath_bus.sys
    *** ERROR: Module load completed but symbols could not be loaded for btath_bus.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for btfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    *** WARNING: Unable to verify timestamp for asmthub3.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
    *** WARNING: Unable to verify timestamp for ASUSFILTER.sys
    *** ERROR: Module load completed but symbols could not be loaded for ASUSFILTER.sys
    *** WARNING: Unable to verify timestamp for xusb21.sys
    *** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
    *** WARNING: Unable to verify timestamp for kl2.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl2.sys
    *** WARNING: Unable to verify timestamp for klim6.sys
    *** ERROR: Module load completed but symbols could not be loaded for klim6.sys
    *** WARNING: Unable to verify timestamp for dump_iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    *** WARNING: Unable to verify checksum for win32k.sys
    *** WARNING: Unable to verify checksum for TSDDD.dll
    *** WARNING: Unable to verify checksum for cdd.dll
    *** WARNING: Unable to verify checksum for ATMFD.DLL
    *** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
    Gotta run for now. Storm blowing in!
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Update Asmedia 106x SATA Host Controller Driver from ASMedia Technology Inc. ????

    Download and install this particular version of Intel Rapid Storage.

    Free up the startup.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Some other things are also need a look. Will see those after seeing the results of these.
      My Computer


  6. Posts : 53
    Windows 7 Ultimate x64
    Thread Starter
       #6

    carwiz said:
    Wow! Don't know what this is all about. Looks like Windows is missing a bunch of updates. You might start there first.

    Code:
     
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    *** WARNING: Unable to verify timestamp for AiChargerPlus.sys
    *** ERROR: Module load completed but symbols could not be loaded for AiChargerPlus.sys
    *** WARNING: Unable to verify timestamp for iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    *** WARNING: Unable to verify timestamp for asahci64.sys
    *** ERROR: Module load completed but symbols could not be loaded for asahci64.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for iaStorF.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
    *** WARNING: Unable to verify timestamp for AsIO.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsIO.sys
    *** WARNING: Unable to verify timestamp for AsUpIO.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsUpIO.sys
    *** WARNING: Unable to verify timestamp for HECIx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    *** WARNING: Unable to verify timestamp for asmtxhci.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
    *** WARNING: Unable to verify timestamp for ICCWDT.sys
    *** ERROR: Module load completed but symbols could not be loaded for ICCWDT.sys
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *** WARNING: Unable to verify timestamp for nvhda64v.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys
    *** WARNING: Unable to verify timestamp for btath_bus.sys
    *** ERROR: Module load completed but symbols could not be loaded for btath_bus.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for btfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    *** WARNING: Unable to verify timestamp for asmthub3.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
    *** WARNING: Unable to verify timestamp for ASUSFILTER.sys
    *** ERROR: Module load completed but symbols could not be loaded for ASUSFILTER.sys
    *** WARNING: Unable to verify timestamp for xusb21.sys
    *** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
    *** WARNING: Unable to verify timestamp for kl2.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl2.sys
    *** WARNING: Unable to verify timestamp for klim6.sys
    *** ERROR: Module load completed but symbols could not be loaded for klim6.sys
    *** WARNING: Unable to verify timestamp for dump_iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    *** WARNING: Unable to verify checksum for win32k.sys
    *** WARNING: Unable to verify checksum for TSDDD.dll
    *** WARNING: Unable to verify checksum for cdd.dll
    *** WARNING: Unable to verify checksum for ATMFD.DLL
    *** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
    Gotta run for now. Storm blowing in!
    OK I scanned twice for updates, no new updates are available. I have 36 optional available though, 34 are for extra languages and the other two are Bing and SilverLight. If I reinstalled windows would it fix this? I was gonna upgrade to 4-6TB's of space very soon anyway. Also could this be the cause of my random game minimizing? Thanks!
      My Computer


  7. Posts : 53
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Arc said:
    Update Asmedia 106x SATA Host Controller Driver from ASMedia Technology Inc. ????

    Download and install this particular version of Intel Rapid Storage.

    Free up the startup.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Some other things are also need a look. Will see those after seeing the results of these.
    OK, I'll look at downloading those. I don't understand how disabling everything but Antivirus will help. As far as I can remember none of the blue screens happened once Windows was booted, they happened right after (or possibly before) the BIO's screen flashes.

    BTW, Has anyone ever heard of and know what "Zippy OSD" is?
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    ZombieKiller said:
    I don't understand how disabling everything but Antivirus will help.
    Then why you dont try to trust on who understand ? :)
    People are afraid of removing startup entries only when they think that they are necessary. But no version of windows (and any other OS) does not need any other program to start with it. They are just extra, and they cause various issues, conflicts and BSODs, too. Nobody will accept the fact that you are running 17 items in the background all the times. Remove them. Nothing will be lost. You can access them anytime from Start> All Programs.
    ZombieKiller said:
    As far as I can remember none of the blue screens happened once Windows was booted, they happened right after (or possibly before) the BIO's screen flashes.
    That's an important information. Which may lead to a sense of hardware error. But as far as there are software errors present, they are to be eliminated, too. And Removing startup items are the first step.

    But if you still disagree to do it, I may doubt that you may disagree that the later suggestions too. And if you disagree, no help can be effective.

    XBox USB wireless controller driver is a very well known cause of BSODs, and it is contributing to your BSODs, too.
    Code:
    fffff880`0693f740  fffff880`097e2b74Unable to load image \SystemRoot\system32\DRIVERS\xusb21.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xusb21.sys
    *** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
     xusb21+0x2b74
    fffff880`0693f748  fffff880`097e2b74 xusb21+0x2b74
    fffff880`0693f750  fffffa80`19883928
    fffff880`0693f758  fffff880`097e9891 xusb21+0x9891
    And that particular 2009 version of this driver always BSODs.
    Code:
    fffff880`097e0000 fffff880`097f2100   xusb21   T (no symbols)           
        Loaded symbol image file: xusb21.sys
        Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
        Image name: xusb21.sys
        Timestamp:        Fri Aug 14 03:40:17 2009 (4A848F49)
        CheckSum:         0001398B
        ImageSize:        00012100
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Update it from Software Downloads | Microsoft Hardware.

    You can see a lot of USBPORT.sys error is present there.
    Code:
    fffff880`0693fc58  fffff880`07cb8db0 USBPORT!USBPORT_Xdpc_Worker
    fffff880`0693fb58  fffff880`07cb8f89 USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`0693fb18  fffff880`07cc766f USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`0693fae8  fffff880`07ccbd23 USBPORT!USBPORT_Core_CheckTimeout+0x27
    fffff880`0693fab8  fffff880`07cc9b0f USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`0693f9d8  fffff880`07cc9631 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
    fffff880`0693fa08  fffff880`07cc7500 USBPORT!USBPORT_FlushAdapterDBs+0x144
    fffff880`0693fa28  fffff880`07cc5b28 USBPORT!USBPORT_TxCsqFindIrp+0x1c
    fffff880`0693f978  fffff880`07cde6d6 USBPORT!USBPORT_DereferenceDeviceHandle+0x14e
    These might be caused by either the XBOX driver, or any other reason is there behind it. Do some general USB related troubleshooting. For the port, first, uninstall and reinstall the USB ports drivers.

    1. Right click on Computer icon > manage. It will open the computer management window.
    2. Click on "Device Manager" in the left pane, it will list all installed devices up.
    3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
    4. Click on one item to select, then right click and uninstall.
    5. Do the same for all.
    6. Restart the computer.
    7. At restart, windows will auto configure the appropriate drivers.

    And, Disable USB Selective Suspense too.
    USB Selective Suspend - Turn On or Off

    For the devices, first, detach all the USB devices other than the keyboard and mouse.
    Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.

    If you think that you should do these, or these might help, you do these and reply back.
    ________________________________________________________________
    BSOD ANALYSIS (all the latest crash dumps are essentially identical, other than that of 14.01; and the problem of that date does not exist today)
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {40, 2, 1, fffff800032da1c8}
    
    Probably caused by : Wdf01000.sys ( Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+20e )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000040, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800032da1c8, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003504100
    GetUlongFromAddress: unable to read from fffff800035041c0
     0000000000000040 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiTryUnwaitThread+28
    fffff800`032da1c8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88006946FB0
    
    TRAP_FRAME:  fffff8800693f4b0 -- (.trap 0xfffff8800693f4b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880069222c8 rbx=0000000000000000 rcx=fffff88006917180
    rdx=fffffa8019482d08 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800032da1c8 rsp=fffff8800693f640 rbp=0000000000000002
     r8=0000000000000100  r9=0000000000000000 r10=fffffa8019482d08
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiTryUnwaitThread+0x28:
    fffff800`032da1c8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032cb1e9 to fffff800032cbc40
    
    STACK_TEXT:  
    fffff880`0693f368 fffff800`032cb1e9 : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0693f370 fffff800`032c9e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0693f4b0 fffff800`032da1c8 : fffff880`0693f7a8 00000000`00000000 fffffa80`19453cf0 00000000`00000002 : nt!KiPageFault+0x260
    fffff880`0693f640 fffff800`032d0688 : fffffa80`1985b878 00000000`00000002 00000000`00000000 fffff880`06917180 : nt!KiTryUnwaitThread+0x28
    fffff880`0693f6a0 fffff880`00f49b8a : 00000000`00000000 00000000`00000000 fffff880`0693f700 fffff880`069221c0 : nt!KeSetEvent+0x446
    fffff880`0693f710 fffff880`00ef35c0 : fffffa80`1985b480 00000000`00000000 fffffa80`19486860 fffffa80`c0000184 : Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+0x20e
    fffff880`0693f790 fffff880`00ef4838 : fffffa80`19482e40 fffffa80`19482e30 00000000`00000001 fffffa80`19482e40 : Wdf01000!FxRequestBase::CompleteSubmitted+0x170
    fffff880`0693f810 fffff880`00ef54b8 : 00000000`00000002 fffffa80`194d5c40 00000000`00000000 fffffa80`18a85250 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1c0
    fffff880`0693f880 fffff800`032b77a5 : 00000000`00000000 fffff800`0345c580 00000000`00000005 fffff800`034004f1 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
    fffff880`0693f8b0 fffff800`032cf6d1 : fffffa80`1985d3b3 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
    fffff880`0693f8f0 fffff880`07cc9631 : fffffa80`18549050 fffffa80`1985df00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff880`0693f9e0 fffff880`07cc9b0f : fffffa80`19472c02 fffffa80`1985d010 00000000`ffffffff fffffa80`18549eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
    fffff880`0693fac0 fffff880`07cc766f : fffffa80`18549eb0 fffffa80`185491a0 fffffa80`1854a050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`0693fb20 fffff880`07cb8f89 : fffffa80`18549050 00000000`00000000 fffffa80`18549e02 fffffa80`18549eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`0693fb60 fffff800`032d63fc : fffff880`06917180 fffffa80`18549eb0 fffffa80`18549ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`0693fb90 fffff800`032c394a : fffff880`06917180 fffff880`069221c0 00000000`00000000 fffff880`07cb8db0 : nt!KiRetireDpcList+0x1bc
    fffff880`0693fc40 00000000`00000000 : fffff880`06940000 fffff880`0693a000 fffff880`0693fc00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+20e
    fffff880`00f49b8a 4c8d5c2450      lea     r11,[rsp+50h]
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+20e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Wdf01000
    
    IMAGE_NAME:  Wdf01000.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5010aa89
    
    FAILURE_BUCKET_ID:  X64_0xA_Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+20e
    
    BUCKET_ID:  X64_0xA_Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+20e
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 4,161
    Windows 7 Pro-x64
       #9

    Still stormy here so I won't be on long. It's possible that my wireless connection was flaky last night with the storm and the symbols from the Microsoft server didn't come through so I'd disregard the list above.

    Sounds like another wave coming so I'm shutting down (again).
      My Computer


  10. Posts : 53
    Windows 7 Ultimate x64
    Thread Starter
       #10

    OK so seems like its all software/driver related? Correct? If thats the case I'll just skip all the trouble shooting, I should have a new 4TB Seagate (DX) HDD in a few day (next week at latest). After it shows up I'll format my SSD and replace my 1TB HDD with the new 4TB, and reinstall windows... and get all the joy of downloading 800GB+ in STEAM games...
    So if (like I asked earlier) all the problems are because of drivers I'll just update my BIO's for now and install new firmware on my SSD and HDD when I reinstall.
    My current BIO's on my R4E is 1202 and the newest is something like 3602. I haven't updated them yet because I have never done it and I think I have to convert my BIO's from .ROM to .CAP for Windows 8. I am using W7 though. Do you know if it will cause compatibility issues??
    https://www.asus.com/Motherboards/RA...rt_Download_30
    As you can see on some of the BIO's it says I need to update to .CAP first then others don't say... Would really appreciate some help! :) Thanks for the help!

    Sorry I don't seem to know very much in this area...
      My Computer


 
Page 1 of 6 123 ... LastLast

  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 03:20.
Find Us