BSOD: IRQL_NOT_LESS_OR_EQUAL now computer very unstable

lordothello · 16 Dec 2013

Hello folks,
This morning I woke up to find that my computer had experienced a BSOD at approximately 3.30am while I was asleep, and had rebooted.
As far as I know, there was nothing mysterious going on with my computer. I had left it to download during the night, and only utorrent and chrome were running.

Now, whenever I boot into my windows, the whole system is very unstable. The boot up takes forever. The CPU is near 100% the entire time. And opening IE10, or Chrome just crashes the apps. Right now I am writing this from within Safe Mode on my machine.

I know I am supposed to run the SF diagnostic tool to gather all the data, but I am unable to run the program at all. So I have manually zipped the dmp file, and am attaching it here.

I would be very grateful, if someone could take a look at the file and point me in the right direction of a solution.

Thanks in advance.

lordothello · 16 Dec 2013

I managed to get the SF tool to run. I have no idea if it ran correctly or all the way, but here is the zipped archive of the result.
Thanks.

Arc · 16 Dec 2013

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff800031e8477}

*** 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+5b7d )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eae100
GetUlongFromAddress: unable to read from fffff80002eae1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9a4c0 -- (.trap 0xfffff80000b9a4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000300
rdx=0000000000000300 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031e8477 rsp=fffff80000b9a658 rbp=0000000000000000
 r8=0000000000000064  r9=0000000000000000 r10=00000000000fffff
r11=fffffa800543f4d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`031e8477 448b08          mov     r9d,dword ptr [rax] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c76169 to fffff80002c76bc0

STACK_TEXT:  
fffff800`00b9a378 fffff800`02c76169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9a380 fffff800`02c74de0 : fffffa80`09152ba8 fffff800`00b9a548 00000000`00000001 fffffa80`07c0e1a8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9a4c0 fffff800`031e8477 : fffffa80`07f2a010 fffffa80`04ce3d00 fffff800`031e8524 fffffa80`07c0e1a8 : nt!KiPageFault+0x260
fffff800`00b9a658 fffff800`031e8524 : fffffa80`07c0e1a8 fffffa80`0543f4d0 fffffa80`05442580 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff800`00b9a670 fffff800`031eb4fb : fffffa80`07c0e1a8 fffffa80`0543f4d0 fffffa80`07f2a010 fffff880`0561a1c7 : hal!HalpDmaMapScatterTransfer+0x34
fffff800`00b9a6c0 fffff800`031eb472 : fffffa80`07c0e1a8 fffffa80`07c0e1a0 00000000`00000064 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff800`00b9a750 fffff800`031ea94f : 00000000`00000000 fffff800`031e7fb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff800`00b9a790 fffff800`031eaafd : fffffa80`05170050 fffffa80`0543f4d0 00000000`00000001 fffffa80`00000078 : hal!HalpAllocateAdapterCallback+0xc7
fffff800`00b9a830 fffff800`031eb156 : fffffa80`0543f4d0 00000000`00000000 fffffa80`0543f400 00000000`00000002 : hal!IoFreeAdapterChannel+0x109
fffff800`00b9a860 fffff800`031ea71f : fffffa80`04b65540 00000000`00000054 fffffa80`0543f4d0 fffffa80`066badd0 : hal!HalAllocateAdapterChannel+0x11a
fffff800`00b9a8a0 fffff880`016c0600 : fffffa80`077e2b40 fffffa80`054415a0 00000000`000000a0 fffff880`05856f27 : hal!HalBuildScatterGatherList+0x2f3
fffff800`00b9a910 fffff880`0560fb7d : fffffa80`051701a0 fffff880`05856b20 fffffa80`04b05dc0 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff800`00b9a9b0 fffffa80`051701a0 : fffff880`05856b20 fffffa80`04b05dc0 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff800`00b9a9b8 fffff880`05856b20 : fffffa80`04b05dc0 fffff780`00000014 00000000`00000000 00000054`00000100 : 0xfffffa80`051701a0
fffff800`00b9a9c0 fffffa80`04b05dc0 : fffff780`00000014 00000000`00000000 00000054`00000100 00000000`00000000 : netw5v64+0x24cb20
fffff800`00b9a9c8 fffff780`00000014 : 00000000`00000000 00000054`00000100 00000000`00000000 fffff880`05617fb9 : 0xfffffa80`04b05dc0
fffff800`00b9a9d0 00000000`00000000 : 00000054`00000100 00000000`00000000 fffff880`05617fb9 fffff880`058d6f80 : 0xfffff780`00000014


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v64+5b7d
fffff880`0560fb7d ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  netw5v64+5b7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME:  netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49cbab84

FAILURE_BUCKET_ID:  X64_0xA_netw5v64+5b7d

BUCKET_ID:  X64_0xA_netw5v64+5b7d

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

0: kd> lmvm netw5v64
start             end                 module name
fffff880`0560a000 fffff880`05b45000   netw5v64 T (no symbols)           
    Loaded symbol image file: netw5v64.sys
    Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
    Image name: netw5v64.sys
    Timestamp:        Thu Mar 26 21:51:24 2009 (49CBAB84)
    CheckSum:         00533DE3
    ImageSize:        0053B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The issue is with the wifi, the driver is too old.

If you want us to assist you to find an appropriate driver, upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

lordothello · 16 Dec 2013

Thank you for the reply. I am attaching the zipped nfo file as you requested. I did this from within safe mode, so I hope that doesnt make a difference.
I also noticed a lot of errors in the windows error reporting section of the nfo file. None of them made any sense to me though.
Thank you so much once again.

Arc · 16 Dec 2013

Yours is Intel® WiFi Link 5100. So you need to get Intel® PROSet/Wireless Software and Drivers for Windows 7.

lordothello · 17 Dec 2013

I have a quick clarification to make. If there is a fault with my wireless driver, then how is it that I can access the internet from within Safe Mode with Networking? I mean, Safe Mode works perfectly fine, without any glitches from what I can see.

lordothello · 17 Dec 2013

I also updated the driver like you said from within Safe Mode. But the problem still persists while booting into the regular mode. It is very unstable.

Arc · 17 Dec 2013

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the system configuration window, with the "general" tab selected.
- Click the "startup" tab. Click "Disable all" > Apply > OK.
- Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still? Let us know.

lordothello · 17 Dec 2013

Okay so it is true that disabling all the non-ms startup entries, did improve the booting process at bit. but not entirely. while the CPU remains consistent at 100%, the startup entries that were disabled were the likes of Google updates, acrobat updater, roboform etc. And there were too many of them either. Perhaps one of the services was corrupted.
I think the best course of action is to reformat the computer. Because I have been using the same software config for years without and issue like this.

Arc · 18 Dec 2013

lordothello said:

I think the best course of action is to reformat the computer. Because I have been using the same software config for years without and issue like this.

Go for it then :)