BSOD when entering Sleep mode

Page 1 of 4 123 ... LastLast

  1. Posts : 46
    Windows 7 Home Premium 64-bit
       #1

    BSOD when entering Sleep mode


    Hello,

    I recently got a BSOD when I entered Sleep mode.

    I thought a program which I recently installed caused the problem,
    but I got another BSOD when I restarted my computer,
    uninstalled the program and tried entering Sleep mode a second time.

    My second thought was that the power cut today could have caused this problem, but I don't really know.


    I ran WinDbg and got this:


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


    Loading Dump File [C:\Windows\Minidump\032412-20092-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
    Machine Name:
    Kernel base = 0xfffff800`03268000 PsLoadedModuleList = 0xfffff800`034ac650
    Debug session time: Sat Mar 24 20:27:44.980 2012 (UTC + 13:00)
    System Uptime: 0 days 0:08:14.073
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    .....
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\winxp\triage.ini, error 2
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff880016e56a0, 2, 8, fffff880016e56a0}

    *** WARNING: Unable to verify timestamp for wsimdx.sys
    *** ERROR: Module load completed but symbols could not be loaded for wsimdx.sys
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : wsimdx.sys ( wsimdx+7959 )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: fffff880016e56a0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff880016e56a0, address which referenced memory

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

    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003516100
    GetUlongFromAddress: unable to read from fffff800035161c0
    fffff880016e56a0 Nonpaged pool

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff8800a8ce600 -- (.trap 0xfffff8800a8ce600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80061f21a0
    rdx=fffff8800a8ce928 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880016e56a0 rsp=fffff8800a8ce798 rbp=fffff8800a8ce928
    r8=0000000000000000 r9=0000000000000000 r10=fffff880016c5ec0
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    ndis!NdisIMNotifyPnPEvent:
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx ss:fffff880`0a8ce7a0=fffff8800a8cebd4
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800032e42e9 to fffff800032e4d40

    FAILED_INSTRUCTION_ADDRESS:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx

    STACK_TEXT:
    fffff880`0a8ce4b8 fffff800`032e42e9 : 00000000`0000000a fffff880`016e56a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0a8ce4c0 fffff800`032e2f60 : fffffa80`058d8850 20707249`00000000 fffff800`0341ec50 fffffa80`0b53bb80 : nt!KiBugCheckDispatch+0x69
    fffff880`0a8ce600 fffff880`016e56a0 : fffff880`047eb959 fffff880`0a8cebd4 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0a8ce798 fffff880`047eb959 : fffff880`0a8cebd4 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 : ndis!NdisIMNotifyPnPEvent
    fffff880`0a8ce7a0 fffff880`0a8cebd4 : 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 : wsimdx+0x7959
    fffff880`0a8ce7a8 00000000`00000001 : 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 : 0xfffff880`0a8cebd4
    fffff880`0a8ce7b0 00000000`00000001 : fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 : 0x1
    fffff880`0a8ce7b8 fffffa80`0b53bb80 : 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 : 0x1
    fffff880`0a8ce7c0 00000000`00000000 : fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 fffff880`0a8ce928 : 0xfffffa80`0b53bb80


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    wsimdx+7959
    fffff880`047eb959 ?? ???

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: wsimdx+7959

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: wsimdx

    IMAGE_NAME: wsimdx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49bf410b

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: fffff880016e56a0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff880016e56a0, address which referenced memory

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

    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2

    READ_ADDRESS: fffff880016e56a0 Nonpaged pool

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff8800a8ce600 -- (.trap 0xfffff8800a8ce600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80061f21a0
    rdx=fffff8800a8ce928 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880016e56a0 rsp=fffff8800a8ce798 rbp=fffff8800a8ce928
    r8=0000000000000000 r9=0000000000000000 r10=fffff880016c5ec0
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    ndis!NdisIMNotifyPnPEvent:
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx ss:fffff880`0a8ce7a0=fffff8800a8cebd4
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800032e42e9 to fffff800032e4d40

    FAILED_INSTRUCTION_ADDRESS:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx

    STACK_TEXT:
    fffff880`0a8ce4b8 fffff800`032e42e9 : 00000000`0000000a fffff880`016e56a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0a8ce4c0 fffff800`032e2f60 : fffffa80`058d8850 20707249`00000000 fffff800`0341ec50 fffffa80`0b53bb80 : nt!KiBugCheckDispatch+0x69
    fffff880`0a8ce600 fffff880`016e56a0 : fffff880`047eb959 fffff880`0a8cebd4 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0a8ce798 fffff880`047eb959 : fffff880`0a8cebd4 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 : ndis!NdisIMNotifyPnPEvent
    fffff880`0a8ce7a0 fffff880`0a8cebd4 : 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 : wsimdx+0x7959
    fffff880`0a8ce7a8 00000000`00000001 : 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 : 0xfffff880`0a8cebd4
    fffff880`0a8ce7b0 00000000`00000001 : fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 : 0x1
    fffff880`0a8ce7b8 fffffa80`0b53bb80 : 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 : 0x1
    fffff880`0a8ce7c0 00000000`00000000 : fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 fffff880`0a8ce928 : 0xfffffa80`0b53bb80


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    wsimdx+7959
    fffff880`047eb959 ?? ???

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: wsimdx+7959

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: wsimdx

    IMAGE_NAME: wsimdx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49bf410b

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

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


    Please help me.

    Thanks in advance.

    Regards,
    Christian


    PS: Would a System Restore do the trick?
    Last edited by christianb9632; 24 Mar 2012 at 04:11.
      My Computer


  2. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #2

    You could try a System Restore, wouldn't hurt.

    The file wsimdx.sys refers to Atheros Communications, Inc. Wireless Intermediate Miniport Driver that should be updated.

    You can use information from this: https://www.sevenforums.com/crashes-debugging/219284-bsod-error-oa002afx-sys-oa002ufd-sys-ndis-sys.html#post1837607

    Or find them here:
    Atheros Driver Download
    ATHEROS drivers for Microsoft Windows (Atheros?????)
      My Computer


  3. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    I tried a System Restore, but it failed/did not complete;
    an error cause the unsuccessfullness :P
    (0x80071a90)
    I will try updating the ATHEROS driver.

    I have also tried installing internet explorer 9 because I needed it. but an error came up saying there is already an update of internet explorer on the computer. so i uninstalled the update, and tried installing internet explorer again, then i got an error that the intallation was unsuccessful, and now my sidebar does not work (Gadgets) and also Device Manage does not work (an error message come up saying: MMC will not run with a version of Internet Explorer earlier than Internet Explorer 5.5) and I also cannot access the User Account Settings. I cannot find any internet explorer on my computer (so far I can look for it) and I do not understand what this error message [above] has to do with Device Manager.

    Could a virus be a problem? Should I run a Full System Check? I use Norton 360 5.2.0.13

    Please Help.


    Regards,

    Christian
    Last edited by christianb9632; 24 Mar 2012 at 22:45.
      My Computer


  4. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #4

    Could a virus be a problem? Should I run a Full System Check? I use Norton 360 5.2.0.13
    Yes I would.

    You could also try: https://www.superantispyware.com/ the free version, I was going to link MBAM, but I can't connect.

    In the meantime I'll try and track down those errors.
      My Computer


  5. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #5

    Try disabling Norton and run the System Restore again.

    MMC should run if you can run SFC /SCANNOW Command - System File Checker

    Before you do this:
    Do you have SP1 installed? Windows Update error 80071A90
      My Computer


  6. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #6

    Hello,

    Ok, looks like I got this problem with MMC fixed, at first I couldn't install IE9, but I don;t know what happened then, when i tried a 2nd time, it worked, I installed IE9, and the prob with MMC and Device Manager disappeared,...looks like nothing works without proper IE installed...


    But I am still getting the BSODs when I enter Sleep mode.
    I updated the driver, but I am still getting them BSODs....

    Should I try the Retstore again? If I do, then IE will be gone and I will have to reinstall that.

    Or is there a better idea?

    Regards,
    Christian


    PS: This is WinDbg after I updated the Atheros Driver:




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


    Loading Dump File [C:\Windows\Minidump\032512-24382-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
    Machine Name:
    Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a7650
    Debug session time: Sun Mar 25 16:31:21.425 2012 (UTC + 13:00)
    System Uptime: 0 days 0:02:08.518
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    ....
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\winxp\triage.ini, error 2
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff880014876a0, 2, 8, fffff880014876a0}

    *** WARNING: Unable to verify timestamp for wsimdx.sys
    *** ERROR: Module load completed but symbols could not be loaded for wsimdx.sys
    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : wsimdx.sys ( wsimdx+7959 )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: fffff880014876a0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff880014876a0, address which referenced memory

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

    TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2

    READ_ADDRESS: fffff880014876a0 Nonpaged pool

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`014876a0 48895c2408 mov qword ptr [rsp+8],rbx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff88003cd2600 -- (.trap 0xfffff88003cd2600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800652c1a0
    rdx=fffff88003cd2928 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880014876a0 rsp=fffff88003cd2798 rbp=fffff88003cd2928
    r8=0000000000000000 r9=0000000000000000 r10=fffff88001467ec0
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    ndis!NdisIMNotifyPnPEvent:
    fffff880`014876a0 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffff880`03cd27a0=fffff88003cd2bd4
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800032df2e9 to fffff800032dfd40

    FAILED_INSTRUCTION_ADDRESS:
    ndis!NdisIMNotifyPnPEvent+0
    fffff880`014876a0 48895c2408 mov qword ptr [rsp+8],rbx

    STACK_TEXT:
    fffff880`03cd24b8 fffff800`032df2e9 : 00000000`0000000a fffff880`014876a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`03cd24c0 fffff800`032ddf60 : fffffa80`06fd1de8 fffffa80`0b34b500 fffffa80`03bb0000 fffffa80`0b043b80 : nt!KiBugCheckDispatch+0x69
    fffff880`03cd2600 fffff880`014876a0 : fffff880`046ba959 fffff880`03cd2bd4 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`03cd2798 fffff880`046ba959 : fffff880`03cd2bd4 00000000`00000000 00000000`00000001 fffffa80`0b043b80 : ndis!NdisIMNotifyPnPEvent
    fffff880`03cd27a0 fffff880`03cd2bd4 : 00000000`00000000 00000000`00000001 fffffa80`0b043b80 00000000`00000000 : wsimdx+0x7959
    fffff880`03cd27a8 00000000`00000000 : 00000000`00000001 fffffa80`0b043b80 00000000`00000000 00000000`00000000 : 0xfffff880`03cd2bd4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    wsimdx+7959
    fffff880`046ba959 ?? ???

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: wsimdx+7959

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: wsimdx

    IMAGE_NAME: wsimdx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49bf410b

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959

    Followup: MachineOwner
    ---------
    Last edited by christianb9632; 24 Mar 2012 at 22:45.
      My Computer


  7. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #7

    After going over your Dbg reports I see BUGCHECK_STR: 0xD1 listed.

    Researching here: BSOD Index you have to scroll down to where it applies to win7 systems, I found this:

    There is a hotfix available for this here: Stop error message when you resume a computer that is running Windows 7 or Windows Server 2008 R2 from sleep or from hibernation: "Stop error code 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)", but go over the Resolution section before applying to see if it applies to you.

    If you do apply it create a restore point before hand in case of further problems, that way you can get back to square one.

    It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the https://www.sevenforums.com/crashes-d...tructions.html, Found at the top of all BSOD threads.
      My Computer


  8. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #8

    Anak said:
    It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the https://www.sevenforums.com/crashes-d...tructions.html, Found at the top of all BSOD threads.

    [Attached]


    Regards,
    Christian
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #9

    christianb9632 said:
    Anak said:
    It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the https://www.sevenforums.com/crashes-d...tructions.html, Found at the top of all BSOD threads.

    [Attached]


    Regards,
    Christian
    Related to Wireless Intermediate Miniport Driver is a driver file from company Atheros Communications, Inc. belonging to product Wireless Intermediate Miniport Driver.

    Yours is from 3/2009. I would update to most recent available.
      My Computer


  10. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #10

    zigzag3143 said:
    christianb9632 said:
    Anak said:
    It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the https://www.sevenforums.com/crashes-d...tructions.html, Found at the top of all BSOD threads.

    [Attached]


    Regards,
    Christian
    Related to Wireless Intermediate Miniport Driver is a driver file from company Atheros Communications, Inc. belonging to product Wireless Intermediate Miniport Driver.

    Yours is from 3/2009. I would update to most recent available.

    Hello,

    I have done the same as last time I had this problem.
    I tried updating the driver, (I downloaded a new driver from ... (can't remember website) but after I restarted the computer, internet has stopped working, so I went into Device Manager, and uninstalled the driver that didn't work, from there (ATHEROS driver).
    After another restart windows automatically installed a driver for ATHEROS and internet started working again...
    This is where I am now.

    (I am saving all my necessary files on an external drive just in case)


    Regards,
    Christian


    PS: In another article, I read that reformatting would do the trick but I do not know how to do this nor if this would do anything to this problem
    (Getting a STOP 0x000000D1 error - Microsoft Answers)
    Last edited by christianb9632; 26 Mar 2012 at 01:50. Reason: I did have done the same... FAIL xD
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:18.
Find Us