Suspend mode bsod

[Fabrix]

Hi guys, it's my first post here, and I already have a problem.
Practically when I suspend my pc, when I want to reuse it, many times it shows a bsod and has to do a restart. I can't understand what may be the problem

Here some informations:

-Windows 7 x64
-First and only os installed on the computer
-Retail version
-Both the os and the hardware are three months old

Ps : you have to apologize me for my bad english, but I'm italian. I've noticed that some files of the reports are written in italian, if you have some problem to understand them, I may give a simple translation.

 

[Fabrix]

Nobody may help me ??

 

[zigzag3143]

Nobody may help me ??

Fabrix Ciao e benvenuto. Il file che avete accluso sembra essere il executible, non i dati che abbiamo bisogno. Potete guardare nella cartella Documenti cartella quella corretta.


Hello and welcome. The file you attached appears to be the executable, not the data that we need. Can you look in your documents folder folder the correct one.

Let us know if you need assistance finding it

Ken

 

[Fabrix]

Nobody may help me ??

Hello and welcome. The file you attached appears to be the executable, not the data that we need. Can you look in your documents folder folder the correct one.

Let us know if you need assistance finding it

Ken

Oh, I should have commited a mistake . Anyway now everything is right, have a look at the data, I've uploaded them in the first post

 

[zigzag3143]

Nobody may help me ??

Hello and welcome. The file you attached appears to be the executable, not the data that we need. Can you look in your documents folder folder the correct one.

Let us know if you need assistance finding it

Ken

Oh, I should have commited a mistake . Anyway now everything is right, have a look at the data, I've uploaded them in the first post

These were caused by your netgear driver (WN111v2w7x.sys)

I would go to netgear and download the newest driver and re-install it.

Let us know if you need more help


Ken

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\090310-13306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Fri Sep  3 08:32:35.531 2010 (GMT-4)
System Uptime: 0 days 0:21:00.263
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {18, 2, 0, fffff88003a4877e}

Unable to load image \SystemRoot\system32\DRIVERS\WN111v2w7x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WN111v2w7x.sys
*** ERROR: Module load completed but symbols could not be loaded for WN111v2w7x.sys
Probably caused by : WN111v2w7x.sys ( WN111v2w7x+2177e )

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

0: 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: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003a4877e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
 0000000000000018 

CURRENT_IRQL:  2

FAULTING_IP: 
WN111v2w7x+2177e
fffff880`03a4877e 488b4018        mov     rax,qword ptr [rax+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff80004100530 -- (.trap 0xfffff80004100530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80056aa000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a4877e rsp=fffff800041006c0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002a67000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WN111v2w7x+0x2177e:
fffff880`03a4877e 488b4018        mov     rax,qword ptr [rax+18h] ds:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad6ca9 to fffff80002ad7740

STACK_TEXT:  
fffff800`041003e8 fffff800`02ad6ca9 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`041003f0 fffff800`02ad5920 : 00000000`00000000 fffffa80`054e21a0 00000000`00000002 fffffa80`078cf168 : nt!KiBugCheckDispatch+0x69
fffff800`04100530 fffff880`03a4877e : fffffa80`054e21a0 ffffffff`fffe7960 00000000`00000001 fffffa80`04f534b0 : nt!KiPageFault+0x260
fffff800`041006c0 fffffa80`054e21a0 : ffffffff`fffe7960 00000000`00000001 fffffa80`04f534b0 fffffa80`06706900 : WN111v2w7x+0x2177e
fffff800`041006c8 ffffffff`fffe7960 : 00000000`00000001 fffffa80`04f534b0 fffffa80`06706900 fffffa80`04eebb30 : 0xfffffa80`054e21a0
fffff800`041006d0 00000000`00000001 : fffffa80`04f534b0 fffffa80`06706900 fffffa80`04eebb30 00000000`00000001 : 0xffffffff`fffe7960
fffff800`041006d8 fffffa80`04f534b0 : fffffa80`06706900 fffffa80`04eebb30 00000000`00000001 fffff880`03a44ffa : 0x1
fffff800`041006e0 fffffa80`06706900 : fffffa80`04eebb30 00000000`00000001 fffff880`03a44ffa 00000000`00000000 : 0xfffffa80`04f534b0
fffff800`041006e8 fffffa80`04eebb30 : 00000000`00000001 fffff880`03a44ffa 00000000`00000000 fffff880`0162508d : 0xfffffa80`06706900
fffff800`041006f0 00000000`00000001 : fffff880`03a44ffa 00000000`00000000 fffff880`0162508d fffffa80`04f534b0 : 0xfffffa80`04eebb30
fffff800`041006f8 fffff880`03a44ffa : 00000000`00000000 fffff880`0162508d fffffa80`04f534b0 fffffa80`06706900 : 0x1
fffff800`04100700 00000000`00000000 : fffff880`0162508d fffffa80`04f534b0 fffffa80`06706900 fffffa80`04f53628 : WN111v2w7x+0x1dffa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WN111v2w7x+2177e
fffff880`03a4877e 488b4018        mov     rax,qword ptr [rax+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WN111v2w7x+2177e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WN111v2w7x

IMAGE_NAME:  WN111v2w7x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ade879d

FAILURE_BUCKET_ID:  X64_0xD1_WN111v2w7x+2177e

BUCKET_ID:  X64_0xD1_WN111v2w7x+2177e

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

 

[Fabrix]

Ok, I installed the driver and everything seems ok by now. If I run into other problems I'll post it here. Thank you very much zigzag