Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Lenovo IDEAPAD BSOD

11 Jan 2010   #1

Windows 7
 
 
Lenovo IDEAPAD BSOD

Hey I was hoping for a little help with a pc issue i have been having lately. In the past month out of nowhere i have been receiving BSOD reading irql less or equal. I'm running 7 on this laptop and have been running the preview since march with zero hardware issues previously. All of my drivers are up to date as far as i can tell and i never encountered any issues with this before. I have attempted tom isolate the issue but i have not been able to pinpoint the source any help would be very appreciated. My laptop is a lenovo ideapad y530 and i have attached a zip of my last three minidumps.

My System SpecsSystem Spec
.

11 Jan 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by gdelia928 View Post
Hey I was hoping for a little help with a pc issue i have been having lately. In the past month out of nowhere i have been receiving BSOD reading irql less or equal. I'm running 7 on this laptop and have been running the preview since march with zero hardware issues previously. All of my drivers are up to date as far as i can tell and i never encountered any issues with this before. I have attempted tom isolate the issue but i have not been able to pinpoint the source any help would be very appreciated. My laptop is a lenovo ideapad y530 and i have attached a zip of my last three minidumps.

Hi and welcome

the probable cause of all three crashes is NETw5s64.sys, which is part of your Intel wifi driver;


I would update the driver

also run a system file check.
type cmd in

search>right click and run as admin>sfc /scannow

Ken J+


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


Loading Dump File [C:\Users\K\Desktop\New folder (3)\011110-24726-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Mon Jan 11 01:36:40.767 2010 (GMT-5)
System Uptime: 0 days 1:23:05.765
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, fffff80002c16477}

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: fffff80002c16477, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`02c16477 448b08          mov     r9d,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88009dd02c0 -- (.trap 0xfffff88009dd02c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000002c
rdx=000000000000002c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c16477 rsp=fffff88009dd0458 rbp=0000000000000000
 r8=000000000000001c  r9=0000000000000000 r10=00000000000fffff
r11=fffffa8006c6ac70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`02c16477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cce469 to fffff80002ccef00

STACK_TEXT:  
fffff880`09dd0178 fffff800`02cce469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09dd0180 fffff800`02ccd0e0 : fffffa80`04dd4150 fffffa80`0707a0d0 fffffa80`065728c0 fffff880`04ab5893 : nt!KiBugCheckDispatch+0x69
fffff880`09dd02c0 fffff800`02c16477 : fffffa80`04cc9190 fffffa80`0864dfd4 fffff800`02c16524 fffffa80`0707a0d0 : nt!KiPageFault+0x260
fffff880`09dd0458 fffff800`02c16524 : fffffa80`0707a0d0 fffffa80`06c6ac70 fffffa80`086413a0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`09dd0470 fffff800`02c194fb : fffffa80`0707a0d0 fffffa80`06c6ac70 fffffa80`04cc9190 fffffa80`065b7fd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`09dd04c0 fffff800`02c19472 : fffffa80`0707a0d0 fffffa80`0707a0c8 00000000`0000001c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`09dd0550 fffff800`02c1894f : fffffa80`06c6a990 fffff800`02c1601e 00000000`00000002 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`09dd0590 fffff800`02c18afd : fffffa80`063cb050 fffffa80`06c6ac70 00000000`00000001 fffffa80`00000544 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`09dd0630 fffff800`02c19156 : fffffa80`06c6ac70 00000000`00000500 fffffa80`06c6ac00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`09dd0660 fffff800`02c1871f : fffffa80`04f8be40 00000000`000005f4 fffffa80`06c6ac70 fffffa80`049e51c0 : hal!HalAllocateAdapterChannel+0x11a
fffff880`09dd06a0 fffff880`018f97c0 : fffffa80`061d8470 fffffa80`06c6a8e0 fffffa80`000000a0 fffff880`04cafc40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`09dd0710 fffff880`04a6b76b : fffffa80`063cb1a0 00000000`00000000 fffffa80`049dd2f0 fffff880`04c10aa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`09dd07b0 fffffa80`063cb1a0 : 00000000`00000000 fffffa80`049dd2f0 fffff880`04c10aa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`09dd07b8 00000000`00000000 : fffffa80`049dd2f0 fffff880`04c10aa0 00000000`00000000 000005f4`00000100 : 0xfffffa80`063cb1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+b76b
fffff880`04a6b76b ??              ???

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
---------
My System SpecsSystem Spec
12 Jan 2010   #3

Windows 7
 
 
Thank you for your help

The driver I had was the most updated one available frm intel so I rollbacked to the native windows driver and it seems to have resolved the issue
thank you so much for taking the time to help out, It is really appreciated
My System SpecsSystem Spec
.


Reply

 Lenovo IDEAPAD BSOD





Thread Tools



Similar help and support threads for2: Lenovo IDEAPAD BSOD
Thread Forum
Can Help with Recommended RAM for Lenovo IdeaPad Y570? Hardware & Devices
Upgrading Lenovo Ideapad Y550 CPU. Hardware & Devices
Lenovo Ideapad Y550 Hardware & Devices
Lenovo ideapad U450p BSOD BSOD Help and Support
Lenovo IdeaPad S10-3t Hardware & Devices
Lenovo S10 Ideapad have a bootscreen in vista! General Discussion
Windows 7 Pro freezes on Lenovo Y430 ideapad BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 01:30 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33