none
BSOD's in Win 7 64bit

    Question

  •  

    Hi all,

    i need a hint/advice regarding this BSOD's which i get on a Sony VAIO VGN-Z51WG . All hardware tests were and are OK.
    It was send once in service because of the same behavior and still has this problem : when it is powered from stand by state, randomly give this BSOD

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

    Additional information about the problem:
    BCCode: 1000009f
    BCP1: 0000000000000004
    BCP2: 0000000000000258
    BCP3: FFFFFA800551C680
    BCP4: FFFFF800043294D0
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Dump files: http://cid-03c69d8d2828f7fc.skydrive.live.com/self.aspx/.Public/DumpsWin764bit.zip

    Wednesday, June 02, 2010 8:07 AM

Answers

  • Hi,

     

    It  is the error with DRIVER_POWER_STATE_FAILURE. To resolve it, you need to use a tool named Driver Verifier to monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that mignt corrupt the system. For details, please refer to:

    Driver Verifier

    If the issue persists, It is recommended to contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Best Regards

    Dale

     

    Wednesday, June 02, 2010 8:53 AM
  • The old dumps seem to indicate the same as the new.  The qcusbnetsny.sys driver is old and should be updated or removed to test the issue.

     FWIW, there are a variety of stale drivers on the system, that are from before the RTM of Windows 7.  So there could certainly be some compatibility issue:

    lmimirr.sys 4/10/2007 

    SFEP.sys 8/3/2007 

    SonyPI.sys 8/3/2007

    RaInfo.sys 1/4/2008 

    qcfiltersny.sys 5/12/2008

    LMIRfsDriver.sys 7/14/2008 

    shpf.sys 8/22/2008 

    CAX_CNXT.sys 2/13/2009 

    CAXHWAZL.sys 2/13/2009 

    CAX_DPV.sys 2/13/2009 

    btwl2cap.sys 4/3/2009 

    qcusbsersny.sys 4/8/2009 

    qcusbnetsny.sys 4/8/2009 

    XAudio64.sys 4/29/2009

    PxHlpa64.sys 5/15/2009

    RTKVHD64.sys 5/22/2009

    rimssn64.sys 6/10/2009 

    risdsn64.sys 6/11/2009 

    e1y62x64.sys 6/12/2009 

    Apfiltr.sys 6/16/2009 

    btwavdt.sys 6/25/2009 

    btwrchid.sys 6/25/2009 

    btwaudio.sys 7/1/2009 


    For dealing with Blue Screens, general guidance follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    Wednesday, June 02, 2010 10:49 PM

All replies

  • Hi,

     

    It  is the error with DRIVER_POWER_STATE_FAILURE. To resolve it, you need to use a tool named Driver Verifier to monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that mignt corrupt the system. For details, please refer to:

    Driver Verifier

    If the issue persists, It is recommended to contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Best Regards

    Dale

     

    Wednesday, June 02, 2010 8:53 AM
  • Your [Qualcomm/USB networking/Sony ("QCUSB")]? device/driver seems to be responsible for the problems.  In all but one dump, the driver qcusbnetsny.sys from April 8 2009 was in the stack.  The other dump implicated another USB driver but that may have been a side effect of something the qcusbnetsny driver was involved in.  The dumps suggest one-bit memory corruption which is most frequently associated with faulty RAM, but in this case the consistency of the problem combined with the age of the driver strongly suggests you need to get an update to this driver, or remove it from your system.
    • Proposed as answer by No.Compromise Wednesday, June 02, 2010 11:17 AM
    Wednesday, June 02, 2010 11:17 AM
  • Hi,

    thank you all for your answers. The only drivers installed are the one provided by Sony Update. First time i analyse this errors i also assume qualcomm device is not working properly ( this is the internal HSPDA 3G modem / internal UMTS card ). Please see the attached older dump's of the same system(before going to service) but when it came back from service, on the paper they give me it is written at the hardware replaced list: "Others:HSPDA, ifx498" ( i don't know if that means replaced or repaired; what should be ifx498?!)

    We have about 6 laptop's same configuration hardware and software ( we have a software standard ) and none of them have this kind of problems. The system has been reinstalled from scratch about 4 times until now but same problem persist.

    http://cid-03c69d8d2828f7fc.skydrive.live.com/self.aspx/.Public/sony-dumps%5E_OLD.zip

    If you have any other clue please share.

    Thank you!

    Wednesday, June 02, 2010 11:55 AM
  • SkyDrive seems to be having problems now so I can't get at the "OLD" dumps.

    Compare the version of the qcusbnetsny.sys on the affected system with the driver on the systems that do not have this problem.  The driver on the affected system is from April 8 2009, many months before Windows 7 RTM'd and there could be a compatibility issue.  If it's not that driver, it's likely faulty RAM due to the one-bit corruption that was detected.  Since you have many systems on hand, to test that shouldn't be a problem - swap RAM modules from two systems (the affected system, and another that is not experiencing the problem) around.

    • Edited by No.Compromise Wednesday, June 02, 2010 4:54 PM clarify
    Wednesday, June 02, 2010 12:14 PM
  • The old dumps seem to indicate the same as the new.  The qcusbnetsny.sys driver is old and should be updated or removed to test the issue.

     FWIW, there are a variety of stale drivers on the system, that are from before the RTM of Windows 7.  So there could certainly be some compatibility issue:

    lmimirr.sys 4/10/2007 

    SFEP.sys 8/3/2007 

    SonyPI.sys 8/3/2007

    RaInfo.sys 1/4/2008 

    qcfiltersny.sys 5/12/2008

    LMIRfsDriver.sys 7/14/2008 

    shpf.sys 8/22/2008 

    CAX_CNXT.sys 2/13/2009 

    CAXHWAZL.sys 2/13/2009 

    CAX_DPV.sys 2/13/2009 

    btwl2cap.sys 4/3/2009 

    qcusbsersny.sys 4/8/2009 

    qcusbnetsny.sys 4/8/2009 

    XAudio64.sys 4/29/2009

    PxHlpa64.sys 5/15/2009

    RTKVHD64.sys 5/22/2009

    rimssn64.sys 6/10/2009 

    risdsn64.sys 6/11/2009 

    e1y62x64.sys 6/12/2009 

    Apfiltr.sys 6/16/2009 

    btwavdt.sys 6/25/2009 

    btwrchid.sys 6/25/2009 

    btwaudio.sys 7/1/2009 


    For dealing with Blue Screens, general guidance follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    Wednesday, June 02, 2010 10:49 PM