Win 7 X64 BSOD (BAD_POOL_CALLER)

[Lossus]

Hy guys, I'm new here and wanted to thank everbody h is willing to help me ior at least is trying so .

My Computer is a Acer Aspire 7738g (Notebook).
I have a Windows 7 Home Premium X64 OEM.
My Notebook is about a half year old and I have reinstalled the Windows for 2 months.

If you are missing any Information dont hessitate to ask.

Sorry for my bad english and any typing errors.

 

[richc46]

You had a lot of BSOD. I checked about 25%. They all require that you update this driver

Netw5s64.sys
Productname: Intel® Wireless WiFi Link Adapter
Description: Intel® Wireless WiFi Link
Driver Company: Intel Corporation
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
 
 
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\070310-26488-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0360f000 PsLoadedModuleList = 0xfffff800`0384ce50
Debug session time: Sat Jul  3 17:03:53.766 2010 (GMT-4)
System Uptime: 0 days 12:26:41.967
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80003bed477}
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003bed477, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038b70e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`03bed477 448b08          mov     r9d,dword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
TRAP_FRAME:  fffff880023c3dc0 -- (.trap 0xfffff880023c3dc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000004d8
rdx=00000000000004d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003bed477 rsp=fffff880023c3f58 rbp=0000000000000000
 r8=00000000000000c8  r9=0000000000000000 r10=00000000000fffff
r11=fffffa8006b25b70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`03bed477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff8000367eb69 to fffff8000367f600
STACK_TEXT:  
fffff880`023c3c78 fffff800`0367eb69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`023c3c80 fffff800`0367d7e0 : fffffa80`087231a0 fffffa80`0a3d4348 fffffa80`05aeb310 fffff880`04900893 : nt!KiBugCheckDispatch+0x69
fffff880`023c3dc0 fffff800`03bed477 : fffffa80`0a86bf40 00000000`0033cb28 fffff800`03bed524 fffffa80`0a3d4348 : nt!KiPageFault+0x260
fffff880`023c3f58 fffff800`03bed524 : fffffa80`0a3d4348 fffffa80`06b25b70 fffffa80`09feaa60 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`023c3f70 fffff800`03bf04fb : fffffa80`0a3d4348 fffffa80`06b25b70 fffffa80`0a86bf40 fffffa80`0ad25fd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`023c3fc0 fffff800`03bf0472 : fffffa80`0a3d4348 fffffa80`0a3d4340 00000000`000000c8 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`023c4050 fffff800`03bef94f : fffffa80`06b259d0 fffff800`03bed01e 00000000`00000001 00000000`00000005 : hal!IoMapTransfer+0x8e
fffff880`023c4090 fffff800`03befafd : fffffa80`0604f050 fffffa80`06b25b70 00000000`00000001 fffffa80`00000290 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`023c4130 fffff800`03bf0156 : fffffa80`06b25b70 00000000`00000100 fffffa80`06b25b00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`023c4160 fffff800`03bef71f : fffffa80`087d0ae0 00000000`000001cc fffffa80`06b25b70 fffffa80`0a71f020 : hal!HalAllocateAdapterChannel+0x11a
fffff880`023c41a0 fffff880`0184f7c0 : fffffa80`09c7fab0 fffffa80`06b257e0 fffffa80`000000a0 fffff880`04afac40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`023c4210 fffff880`048b676b : fffffa80`0604f1a0 00000000`00000000 fffffa80`05981cf0 fffff880`04a5baa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`023c42b0 fffffa80`0604f1a0 : 00000000`00000000 fffffa80`05981cf0 fffff880`04a5baa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`023c42b8 00000000`00000000 : fffffa80`05981cf0 fffff880`04a5baa0 00000000`00000000 000001cc`00000100 : 0xfffffa80`0604f1a0
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
NETw5s64+b76b
fffff880`048b676b ??              ???
SYMBOL_STACK_INDEX:  c
SYMBOL_NAME:  NETw5s64+b76b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME:  NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7
FAILURE_BUCKET_ID:  X64_0xA_NETw5s64+b76b
BUCKET_ID:  X64_0xA_NETw5s64+b76b
Followup: MachineOwner
---------

A kernel-mode process or driver attempted to access a memory location without authorization. This Stop error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the Stop error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this Stop error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program. This KB314063 may show you the direction.

 

[Lossus]

Yeah you are right i had a lot of Problems in the last time and I'm realy thankfull for your advise with the driver, I will try it out and post here again^^.

 

[richc46]

Take your time. I or other members will be glad to help. 24 x 7

 

[Lossus]

I've installed the new Driver and can start now without any problems and do anything that hadn't worked befor.

Thank you very much.

You can close the thread now if you want.

Kind regards

Frederic Golser

 

[richc46]

To teach others, how did you update the driver. Website, automatic update?
What steps did you take. From your point of view how was it done. Not in texbook language. Use language that we can all understand.

Did you think that it was easy, can anyone do it?

I am as happy as you are Fred
Thanks for telling us.

 

[zigzag3143]

Nice thread Rich

 

[Lossus]

At first i went to my Devices Manager and took a look on the exact name of my Wifi Adapter. Then i went to: http://downloadcenter.intel.com/Default.aspx
and searched for my Device. AfterI installed it I just had to restart and now it works fine

 

[richc46]

Thank you Zigzag

and thank you Lossus.

We helped you and now you have helped others. I am going to include this when I tell others how it is done.

 

[Lossus]

Thanks. I'm realy glad I found this site and will tell many friends where they can find friendly people that will help them.

Thank you very much again and we will see us agian in the Futur. I'm sure I will have some Problems in the futur XD

 

[richc46]

Im glad that we were here for you