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: BSOD - Windows t 7 Pro - 64-bit.

09 Dec 2009   #1
Jeezy123

Windows 7 Pro
 
 
BSOD - Windows t 7 Pro - 64-bit.

Hi -

I get the BSOD after like 20 minutes or so on Windows 7 Pro. I fresh installed on a new HD.

Here are my computer's specs (Laptop):


ThinkPad T61

Color - Black

Processor - Intel Core2 Duo T8100 (2.10 GHz, 3MB L2, 800 MHz FSB)

Operating system - Windows 7 Pro - 64 Bit

Screen size - 15.4" WSXGA+ (1680 X 1050) TFT ( 1680 X 1050 )

RAM Memory: 2x2GB PC2-5300 DDR2 SDRAM 667MHz SODIMM Memory

Harddrive - 320GB, 5400RPM Serial ATA 2.5" Drive

Optical drive - DVD Recordable 8x Max Dual Layer

WLan - Intel® Wireless WiFi Link 4965AG (supporting Centrino Pro)

Battery - 6 Cell Lithium Ion Battery (6.5 Hour Run Time)

Discrete Graphics - NVIDIA Quadro NVS 140M (128MB)

UltraNav (TrackPoint and TouchPad)


I have attached my minidump file. Please help! I either get the irql_not_less_or_equal or drivers_irql_not_less_or_equal. The computer will then reboot.


My System SpecsSystem Spec
.
09 Dec 2009   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Jeasy

The zip file is corrupt. upload it again


Thanks Kenn J+
My System SpecsSystem Spec
09 Dec 2009   #3
Jeezy123

Windows 7 Pro
 
 

Hi Kenn -

Sorry, I zipped the files into a .zipx file and e-mailed it to myself and tried to upload it here at work. I guess the file got corrupted when i changed it to a .zip file. Does this help? I received this message when I signed back onto windows.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002805477
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\120609-17830-01.dmp
C:\Users\Derek\AppData\Local\Temp\WER-37237-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
.

09 Dec 2009   #4
Jeezy123

Windows 7 Pro
 
 

Here is the new zip file. Please help!

Thanks.
My System SpecsSystem Spec
09 Dec 2009   #5
usasma
Microsoft MVP

 
 

Holy smokes! 34 memory dumps in 3 days! All are STOP 0xA: IRQL_NOT_LESS_OR_EQUAL ( BSOD Index ) and STOP 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL ( BSOD Index )

I suspect your network drivers netw5v64.sys (which belongs to your Intel® Wireless WiFi Link 5000 Series Adapter Driver) - but will run the last 10 dump files to see what they say (FWIW - they confirm that the Intel wifi driver is to blame).

While waiting for the dump files to finish, here's the way to update the drivers.
- download the latest Win7 64 bit drivers from the Intel download site
- uninstall the current wireless drivers from Control Panel...Programs...Uninstall a program
- install the freshly downloaded drivers.


I would also suggest searching Google for these older drivers and updating them also:
Code:
ibmpmdrv.sys Thu May 31 05:51:31 200
rixdpx64.sys Fri Nov 17 23:07:46 2006
Here's the summary of the BSOD analysis:
Code:
Debug session time: Tue Dec  8 09:25:03.183 2009 (GMT-5)
System Uptime: 0 days 0:18:00.243
BugCheck A, {0, 2, 0, fffff800033f3477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 10:00:22.169 2009 (GMT-5)
System Uptime: 0 days 0:34:09.229
BugCheck A, {0, 2, 0, fffff80002e15477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 10:34:02.739 2009 (GMT-5)
System Uptime: 0 days 0:32:31.799
BugCheck D1, {30, 2, 0, fffff88004063994}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+1b4994 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 11:10:57.049 2009 (GMT-5)
System Uptime: 0 days 0:35:45.109
BugCheck A, {0, 2, 0, fffff80002e05477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 11:23:27.319 2009 (GMT-5)
System Uptime: 0 days 0:11:19.379
BugCheck A, {0, 2, 0, fffff80002e17477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 11:39:37.246 2009 (GMT-5)
System Uptime: 0 days 0:15:03.306
BugCheck A, {0, 2, 0, fffff800033e7477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 12:04:05.682 2009 (GMT-5)
System Uptime: 0 days 0:23:18.617
BugCheck D1, {30, 2, 0, fffff88003ffe994}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+1b4994 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 13:18:49.758 2009 (GMT-5)
System Uptime: 0 days 1:13:34.818
BugCheck D1, {30, 2, 0, fffff88004043994}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+1b4994 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 13:55:25.953 2009 (GMT-5)
System Uptime: 0 days 0:35:24.013
BugCheck A, {0, 2, 0, fffff80002e1d477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 16:44:23.283 2009 (GMT-5)
System Uptime: 0 days 0:05:03.343
BugCheck D1, {30, 2, 0, fffff88003fbb994}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+1b4994 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
My System SpecsSystem Spec
10 Dec 2009   #6
Jeezy123

Windows 7 Pro
 
 

Thanks Usasama! It worked. I left my computer on over night and no signs of BSOD.

I'm new to this forum. How do i rep you?
My System SpecsSystem Spec
11 Dec 2009   #7
usasma
Microsoft MVP

 
 

Little scale thing in the upper left of one of the posts for the member you want to rep.

If you don't crash in one day, we hope that we've fixed it.
If you don't crash in 3 days, we start to think that we've fixed it.
If you don't crash in 1 week, we're pretty sure that it's fixed.

It's good to hear that it seems to have fixed things for you!
Thanks for letting us known!
My System SpecsSystem Spec
18 Jan 2010   #8
Jeezy123

Windows 7 Pro
 
 

I am receiving the BSOD again....not as often as before. Do you think you can help me once again?
My System SpecsSystem Spec
18 Jan 2010   #9
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jeezy123 View Post
I am receiving the BSOD again....not as often as before. Do you think you can help me once again?

Hi and welcome

This one was probably caused by you wifi driver netw5v64.sys. I would download a fresh copy and install it

I would also run a system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP


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\011610-16629-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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`03097e50
Debug session time: Sat Jan 16 16:43:56.228 2010 (GMT-5)
System Uptime: 3 days 13:26:42.288
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, fffff80002e13477}

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031020e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`02e13477 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:  fffff88009c83b00 -- (.trap 0xfffff88009c83b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000dc0
rdx=0000000000000dc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e13477 rsp=fffff88009c83c98 rbp=0000000000000000
 r8=0000000000000564  r9=0000000000000000 r10=00000000000fffff
r11=fffffa8005ac3c70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`02e13477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecb469 to fffff80002ecbf00

STACK_TEXT:  
fffff880`09c839b8 fffff800`02ecb469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09c839c0 fffff800`02eca0e0 : fffffa80`040bba10 fffffa80`046f3be8 fffffa80`0541d940 fffff880`03f207f3 : nt!KiBugCheckDispatch+0x69
fffff880`09c83b00 fffff800`02e13477 : fffffa80`06e6fdf0 fffffa80`0754d240 fffff800`02e13524 fffffa80`046f3be8 : nt!KiPageFault+0x260
fffff880`09c83c98 fffff800`02e13524 : fffffa80`046f3be8 fffffa80`05ac3c70 fffffa80`048ca7a0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`09c83cb0 fffff800`02e164fb : fffffa80`046f3be8 fffffa80`05ac3c70 fffffa80`06e6fdf0 fffffa80`06e8bfd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`09c83d00 fffff800`02e16472 : fffffa80`046f3be8 fffffa80`046f3be0 00000000`00000564 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`09c83d90 fffff800`02e1594f : 00000000`00000000 fffff800`02e1301e 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`09c83dd0 fffff800`02e15afd : fffffa80`0525f050 fffffa80`05ac3c70 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`09c83e70 fffff800`02e16156 : fffffa80`05ac3c70 00000000`00000100 fffffa80`05ac3c00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`09c83ea0 fffff800`02e1571f : fffffa80`049702a0 00000000`00000155 fffffa80`05ac3c70 fffffa80`04021a10 : hal!HalAllocateAdapterChannel+0x11a
fffff880`09c83ee0 fffff880`014cc7c0 : fffffa80`03d37a20 fffffa80`05ac38e0 fffffa80`000000a0 fffff880`0411b550 : hal!HalBuildScatterGatherList+0x2f3
fffff880`09c83f50 fffff880`03ed64eb : fffffa80`0525f1a0 00000000`00000000 fffffa80`04022dc0 fffff880`0407c0a0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`09c83ff0 fffffa80`0525f1a0 : 00000000`00000000 fffffa80`04022dc0 fffff880`0407c0a0 00000000`00000000 : netw5v64+0xb4eb
fffff880`09c83ff8 00000000`00000000 : fffffa80`04022dc0 fffff880`0407c0a0 00000000`00000000 00000155`00000100 : 0xfffffa80`0525f1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v64+b4eb
fffff880`03ed64eb ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  netw5v64+b4eb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME:  netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aafec38

FAILURE_BUCKET_ID:  X64_0xA_netw5v64+b4eb

BUCKET_ID:  X64_0xA_netw5v64+b4eb

Followup: MachineOwner
---------
My System SpecsSystem Spec
20 Jan 2010   #10
Jeezy123

Windows 7 Pro
 
 

That seemed to do the job. Thanks!
My System SpecsSystem Spec
Reply

 BSOD - Windows t 7 Pro - 64-bit.




Thread Tools




Similar help and support threads
Thread Forum
BSOD on Windows Update; BSOD when playing games
NOTE: DM log collector seem to be getting stuck when collecting msinfo32.nfo, so the attached file can be incomplete. Please let me know if it can take longer than 10 minutes to collect this data so i will run the program again. BSOD #1: It started at around January 15th - basically when i shoot...
BSOD Help and Support
BSOD using FULL windows 7, no BSOD using safe mode
My computer has been stable for years, however recently I have been getting BSOD when doing any task. Windows will sometimes load to the desktop and I am able to watch video, run windows score, check email, etc before it will BSOD. Other times, it will BSOD before getting to the windows login...
BSOD Help and Support
BSOD trying to start Windows, gets to desktop then BSOD, then reboots
Hi guys, I encountered BSOD for the first time. Very annoying. Right now I have to run this on Safe Mode in order to access the internet. I also noticed I can't use Firefox right now, and instead am using iE. I couldn't run the the performance scan report either (time out?), but I did attach the...
BSOD Help and Support
lots of BSOD - Format, Clean windows install - Still same BSOD
Hi, I use a 1.5 year old aces aspire 5738z and I think it just died on me. Here is what happens. Whatever I do it cannot stay without a BSOD for more than 10 minutes. I tried reinstalling drivers and it did not change anything so I tried several things but finally just formated it and installed...
BSOD Help and Support
BSOD Starting Windows Virtual PC Machines (any machine, always bsod)
Hello All, I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last...
BSOD Help and Support
Windows crash (BSOD without BSOD) nVidia
Hello! I have been expiriencing problems with my computer which are as follows: I do my thing on the computer (surf, play etc.) and suddently my screen goes black. It has been doing this for about a week now, and I received my new SSDs recently so I popped them in, put them in RAID-0 and...
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 12:08.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App