Results 1 to 9 of 9

Thread: Windows 7 BSOD 9F-3

  1. #1
    thom_little Guest

    Default Windows 7 BSOD 9F-3

    I have gotten 13 BSODs on two hachines runnnig Windows 7 and ZAES 9.1.008.000 on a 64-bit machine. Is this a possible ZAES problem? The Minidump flags ... b57nd60a.sys ... and that driver was reinstalled. The Minidump is ...

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Thom Little\Desktop\Mini Dump\012410-38625-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
    Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c8ee50
    Debug session time: Sun Jan 24 13:16:20.690 2010 (GMT-5)
    System Uptime: 0 days 14:53:15.546
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    .................................
    Loading User Symbols
    Loading unloaded module list
    ........
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800a3c7060, fffff80000b9c518, fffffa800c7cc950}

    *** WARNING: Unable to verify timestamp for b57nd60a.sys
    *** ERROR: Module load completed but symbols could not be loaded for b57nd60a.sys
    Probably caused by : b57nd60a.sys

    Followup: MachineOwner
    ---------

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

    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
    Arg2: fffffa800a3c7060, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa800c7cc950, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE: 3

    IRP_ADDRESS: fffffa800c7cc950

    DEVICE_OBJECT: fffffa800cad1050

    DRIVER_OBJECT: fffffa800ca6d800

    IMAGE_NAME: b57nd60a.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a1f410f

    MODULE_NAME: b57nd60a

    FAULTING_MODULE: fffff88004281000 b57nd60a

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff80002b31e23 to fffff80002ac2f00

    STACK_TEXT:
    fffff800`00b9c4c8 fffff800`02b31e23 : 00000000`0000009f 00000000`00000003 fffffa80`0a3c7060 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02acefa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
    fffff800`00b9c570 fffff800`02ace326 : fffff800`02c71700 00000000`00346c45 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02acee7e : 0000007c`c96f5f03 fffff800`00b9cc58 00000000`00346c45 fffff800`02c3eb28 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02ace697 : 0000001e`cb7ff8c1 0000001e`00346c45 0000001e`cb7ff8da 00000000`00000045 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02acb6fa : fffff800`02c3be80 fffff800`02c49c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    FAILURE_BUCKET_ID: X64_0x9F_IMAGE_b57nd60a.sys

    BUCKET_ID: X64_0x9F_IMAGE_b57nd60a.sys

    Followup: M

  2. #2
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,288

    Default Re: Windows 7 BSOD 9F-3

    Hi!
    This seems not to point to any relevant ZA file. The file causing problems is linked to your network adapter (VISTA driver on a WIN7)?. For example see here. No other suggestion than updating you network drivers.

    Cheers,
    Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

  3. #3
    thom_little Guest

    Default Re: Windows 7 BSOD 9F-3

    I agree with you. The drivers were changed on two different occasions by my computer supplier. I still get the problem.

    There is a later driver listed on the network interface vendor website. I am checking wiuth my computer supplier about its installation.

    The reason I was asking was that I have another problem in another forum here where I can not communcate with a SmartPhone using Windows Mobile Device Center unless ZoneAlarm is shut down. (This problem is still pending.)

    Iit seemed possible that the BSOD problem was in the ZoneAlarm arena also.

    ... Thom

  4. #4
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,288

    Default Re: Windows 7 BSOD 9F-3

    Ok Thanks.... for the other problem, if you see no other reaction from users here then better to contact the official support. Link in my signature.

    Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

  5. #5
    thom_little Guest

    Default Re: Windows 7 BSOD 9F-3

    I chatted with ZA Tech Support. I am running the ZA unistall package and will leave ZA off for three days. This will determine if ZA is part of the problem.

    This information was shared with my hardware vendor.

    ... Thom

  6. #6
    thom_little Guest

    Default Re: Windows 7 BSOD 9F-3

    ZAES was uninstalled for 3.5 days and there were no 9F-3 BSODs. At the request of ZA Tech Support I installed the ZAES Beta and will run with it for at lleast three days.

    Without ZAES installed I could, of course, sync my HP Smartphone with Outlook on my Windows 7 machine. Now that the Beta is installed that syncing no longer works.

  7. #7
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,288

    Default Re: Windows 7 BSOD 9F-3

    Great! Remember to feeback the ZA beta team of the problem.

    Cheers,
    Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

  8. #8
    thom_little Guest

    Default Re: Windows 7 BSOD 9F-3

    I had ZAES Beta 9.1.118 installed for four days and I then got a 9F_3 BSOD. I have unistalled ZAES and will see how long I can go without a 9F_3 BSOD.

  9. #9
    Join Date
    Nov 2004
    Location
    localhost
    Posts
    17,288

    Default Re: Windows 7 BSOD 9F-3

    Hi!
    to avoid wrong section posting and repetitions of the same issue please continue on the new thread you just created:
    http://forums.zonealarm.com/showthread.php?t=73046

    I am closing this one.

    Thanks,
    Fax

    Click here for ZA Support
    Monday-Saturday 6am to 10pm Central time
    Closed Sundays and Holidays

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •