locked
Multiple problems on a new machine, crashes everyday RRS feed

  • Question

  • Dear all,

    Recently, I have made several threads here to get help for multiple problems I've been experiencing. None of my issues has been resolved. And now I'm getting daily crashes. So I've decided to post once more, now listing all my issues in 1 post so that maybe someone can connect the dots. Please, help me! It's very hard to get work or fun done on this computer now that it has been become so unstable.

    About the computer : 3rd computer I've built on my own and 1st one with so many issues. Full specs are in my signature. The mobo is an early revision of a P67 board so carries the SATA 2 issue that accompanies all early Sandy Bridge chipsets. As such, all of my internal HDDs are connected to the SATA 3 ports.

    Issues :

    1. Crashes with screeching noise : 1 or twice a day now. The computer becomes unresponsive with screeching noise comes out of the speakers. Only a hard Reset ends it. No error message is given afterward. Happens when playing music, video calling on Skype, or running non-full screen applications. Even since this first started, I have changed my speakers and web-cam. That hasn't fixed the issue.
    2. Unstable wireless adapters : I have gone through 3 wireless adapters with this computer: ASUS N13 USB, TP Link NW822N, and Belkin F5D8053N. The first 2 disconnected my connection during Skype video calls and produced BSOD's related to power state failure. The Belkin F5D8053N (currently connected) randomly makes my connection "Limited". When that happens, nothing short of a Reset or a Restart makes the connection normal again: troubleshooting, unplugging and replugging, and resetting the adapter are all useless. It seems very unlikely that I get 3 bad adapters in the a row so I'm inclined to think that something is wrong with my computer . IMPORTANT: there seems to be an interplay between the problem of the wireless adapters and the display driver . Sometimes right after I fire up a game, my Belkin F5D8053N makes the connection "Limited". Another time, I got a BSOD about the *wireless adapter* after getting error messages about the display driver (see issue 4 below).
    3. Computer becomes unresponsive after being idle : it doesn't always happen but when it does, I can't wake it when my mouse or my keyboard. Again, a hard Reset is required. Moreover, sometimes the HDD is turned off even though I'm having some background task is running (like transferring files via Winscp).
    4. nVidia display driver crashed and successfully recovered : there have been 2 separate incidents, during each I received like 5 errors within a few minutes about my display driver became unresponsive and was recovered. In 1 of these incidents, the computer allowed me to Restart, while in the other, it gave me a BSOD while trying to restart.
    5. Multiple boot choices : I only have Windows 7 installed on my main OS drive. And every time I reinstalled Windows, I formatted the drive. But now I'm having 4 different boot choices, all titled "Windows 7". I can't actually make a selection because the choices only appear for like 2 seconds.

    What have I tried :

    1. I've run Prime95, Furmark, and Memtest86+. No errors.
    2. Reinstalling Windows 7. Doesn't help.
    3. I have updated my BIOS, Windows, and drivers. All are up-to-dated as I'm typing.
    4. Disabling the Intel Management Engine. Doesn't seem to help.
    5. I have posted my issues here: 1 , 2 , 3 , 4 . The issues didn't get resolved by the previous threads .

    Additional info

    1. The screeching noise crashes never happen during full screen gaming.
    2. All my BSOD minidump files can be found here .

    My specs: * Hardware : Core i7 2500K stock, MSI P67A-GD65, 2x4GB RAM stock, GTX 570 factory overclocked, Corsair 850W PSU, Belkin F5D8053N, Logitech C510 Webcam, Logitech Z623 2.1 speakers * Software : Windows 7 x64 Pro SP1 OEM, Avast free 6.0, Firefox 3.6.13, Skype 5.1.0., lastest drivers for all hardware
    Friday, March 11, 2011 6:53 AM

Answers

  • ASUS N13:

    BugCheck 9F,

    Probably caused by : usbhub.sys
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e0 fffffa8009a1d060 00000000 fffff8800104155c-fffff880010413a4 Success Error Cancel
               \Driver\usbhub     ACPI!ACPIDeviceIrpDeviceFilterRequest
                Args: 00012200 00000001 00000003 00000002

    Belkin F5D8053N:

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 0000000000000258, Timeout in seconds.

    Child-SP          RetAddr           Call Site
    fffff880`033aea00 fffff800`02e99992 nt!KiSwapContext+0x7a
    fffff880`033aeb40 fffff800`02e9c1af nt!KiCommitThreadWait+0x1d2
    fffff880`033aebd0 fffff880`00e1c320 nt!KeWaitForSingleObject+0x19f
    fffff880`033aec70 fffff880`00e0d376 Wdf01000!FxUsbPipe::WaitForSentIoToComplete+0x124
    fffff880`033aecc0 fffff880`00e0c71b Wdf01000!FxIoTarget::Remove+0x6a
    fffff880`033aed10 fffff880`00e1bbf2 Wdf01000!FxIoTarget::Dispose+0x93
    fffff880`033aed40 fffff880`00e62bb5 Wdf01000!FxUsbPipe::Dispose+0x12
    fffff880`033aed70 fffff880`00e625c8 Wdf01000!FxObject::DisposeChildrenWorker+0x215
    fffff880`033aedf0 fffff880`00e62789 Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0xbc
    fffff880`033aee60 fffff880`00e62b89 Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xf5
    fffff880`033aeed0 fffff880`00e625c8 Wdf01000!FxObject::DisposeChildrenWorker+0x1e9
    fffff880`033aef50 fffff880`00e62789 Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0xbc
    fffff880`033aefc0 fffff880`00e62b89 Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xf5
    fffff880`033af030 fffff880`00e62883 Wdf01000!FxObject::DisposeChildrenWorker+0x1e9
    fffff880`033af0b0 fffff880`00e62159 Wdf01000!FxObject::DeleteWorkerAndUnlock+0xdf
    fffff880`033af110 fffff880`00e5d085 Wdf01000!FxObject::DeleteObject+0x1a9
    fffff880`033af170 fffff880`070ed90b Wdf01000!imp_WdfObjectDelete+0x101
    fffff880`033af1c0 fffffa80`08fa7600 arusb_win7x +0xc90b

        Image path: \SystemRoot\system32\DRIVERS\arusb_win7x.sys
        Image name: arusb_win7x.sys
        Timestamp:        Thu Nov 26 09:55:17 2009

    TP-Link WN822N:

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0  0 fffffa8009697050 00000000 00000000-00000000   
              Unable to load image \SystemRoot\system32\DRIVERS\arusb_win7x.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for arusb_win7x.sys
    *** ERROR: Module load completed but symbols could not be loaded for arusb_win7x.sys
     \Driver\arusb_win7x



    Because you get crashes with 3 different devices, connect the wireless devices to a different USB port.


    I also had trouble with USB devices, that's why I bought a PCI card for 10€. This is stable and ok for browsing the www.


    André


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Arthur Xie Monday, March 14, 2011 8:58 AM
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Friday, March 11, 2011 2:01 PM
  • Meanwhile, if you or anybody have any more info/opinion, please let me know. Also, does anybody understand or know how to fix the multiple boot choice issue?
    Run EasyBCD to delete the other entires.

    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Arthur Xie Monday, March 14, 2011 8:58 AM
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Friday, March 11, 2011 3:10 PM
  • ntvinh1985, I believe I have the solution to our problem.  I activated the OC Genie feature (turn computer off, push in OC genie button on motherboard, turn computer on) and everything seems stable now.  Someone on another forum mentioned the increase in voltage that occurs when this feature is turned on seems to be required for memory faster than 1333.  I am using 1600 and I suspect you may be using that or faster as well.  Give it a shot.  I've been monitoring processor temps since turning the feature on and I seem to be alright, but I'm going to get a better CPU cooler to be safe.  Hopefully the next few days will prove that the problem is solved for the long haul.
    • Marked as answer by ntvinh1985 Wednesday, April 6, 2011 10:55 AM
    Tuesday, March 15, 2011 3:28 AM
  • Good luck with the new board, hopefully it works out better for you.  The problem has been fixed.  I haven't had a lockup for 18 hours which has never happened.  It was as simple as activating OC Genie.  If you look on the box or in the manual under Supported Memory types, 1600 and above all have "(OC)" next to them.  I thought this meant that you needed at least that speed in order to overclock, but it must mean that you must overclock in order for the board to support those speeds.  The normal memory voltage must not be good enough for the higher speeds.  Looks like this is just a failure of the MSI documentation.  I'm extremely happy to have my computer working perfectly with the added bonus of a faster processor!
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Tuesday, March 15, 2011 3:53 PM

All replies

  • ASUS N13:

    BugCheck 9F,

    Probably caused by : usbhub.sys
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e0 fffffa8009a1d060 00000000 fffff8800104155c-fffff880010413a4 Success Error Cancel
               \Driver\usbhub     ACPI!ACPIDeviceIrpDeviceFilterRequest
                Args: 00012200 00000001 00000003 00000002

    Belkin F5D8053N:

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 0000000000000258, Timeout in seconds.

    Child-SP          RetAddr           Call Site
    fffff880`033aea00 fffff800`02e99992 nt!KiSwapContext+0x7a
    fffff880`033aeb40 fffff800`02e9c1af nt!KiCommitThreadWait+0x1d2
    fffff880`033aebd0 fffff880`00e1c320 nt!KeWaitForSingleObject+0x19f
    fffff880`033aec70 fffff880`00e0d376 Wdf01000!FxUsbPipe::WaitForSentIoToComplete+0x124
    fffff880`033aecc0 fffff880`00e0c71b Wdf01000!FxIoTarget::Remove+0x6a
    fffff880`033aed10 fffff880`00e1bbf2 Wdf01000!FxIoTarget::Dispose+0x93
    fffff880`033aed40 fffff880`00e62bb5 Wdf01000!FxUsbPipe::Dispose+0x12
    fffff880`033aed70 fffff880`00e625c8 Wdf01000!FxObject::DisposeChildrenWorker+0x215
    fffff880`033aedf0 fffff880`00e62789 Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0xbc
    fffff880`033aee60 fffff880`00e62b89 Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xf5
    fffff880`033aeed0 fffff880`00e625c8 Wdf01000!FxObject::DisposeChildrenWorker+0x1e9
    fffff880`033aef50 fffff880`00e62789 Wdf01000!FxObject::PerformDisposingDisposeChildrenLocked+0xbc
    fffff880`033aefc0 fffff880`00e62b89 Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xf5
    fffff880`033af030 fffff880`00e62883 Wdf01000!FxObject::DisposeChildrenWorker+0x1e9
    fffff880`033af0b0 fffff880`00e62159 Wdf01000!FxObject::DeleteWorkerAndUnlock+0xdf
    fffff880`033af110 fffff880`00e5d085 Wdf01000!FxObject::DeleteObject+0x1a9
    fffff880`033af170 fffff880`070ed90b Wdf01000!imp_WdfObjectDelete+0x101
    fffff880`033af1c0 fffffa80`08fa7600 arusb_win7x +0xc90b

        Image path: \SystemRoot\system32\DRIVERS\arusb_win7x.sys
        Image name: arusb_win7x.sys
        Timestamp:        Thu Nov 26 09:55:17 2009

    TP-Link WN822N:

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0  0 fffffa8009697050 00000000 00000000-00000000   
              Unable to load image \SystemRoot\system32\DRIVERS\arusb_win7x.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for arusb_win7x.sys
    *** ERROR: Module load completed but symbols could not be loaded for arusb_win7x.sys
     \Driver\arusb_win7x



    Because you get crashes with 3 different devices, connect the wireless devices to a different USB port.


    I also had trouble with USB devices, that's why I bought a PCI card for 10€. This is stable and ok for browsing the www.


    André


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Arthur Xie Monday, March 14, 2011 8:58 AM
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Friday, March 11, 2011 2:01 PM
  • Dear Andre, you've come to help me again! Thank you so much.

    These wireless adapters have been connected to different USB ports. Unfortunately, that doesn't seem to solve the problem. Maybe I'll get a PCI one soon.

    Within a month or so, I'm actually due for motherboard upgrade/replacement because of the Sandy Bridge issue. I'll contact the vendor to see if I can get a new one earlier.

    Meanwhile, if you or anybody have any more info/opinion, please let me know. Also, does anybody understand or know how to fix the multiple boot choice issue?

    Thanks again.


    My specs: * Hardware : Core i7 2500K stock, MSI P67A-GD65, 2x4GB RAM stock, GTX 570 factory overclocked, Corsair 850W PSU, Belkin F5D8053N, Logitech C510 Webcam, Logitech Z623 2.1 speakers * Software : Windows 7 x64 Pro SP1 OEM, Avast free 6.0, Firefox 3.6.13, Skype 5.1.0., lastest drivers for all hardware
    Friday, March 11, 2011 2:23 PM
  • Meanwhile, if you or anybody have any more info/opinion, please let me know. Also, does anybody understand or know how to fix the multiple boot choice issue?
    Run EasyBCD to delete the other entires.

    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Arthur Xie Monday, March 14, 2011 8:58 AM
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Friday, March 11, 2011 3:10 PM
  • Thanks again. I have  used EasyBCD to remove the extra entries. I have also placed an ordering for replacement of my motherboard. Once the new board is setup, I will see if the problem with the wireless adapter remains.

    I will return here to update things. Please feel free to give me more info/advice, etc. And please don't close this thread.


    My specs: * Hardware : Core i7 2500K stock, MSI P67A-GD65, 2x4GB RAM stock, GTX 570 factory overclocked, Corsair 850W PSU, Belkin F5D8053N, Logitech C510 Webcam, Logitech Z623 2.1 speakers * Software : Windows 7 x64 Pro SP1 OEM, Avast free 6.0, Firefox 3.6.13, Skype 5.1.0., lastest drivers for all hardware
    Saturday, March 12, 2011 6:50 PM
  • Hi ntvinh1985, I replied to you in an older post before stumbling upon this one.  I have nearly the same setup (i7 2600k, P67A-GF65, 2x4GB Corsair Vengeance, Corsair 850W PS, Windows 7 Home 64-bit.)  I actually have the B3 stepping which means it is the new board that they will be replacing yours with.  I'm sorry to report that I'm having the same issue that you are.  I'm fairly certain I'm completely up-to-date with everything.  I'm only 2 days into the new setup, so I'm just beginning my diagnosis.  I'll keep you up-to-date with any findings, but I'm very worried as I've seen a few of these reports around the internet with no resolution.  I may just return the board and get something else before my return window closes.
    Monday, March 14, 2011 6:12 PM
  • ntvinh1985, I believe I have the solution to our problem.  I activated the OC Genie feature (turn computer off, push in OC genie button on motherboard, turn computer on) and everything seems stable now.  Someone on another forum mentioned the increase in voltage that occurs when this feature is turned on seems to be required for memory faster than 1333.  I am using 1600 and I suspect you may be using that or faster as well.  Give it a shot.  I've been monitoring processor temps since turning the feature on and I seem to be alright, but I'm going to get a better CPU cooler to be safe.  Hopefully the next few days will prove that the problem is solved for the long haul.
    • Marked as answer by ntvinh1985 Wednesday, April 6, 2011 10:55 AM
    Tuesday, March 15, 2011 3:28 AM
  • Dear Decayo,

    Thank you very much for the posts. We indeed have a very similar setup. I actually have the VERY same kit of RAM that you have! I did try it once but turned it off shortly after because I thought I needed to fix the instability first. I never realized OC Genie itself could be the fix!

    But unfortunately (maybe fortunately!), I'm exchanging this board soon. I got tired with trying to fix all these problems so instead of requesting a B3 revision, I actually bought the ASUS P67 Deluxe. Once that gets here, I will pry this MSI one out and ship it back to the vendor. I just don't want to deal with this particular board (or any of its later revisions) anymore.

    In any case, if you don't mind, please post back here on your progress. I will be very delighted if you have indeed found a fix for our problems.


    My specs: * Hardware : Core i7 2500K stock, MSI P67A-GD65, 2x4GB Corsair Vengence 1600 RAM stock, GTX 570 factory overclocked, Corsair 850W PSU, Belkin F5D8053N, Logitech C510 Webcam, Logitech Z623 2.1 speakers * Software : Windows 7 x64 Pro SP1 OEM, Avast free 6.0, Firefox 3.6.13, Skype 5.1.0., lastest drivers for all hardware
    Tuesday, March 15, 2011 4:42 AM
  • Good luck with the new board, hopefully it works out better for you.  The problem has been fixed.  I haven't had a lockup for 18 hours which has never happened.  It was as simple as activating OC Genie.  If you look on the box or in the manual under Supported Memory types, 1600 and above all have "(OC)" next to them.  I thought this meant that you needed at least that speed in order to overclock, but it must mean that you must overclock in order for the board to support those speeds.  The normal memory voltage must not be good enough for the higher speeds.  Looks like this is just a failure of the MSI documentation.  I'm extremely happy to have my computer working perfectly with the added bonus of a faster processor!
    • Marked as answer by Arthur Xie Thursday, March 24, 2011 8:00 AM
    Tuesday, March 15, 2011 3:53 PM
  • Dear Decayo, thank you a million times! OC Genie did indeed fix my problems. It's been almost 2 weeks now and I haven't had ANY of the original problem. In fact, I haven't had any problem AT ALL! :D :D. I haven't had time to swap the new board in yet but my current issue is finally resolved. A mod can close this thread if he/she likes. Thank you all for helping me.


    My specs: * Hardware : Core i7 2500K stock, MSI P67A-GD65, 2x4GB 1600 Corsair Vengeance RAM stock, GTX 570 factory overclocked, Corsair 850W PSU, Belkin F5D8053N, Logitech C510 Webcam, Logitech Z623 2.1 speakers * Software : Windows 7 x64 Pro SP1 OEM, Avast free 6.0, Firefox 3.6.13, Skype 5.1.0., lastest drivers for all hardware

    Wednesday, April 6, 2011 10:56 AM