locked
wlan autoconfig service causes blue screen RRS feed

  • Question

  • Hello, i get the bluescreen after i have type in this comment in cmd.exe.
    "netsh wlan set hostednetwork mode=allow", the computer turn bluescreen
    Everytime i restart the computer, I was able to go as far as the windows logon screen, and after a certain point in the startup sound it started to become bluescreen.
    I have disable the wlan autoconfig service in safemode, and everything go fine, except for the wifi detector,
    what should i do to enable walan autoconfig service?
    i have tried to set "netsh wlan set hostednetwork mode=disallow", but it wont work because the wlansvc is not started, once i started it, my computer turn blue screen.
    i have not backup the system since i installed window 7.
    is there any solution?

    THANKS IN ADVANCE

    • Changed type littlek4za Monday, June 18, 2012 12:35 AM Wrong Section
    Monday, June 18, 2012 12:31 AM

Answers

  • Hi,

    After check your mini dump, the analyze result below:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    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 kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: 0000000000000010, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

    Arg4: fffff880018e55d6, address which referenced memory

    Debugging Details:

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

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c60e0

     0000000000000010

    CURRENT_IRQL:  2

    FAULTING_IP:

    ndis!NdisFreeTimerObject+16

    fffff880`018e55d6 488b5310        mov     rdx,qword ptr [rbx+10h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff880033cb8b0 -- (.trap 0xfffff880033cb8b0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800191c908

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff880018e55d6 rsp=fffff880033cba40 rbp=fffff800032335a0

     r8=0000000000011120  r9=0000000000000000 r10=fffff8000301f000

    r11=fffffa8007b40cb0 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei ng nz na pe nc

    ndis!NdisFreeTimerObject+0x16:

    fffff880`018e55d6 488b5310        mov     rdx,qword ptr [rbx+10h] ds:6040:00000000`00000010=????????????????

    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff8000308e5a9 to fffff8000308f040

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    athrx+47677

    fffff880`04eef677 ??              ???

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  athrx+47677

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: athrx

    IMAGE_NAME:  athrx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

    FAILURE_BUCKET_ID:  X64_0xD1_athrx+47677

    BUCKET_ID:  X64_0xD1_athrx+47677

    Followup: MachineOwner

    ---------

    About bugcheck 0xD1, please refer this article:

    http://msdn.microsoft.com/en-us/library/ff560244(v=vs.85)

    And please update the driver of your wireless card, also update BIOS and chipset to the latest version.

    If the issue persists, , I suggest that you can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, June 25, 2012 8:56 AM
    Tuesday, June 19, 2012 4:02 AM

All replies

  • Without analysing minidump I could not say anything specific. For first help use Nirsoft blue screen viewer. For deeper analysis use Microsoft debug tools (WinDBG).

    Regards

    Milos

    Monday, June 18, 2012 7:37 AM
  • <title>Crash List</title>

    Crash List


    Created by using BlueScreenView

    Dump File 061812-19671-01.dmp
    Crash Time 18/6/2012 12:30:38 AM
    Bug Check String DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code 0x000000d1
    Parameter 1 00000000`00000010
    Parameter 2 00000000`00000002
    Parameter 3 00000000`00000000
    Parameter 4 fffff880`018e55d6
    Caused By Driver ndis.sys
    Caused By Address ndis.sys+2e5d6
    File Description  
    Product Name  
    Company  
    File Version  
    Processor x64
    Crash Address ntoskrnl.exe+70040
    Stack Address 1  
    Stack Address 2  
    Stack Address 3  
    Computer Name  
    Full Path C:\Windows\Minidump\061812-19671-01.dmp
    Processors Count 2
    Major Version 15
    Minor Version 7600
    Dump File Size 273,184

    Monday, June 18, 2012 9:38 AM
  • is this the one u needed?

    Monday, June 18, 2012 9:39 AM
  • this one is the dmp file
    https://skydrive.live.com/redir?resid=D10B2D5F6B18553F!175&authkey=!ALSh5NlO-hYleVc
    Monday, June 18, 2012 9:43 AM
  • Thanks for listing. It points to driver problem. I would contact vendors support and ask driver that support required WLAN properties. For more on WLAN hosted networks read here http://msdn.microsoft.com/en-us/library/windows/desktop/dd815243(v=vs.85).aspx

    Regards

    Milos

    Monday, June 18, 2012 10:54 AM
  • Hi,

    After check your mini dump, the analyze result below:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    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 kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: 0000000000000010, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

    Arg4: fffff880018e55d6, address which referenced memory

    Debugging Details:

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

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c60e0

     0000000000000010

    CURRENT_IRQL:  2

    FAULTING_IP:

    ndis!NdisFreeTimerObject+16

    fffff880`018e55d6 488b5310        mov     rdx,qword ptr [rbx+10h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff880033cb8b0 -- (.trap 0xfffff880033cb8b0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800191c908

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff880018e55d6 rsp=fffff880033cba40 rbp=fffff800032335a0

     r8=0000000000011120  r9=0000000000000000 r10=fffff8000301f000

    r11=fffffa8007b40cb0 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei ng nz na pe nc

    ndis!NdisFreeTimerObject+0x16:

    fffff880`018e55d6 488b5310        mov     rdx,qword ptr [rbx+10h] ds:6040:00000000`00000010=????????????????

    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff8000308e5a9 to fffff8000308f040

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    athrx+47677

    fffff880`04eef677 ??              ???

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  athrx+47677

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: athrx

    IMAGE_NAME:  athrx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

    FAILURE_BUCKET_ID:  X64_0xD1_athrx+47677

    BUCKET_ID:  X64_0xD1_athrx+47677

    Followup: MachineOwner

    ---------

    About bugcheck 0xD1, please refer this article:

    http://msdn.microsoft.com/en-us/library/ff560244(v=vs.85)

    And please update the driver of your wireless card, also update BIOS and chipset to the latest version.

    If the issue persists, , I suggest that you can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, June 25, 2012 8:56 AM
    Tuesday, June 19, 2012 4:02 AM
  • Thank you for helping me.. 
    last question..
    can it be solved by formatting the computer?
    Tuesday, June 19, 2012 6:47 AM
  • Hi,

    That’s seem the wireless card driver related issue, not system files corrupted.

    I suggest to test it on Safe Mode first.

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    Tuesday, June 19, 2012 7:19 AM
  • i checked from the manufacture website and found that my driver is the latest, do you mean try to reinstalling the driver in safe mode?
    i try it but still the same,
    is it related to this command? "netsh wlan set hostednetwork mode=allow"
    i have done this and straight away the computer become bluescreen..
    Tuesday, June 19, 2012 5:19 PM
  • If the issue persists, I suggest that you can contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

    Thank you for your understanding.

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    Thursday, June 21, 2012 2:43 AM