locked
BSODs on a brand-new machine RRS feed

  • Question

  • Hi all,

    I just built a new computer (specs below) and installed Windows 7 x64 Pro on it. I have everything updated daily. So far I have had a few BSOD's and a few other weird behaviors, which are:

     

    (1) The BSOD's: (I have uploaded the minidump files to skydrive .) I think a few of these happened when the machine was idle. I have no clues what caused the BSOD's.

    (2) Even after I installed the driver for the Asus Wireless Adapter USB N13 and plugged the adapter in, it wasn't immediately recognized by Windows. I had to do a reset for the device to be recognized. I have since updated to the newest driver, found on ASUS's site. Still, these days, the adapter randomly turns off or gets disabled by Windows. When I saw the adapter misbehaving, I restarted my computer but then the machine hung at "Shutting down ...", which forced me to press the physical button for reset. Fortunately though, when the machine was back to Windows, the adapter was already working again or only required an enabling from me. It would work fine for a few days. Then the trouble resurfaced.

    (3) I had 2 nasty freezes when obnoxious screeching noise was coming out of my speakers. At both times, someone was trying to send me an IM on skype. And at both times, I pressed the Reset button to restart the computer. I have disabled the IM notification sound effect from Skype and the problem hasn't returned.

    (4) Whenever I play Crysis or Crysis Warhead in DX10 mode, I got RAM leakage, which usually froze the games at around 20 minutes into playing. At the instances of freezing, the games were consuming north of 6.5GB of RAM. This happened regardless of whether I was playing in 32-bit mode or 64-bit mode, with or without Vista SP2 compatibility setting. I have tried playing L4D, L4D2, Battlefield 2: Bad Company but no errors here.

    So, someone with knowledge or experience, please shine me with some light on what is going on. This machine is my main work/entertainment machine and it hasn't even celebrated its 1-week birthday yet!

    Specs (for diagnosis purposes)

    Hardware:

    • CPU: Core i7 2500K @ stock
    • RAM: Corsair Vengeance 2x4GB DDR3 1600 @ 1600MHz
    • Motherboard: MSI P67A-GD65, lastest firmware
    • PSU: Corsair HX850W
    • GPU: EVGA GTX 570 Superclocked @ factory overclocked state
    • HDD's: 1 OCZ Vertex 2 extended + 1 Western Digital Green plugged into the Intel controller and 1 Western Digital Black plugged into the Marvell controller. Both controller have the SATA mode set to AHCI. The SSD has the latest firmware
    • Nvidia 3D Vision Controller always plugged into a USB port
    • Wireless adapter: ASUS USB N13

    Software:

    • Windows 7 Pro x64 OEM, up-to-dated
    • Microsoft security essentials 2.0, up-to-dated
    • Other software: Fraps, EVGA precision, core temp, skype 5.0, All CPU gadget, skype 5.0
    Sorry for the long post. I tried to be as detailed as I can.
    Thursday, January 20, 2011 1:44 AM

Answers

  • 0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    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.
    Arg3: fffffa8006d09680, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c4d0

    Debugging Details:
    ------------------


    DRVPOWERSTATE_SUBCODE:  4

    FAULTING_THREAD:  fffffa8006d09680

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80002c80052 to fffff80002c7edda

    STACK_TEXT: 
    fffff880`031c3f30 fffff800`02c80052 : fffffa80`06d09680 fffffa80`06d09680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`031c4070 fffff800`02c821af : fffffa80`0823b400 fffffa80`07fff010 fffffa80`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`031c4100 fffff880`00e76320 : fffff880`031c4200 fffffa80`00000000 fffff880`031c4200 fffff880`00e66d00 : nt!KeWaitForSingleObject+0x19f
    fffff880`031c41a0 fffff880`00e6703a : fffffa80`07428ad0 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxUsbPipe::WaitForSentIoToComplete+0x124
    fffff880`031c41f0 fffff880`00e62dbc : 00000000`00000001 00000000`00000001 fffffa80`09762906 00000000`00000000 : Wdf01000!FxIoTarget::Stop+0x4e
    fffff880`031c4230 fffff880`09644134 : fffffa80`07428ad0 00000000`00000006 00000000`00000000 fffffa80`0000035d : Wdf01000!imp_WdfIoTargetStop+0x128
    fffff880`031c4280 fffffa80`07428ad0 : 00000000`00000006 00000000`00000000 fffffa80`0000035d fffff880`01468310 : netr28ux+0x1134
    fffff880`031c4288 00000000`00000006 : 00000000`00000000 fffffa80`0000035d fffff880`01468310 fffff880`09645099 : 0xfffffa80`07428ad0
    fffff880`031c4290 00000000`00000000 : fffffa80`0000035d fffff880`01468310 fffff880`09645099 0000057f`f8bd7528 : 0x6


    STACK_COMMAND:  .thread 0xfffffa8006d09680 ; kb

    FOLLOWUP_IP:
    netr28ux+1134
    fffff880`09644134 ??              ???

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  netr28ux+1134

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: netr28ux

    IMAGE_NAME:  netr28ux.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a799052

    FAILURE_BUCKET_ID:  X64_0x9F_netr28ux+1134

    BUCKET_ID:  X64_0x9F_netr28ux+1134

    Followup: MachineOwner

    ------------------------------------------------------------------------------------------

    Bug Check Code 0x9F: The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.

    For more information, refer to this Microsoft article.

    netr28ux.sys is a Ralink 802.11n Wireless Adaptor Driver. Please update it and check if this solve your problem.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    • Proposed as answer by Andre.Ziegler Thursday, January 20, 2011 1:12 PM
    • Marked as answer by Nicholas Li Wednesday, February 2, 2011 3:15 AM
    Thursday, January 20, 2011 4:00 AM

All replies

  • 0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    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.
    Arg3: fffffa8006d09680, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c4d0

    Debugging Details:
    ------------------


    DRVPOWERSTATE_SUBCODE:  4

    FAULTING_THREAD:  fffffa8006d09680

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80002c80052 to fffff80002c7edda

    STACK_TEXT: 
    fffff880`031c3f30 fffff800`02c80052 : fffffa80`06d09680 fffffa80`06d09680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`031c4070 fffff800`02c821af : fffffa80`0823b400 fffffa80`07fff010 fffffa80`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`031c4100 fffff880`00e76320 : fffff880`031c4200 fffffa80`00000000 fffff880`031c4200 fffff880`00e66d00 : nt!KeWaitForSingleObject+0x19f
    fffff880`031c41a0 fffff880`00e6703a : fffffa80`07428ad0 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxUsbPipe::WaitForSentIoToComplete+0x124
    fffff880`031c41f0 fffff880`00e62dbc : 00000000`00000001 00000000`00000001 fffffa80`09762906 00000000`00000000 : Wdf01000!FxIoTarget::Stop+0x4e
    fffff880`031c4230 fffff880`09644134 : fffffa80`07428ad0 00000000`00000006 00000000`00000000 fffffa80`0000035d : Wdf01000!imp_WdfIoTargetStop+0x128
    fffff880`031c4280 fffffa80`07428ad0 : 00000000`00000006 00000000`00000000 fffffa80`0000035d fffff880`01468310 : netr28ux+0x1134
    fffff880`031c4288 00000000`00000006 : 00000000`00000000 fffffa80`0000035d fffff880`01468310 fffff880`09645099 : 0xfffffa80`07428ad0
    fffff880`031c4290 00000000`00000000 : fffffa80`0000035d fffff880`01468310 fffff880`09645099 0000057f`f8bd7528 : 0x6


    STACK_COMMAND:  .thread 0xfffffa8006d09680 ; kb

    FOLLOWUP_IP:
    netr28ux+1134
    fffff880`09644134 ??              ???

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  netr28ux+1134

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: netr28ux

    IMAGE_NAME:  netr28ux.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a799052

    FAILURE_BUCKET_ID:  X64_0x9F_netr28ux+1134

    BUCKET_ID:  X64_0x9F_netr28ux+1134

    Followup: MachineOwner

    ------------------------------------------------------------------------------------------

    Bug Check Code 0x9F: The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.

    For more information, refer to this Microsoft article.

    netr28ux.sys is a Ralink 802.11n Wireless Adaptor Driver. Please update it and check if this solve your problem.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    • Proposed as answer by Andre.Ziegler Thursday, January 20, 2011 1:12 PM
    • Marked as answer by Nicholas Li Wednesday, February 2, 2011 3:15 AM
    Thursday, January 20, 2011 4:00 AM
  • Thanks a lot. I was suspecting that damn wireless adapter as well. Yeah Ralink 202.11n is the ASUS adapter. Which minidump was this that you looked at?

     

     

    Thursday, January 20, 2011 1:05 PM
  • Hi

     

    I am currently standing by for an update from you and would like to know how things are going. Have you updated the wireless driver? If you have any feedback, please feel free to let us know.

     

    Regards,
    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, January 28, 2011 1:17 AM
  • Hi everybody and Niki, in particular,

    I apologize I haven't updated recently. The work from the university sucked me dry in the recent days.

    Since my last post, I have reinstalled Windows and the driver for the wireless adapter ASUS USB N13. I stopped getting BSODs for a while but my internet connection was very intermittent and from time to time, I still got these non BSOD-crashes that produced ridiculously high-pitched screeching noise. Well so 2 days ago, I changed my wireless adapter to a TP-Link TL-WN822N and got a much more stable connection. But unfortunately, today I got another BSOD. I have posted about it here:

    http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/4a9284f8-74d3-4828-a984-dbb3d9c86f5e

    If anybody is interested and has some time, please help me. Thanks!

    p.s. Happy Lunar New Year!

    Thursday, February 10, 2011 3:31 AM