BSOD when entering Sleep mode

[christianb9632]

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?

 

[Anak]

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: http://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?????)

 

[christianb9632]

I tried a System Restore, but it failed/did not complete;
an error cause the unsuccessfullness
(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

 

[Anak]

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.

 

[Anak]

Try disabling Norton and run the System Restore again.

MMC should run if you can run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

 

[christianb9632]

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
---------

 

[Anak]

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 http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, Found at the top of all BSOD threads.

 

[christianb9632]

It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, Found at the top of all BSOD threads.

[Attached]


Regards,
Christian

 

[zigzag3143]

It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.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.

 

[christianb9632]

It is appreciated that you can supply a WinDbg report, but in the future it would be more helpful if you could run the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.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)

 

[Anak]

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)

Did you discount the hotfix link I posted in my #7 reply?

 

[christianb9632]

[/QUOTE]Did you discount the hotfix link I posted in my #7 reply?[/QUOTE]

I don't know if it's the right one.
My problem is that my computer crashes (BSOD) when I enter Sleep mode, so basically I am not even in Sleep mode yet, and it crashes.
But the Hotfix which you gave me states that the computer crashes when you resume windows from Sleep mode.
And it also says:
"However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article."
So, I am not sure now.


Regards,
Christian

 

[Anak]

I don't know if it's the right one.

So, I am not sure now.

Regards,
Christian

Fair enough,

I looked over your startup Items, and one thing I notice is you have an abundance of wireless/networking helpers.

I would like you to disable the two I have boxed in red. They are related to the wsimdx.sys file.
View attachment 204598

Please follow Method Three here: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Then check to see if you still BSOD before entering sleep.

If you still have problems, disable, and check one at a time the ones I have underlined in green.

Meanwhile, when I get time I will go over your reports, and post back.

 

[christianb9632]

Ok,
I've tried everything.
I disabled the ones you marked in red boxes.
I unchecked and checked one at a time the ones you underlined green.
I even disabled them all (the ones you marked in red and the ones in green)
At the moment they are all disabled (" ^ " ^ " ^ " ^ " ^ " ^ " ^ " ^ " ^ ")

Any other ideas?

Regards,
Christian


(Just in case [ATTACHED])

 

[Anak]

Not at the present time. I will ask for more help on another thread we have, please be patient.


EDIT:
I know you loose your internet connection when you update that driver, but have you tried to see if you still BSOD going into sleep with it installed?

 

[christianb9632]

Okay, I have tried that, and I do not get any BSODs when I have the updated driver and enter Sleep mode, but remember, I cannot access the internet unless I uninstall the driver through Device Manager, and let windows reinstall it again (and I guess windows installs a old drvier).

Regards,
Christian

PS: Could buying a new PCI wireless adapter fix this problem?
I was going to buy one anyway, because I don't like my present one (slow, bad connection)

 

[Anak]

Okay, I have tried that, and I do not get any BSODs when I have the updated driver and enter Sleep mode, but remember, I cannot access the internet unless I uninstall the driver through Device Manager, and let windows reinstall it again (and I guess windows installs a old drvier).

Regards,
Christian

Good, now we're getting somewhere. I only wanted you to run a test.
Did you not have a eureka moment when your machine went to sleep without the BSOD?

There is coding that neither your system likes (The old drivers, you get those BSOD's) or the card doesn't like (The new drivers, you can't connect to the internet ).
Are you sure you are using drivers that are bit compatible with your win7x64 system?

Did this card come with your machine or did you install it? It may not be Dell compatible.

I have heard of users using drivers that are system compatible, but are for a different atheros card. But you run the risk of performance issues, and it gets to be a pain trying all those drivers.

You know the 03/2009 driver date, and the newest doesn't work, so you would have to try, and find one within those dates that does. But you could still strike out.


If your really thinking of doing this:

PS: Could buying a new PCI wireless adapter fix this problem?
I was going to buy one anyway, because I don't like my present one (slow, bad connection)

I would say, go for it, but stay away from atheros. You need to ask what WLAN Cards are Dell compatible. Probably wouldn't have to spend more than $30-50 GST.

Your Dell can handle a PCI Express WiFi card supporting 802.11a/b/g/n | Dell™ Inspiron™ 580 Comprehensive Specifications

You may want to bookmark this Manual:
Dell™ Inspiron™ 580s Service Manual | Removing Replacing PCI and PCI Express Cards

Some sites I found in NZ for WLAN Cards:
Computer Hardware and Component Supplier : Ascent Technology

Wireless Category - Zcom Computer Ltd - One of the largest computer parts importers in New Zealand.

PB Tech - Computer Parts, PC Components, Laptop Computers, LCD Monitors, Tablets and more!

ETC Computers::New Zealand Computer Store with Top Quality at The Best Prices

 

[christianb9632]

eureka? what does that mean? when I went to sleep with new drivers, everything was normal (as it should be)

How do i find out if the drivers i use are bit compatible?

The card did not come with the machine. I installed this card. It's a:
DSE XH9946 WLAN 802.11g PCI Adaptor
I have been using this card for over a year if not more, and the BSODs only started about a month ago or so.

I had some Perfomance issues the first few times I had BSODs:
(http://www.sevenforums.com/crashes-...error-oa002afx-sys-oa002ufd-sys-ndis-sys.html)
But at the moment everything is fine (except BSOD when Sleep)


Regards,
Christian


PS: Do you know which wireless adaptors are good in terms of speed? (eg. advanced/pro class) I am looking for a fast one because the router is quite far away from my computer (other end of house)
More than on recommendation would be good Thanx.

 

[Anak]

eureka? what does that mean? when I went to sleep with new drivers, everything was normal (as it should be)

It is usually a feeling of joy or happiness when the answer to a problem is found. You may have had many in your life, and never realized it.

Have you ever had a problem that was so hard to solve that you had to walk away from it just to take a break, and chill out?
Then when your doing something else far removed from that problem the answer for that problem comes to you in a flash?

That's just one example of a eureka moment.

eureka - definition. American English definition of eureka by Macmillan Dictionary

How do i find out if the drivers i use are bit compatible?

You have it in the back of your mind that you have Windows 7 Home Premium 64bit Edition installed on your machine.
When you are looking for programs or drivers to install on your machine you need to look for the 32/64 bit designation following the name given to those programs or drivers.

Lets take the installation files for your WLAN 802.11g PCI Adaptor as an example, Microsoft Windows Vista 32/64 bit. It means that the files contain both 32, and 64bit drivers, and the installation program will sense which bittage your OS is, and install the proper files.

The card did not come with the machine. I installed this card. It's a:
DSE XH9946 WLAN 802.11g PCI Adaptor
I have been using this card for over a year if not more, and the BSODs only started about a month ago or so.

I had some Perfomance issues the first few times I had BSODs:
(http://www.sevenforums.com/crashes-...error-oa002afx-sys-oa002ufd-sys-ndis-sys.html)
But at the moment everything is fine (except BSOD when Sleep)


Regards,
Christian

If you were using this card for over a year, and were happy with it, those performance issues may have corrupted the DSE files.

I would suggest starting from scratch as if you were installing the DSE card from a year ago.

That means:

• Completely removing any Folders/Files http://www.sevenforums.com/tutorials/77761-programs-features-uninstall-change-program.html
• Even going as far as checking the Program, and Program x86 Folders in Windows Explorer, and removing anything related to the DSE card, and that includes the folders themselves.
• This may also help: http://www.sevenforums.com/tutorials/106594-revo-uninstaller-freeware-uninstall-programs.html
• Reboot the machine.
• Pull the card, reboot the machine.
• Reinstall the drivers from the installation CD, reboot the machine.
• Re-install the Card, reboot the machine, and when the OS asks if you want it to install its drivers or do you have drivers for it, point the OS to the newly installed driver folders.
• Reboot the machine.
• Check to see if you have internet access, and if you BSOD upon entering Sleep mode.
• If you can't find your installation manual it is here: XH9946
  DSE WLAN 802.11g PCI Adaptor.pdf Start at step 5 then go to Step 5.3 .

PS: Do you know which wireless adaptors are good in terms of speed? (eg. advanced/pro class) I am looking for a fast one because the router is quite far away from my computer (other end of house)
More than on recommendation would be good Thanx.

Distance is not the only deciding factor in WLAN performance: 19 Factors Affecting Wireless LAN Performance | ITProPortal.com | Page One

The only drawback that I can see is your card only has a b/g designation: WLAN 802.11 b/g Network, where most cards now have a/b/g/n designations.
In your situation I would only concern myself with b/g/n, and look for a card that has that rating, it would look like this on the box: WLAN 802.11 b/g/n Network.

Again, if you were happy with the cards performance a year ago I'd try the re-install before I would get a new one.

Your welcome.

 

[christianb9632]

Hello,

I bought a new Cisco Linksys AE1000 Wireless-N Adapter.
I deinstalled the old one, and installed the new one.
Unfortunately, I am still getting BSOD erros when entering sleep mode.
The BSOD error says it's caused by ndis.sys, but when I had a look in WinDbg, it turns out it's a wsimdx.sys fault.
After a few clicks in the internet, I found out it could have been infected by a virus.
I searched my computer for all wsimdx.sys files and I found 3 of them in 3 different locations.
I think that at least one is a fault.
Locations are:
C:\Windows\System32\drivers
C:\Windows\System32\DriverStore\FileRepository\wsimdpx.inf_amd64_neutral_bde9dee674bea442
C:\Windows\System32

How do I know which is the faulty one?
How do I repair it?

Regards,
Christian