Share via


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a

Question

Monday, January 17, 2011 11:55 AM

My computer usually gets a blue screen 2 times a day. It's running Windows 7. The following error log is found in event viewer:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xfffff8a025a60054, 0x0000000000000002, 0x0000000000000001, 0xfffff80002fb5901). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011711-50591-01.

 

Log Name:  System
Source:  Microsoft-Windows-WER-SystemErrorReporting
Date:   1/17/2011 7:27:55 AM
Event ID:  1001
Task Category: None
Level:   Error
Keywords:  Classic
User:   N/A
Computer:  MyComputerName
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff8a021c66054, 0x0000000000000002, 0x0000000000000001, 0xfffff80002fb7901). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011711-49592-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
 <EventID Qualifiers="16384">1001</EventID>
 <Version>0</Version>
 <Level>2</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2011-01-17T04:27:55.000000000Z" />
 <EventRecordID>76974</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>System</Channel>
 <Computer>MyComputerName</Computer>
 <Security />
 </System>
 <EventData>
 <Data Name="param1">0x0000000a (0xfffff8a021c66054, 0x0000000000000002, 0x0000000000000001, 0xfffff80002fb7901)</Data>
 <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
 <Data Name="param3">011711-49592-01</Data>
 </EventData>
</Event>

 

I have run memory test using memtest86+-4.10 and found no problems.

Also I have checked drive C: using ScanDisk and also found no problems.

Wael

All replies (7)

Wednesday, January 19, 2011 1:25 PM ✅Answered

Hi Wael,

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.

STACK_TEXT: 
fffff880`06f56ef8 fffff800`02cd2ca9 : 00000000`0000000a fffff8a0`1fc87054 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06f56f00 fffff800`02cd1920 : 00000000`00f800c8 fffffa80`04758890 fffff8a0`00004d60 fffff880`0000003f : nt!KiBugCheckDispatch+0x69
fffff880`06f57040 fffff800`02fb9901 : 00000000`00000000 fffff8a0`0000b030 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`06f571d0 fffff800`02fba56a : fffffa80`047588e0 fffff8a0`1fc87000 00000000`00008000 fffff880`06f573d0 : nt!ObpQueryNameString+0x4ed
fffff880`06f572d0 fffff800`02fb9ecf : fffffa80`00000020 fffffa80`03771d20 00000000`00000000 fffff880`00000100 : nt!ObQueryNameString+0xe
fffff880`06f57310 fffff800`02fba612 : fffffa80`03771d20 ffffffff`80003ea0 fffff8a0`1fc59000 fffff8a0`065ba000 : nt!IopQueryNameInternal+0x9f
fffff880`06f573b0 fffff800`02fb94c4 : 00000000`00000000 00000000`00000000 fffff8a0`1fc5a010 00000000`00000001 : nt!IopQueryName+0x26
fffff880`06f57400 fffff800`02f4f186 : fffffa80`03771d20 fffff8a0`065ba000 fffffa80`00008000 fffff880`06f57570 : nt!ObpQueryNameString+0xb0
fffff880`06f57500 fffff800`02f55124 : fffff8a0`18df77c0 00000000`c0000005 fffff8a0`17040060 fffffa80`03771d20 : nt!CmpQueryNameString+0x9e
fffff880`06f57560 fffff800`02f5a882 : 00000000`00000000 fffff8a0`1fc5a010 00000000`00000001 fffff800`02ed9df8 : nt!CmpInitCmRM+0x264
fffff880`06f57740 fffff800`02f5632b : fffff8a0`00000020 fffff880`06f57a60 00000000`00000000 00000000`00000021 : nt!CmLoadKey +0x452
fffff880`06f57930 fffff800`02f585e4 : 00000980`00000000 00000000`00badfc0 00000000`00000000 00000000`00000000 : nt!NtLoadKeyEx +0x4c5
fffff880`06f57b90 fffff800`02cd2993 : 00000000`00000008 00000000`00000000 00000000`00000001 fffffa80`048e2230 : nt!NtLoadKey+0x24
fffff880`06f57be0 00000000`76e804ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

PROCESS_NAME:  TrustedInstall

Windows crashes while loading a registry key while searching/installing updates.

Run Chkdsk /f /r to detect and resolve any file system structural (NTFS) corruption. You must restart the system before the disk scan begins on a system partition.

Also update the BIOS if possible (yours is a bit old):

BiosVersion = 786F3 v01.16
BiosReleaseDate = 02/19/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP xw4600 Workstation

André

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/


Monday, January 17, 2011 2:47 PM

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

http://msdn.microsoft.com/en-us/library/ff560129%28VS.85%29.aspx

To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

André

[1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/


Wednesday, January 19, 2011 11:01 AM

Hello,

This is the link in my SkyDrive:

http://cid-49cb4997f0098ec6.office.live.com/self.aspx/Minidump/Minidump.zip

 

Wael


Sunday, January 8, 2012 12:28 AM

Hello to all,

I have the same error, BSOD and restarts. I do not have any process like this: PROCESS_NAME: ** TrustedInstall**

I have uploaded the dump files as indicated to my SkyDrive account. Below's the link. Please advise.

https://skydrive.live.com/redir.aspx?cid=9cb41fcd05abb4ac&resid=9CB41FCD05ABB4AC!141&parid=root

note: running win7, x64, SP1, all updates. I've recently uninstalled physically my optical drive from the laptop, but there wasn't any process linked to it. BIOS version is last version available.

thank you


Monday, January 9, 2012 3:49 AM | 1 vote

Hi,

 

For general blue screen troubleshooting,

 

http://mikemstech.blogspot.com/2011/11/windows-crash-dump-analysis.html

 

The specific error that you received was 0xA IRQL_NOT_LESS_OR_EQUAL,

 

http://mikemstech.blogspot.com/2011/11/how-to-troubleshoot-blue-screen-0xa.html

 

yours appears to be due to netw5v64.sys, possibly an Intel WiFi adapter?

You might see if there are updates for your system's network drivers on

the manufacturer's site.

 

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

 

Debugging Details:

 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003310100

 0000000000000000

 

CURRENT_IRQL:  2

 

FAULTING_IP:

hal!HalpDmaNextContiguousPiece+103

fffff800`0301a477 448b08          mov     r9d,dword ptr [rax]

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

BUGCHECK_STR:  0xA

 

PROCESS_NAME:  System

 

TRAP_FRAME:  fffff80000b9bf60 -- (.trap 0xfffff80000b9bf60)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=00000000000009e0

rdx=00000000000009e0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8000301a477 rsp=fffff80000b9c0f8 rbp=0000000000000000

 r8=0000000000000564  r9=0000000000000000 r10=00000000000fffff

r11=fffffa8005b1d520 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl nz ac pe nc

hal!HalpDmaNextContiguousPiece+0x103:

fffff800`0301a477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff800030dd1e9 to fffff800030ddc40

 

STACK_TEXT:

fffff800`00b9be18 fffff800`030dd1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff800`00b9be20 fffff800`030dbe60 : fffffa80`088d88e8 fffff800`00b9bfe8 00000000`00000001 fffffa80`07d9f218 : nt!KiBugCheckDispatch+0x69

fffff800`00b9bf60 fffff800`0301a477 : fffffa80`0701c450 00000000`000ad620 fffff800`0301a524 fffffa80`07d9f218 : nt!KiPageFault+0x260

fffff800`00b9c0f8 fffff800`0301a524 : fffffa80`07d9f218 fffffa80`05b1d520 fffffa80`0457ed80 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103

fffff800`00b9c110 fffff800`0301d4fb : fffffa80`07d9f218 fffffa80`05b1d520 fffffa80`0701c450 fffff880`04acb1c7 : hal!HalpDmaMapScatterTransfer+0x34

fffff800`00b9c160 fffff800`0301d472 : fffffa80`07d9f218 fffffa80`07d9f210 00000000`00000564 00000000`00000000 : hal!HalpMapTransfer+0x7b

fffff800`00b9c1f0 fffff800`0301c94f : fffffa80`05f54a70 fffff800`0301a01e 00000000`00000003 00000000`00000004 : hal!IoMapTransfer+0x8e

fffff800`00b9c230 fffff800`0301cafd : fffffa80`05146050 fffffa80`05b1d520 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7

fffff800`00b9c2d0 fffff800`0301d156 : fffffa80`05b1d520 00000000`00000500 fffffa80`05b1d500 00000000`00000003 : hal!IoFreeAdapterChannel+0x109

fffff800`00b9c300 fffff800`0301c71f : fffffa80`063abad0 00000000`000005fc fffffa80`05b1d520 fffffa80`049853c0 : hal!HalAllocateAdapterChannel+0x11a

fffff800`00b9c340 fffff880`01442750 : fffffa80`071995c0 fffffa80`05640780 00000000`000000a0 fffff880`04d07f27 : hal!HalBuildScatterGatherList+0x2f3

fffff800`00b9c3b0 fffff880`04ac0b7d : fffffa80`051461a0 fffff880`04d07b20 fffffa80`067cd020 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110

fffff800`00b9c450 fffffa80`051461a0 : fffff880`04d07b20 fffffa80`067cd020 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d

fffff800`00b9c458 fffff880`04d07b20 : fffffa80`067cd020 fffff780`00000014 00000000`00000000 000005fc`00000100 : 0xfffffa80`051461a0

fffff800`00b9c460 fffffa80`067cd020 : fffff780`00000014 00000000`00000000 000005fc`00000100 00000000`00000000 : netw5v64+0x24cb20

fffff800`00b9c468 fffff780`00000014 : 00000000`00000000 000005fc`00000100 00000000`00000000 fffff880`04ac8fb9 : 0xfffffa80`067cd020

fffff800`00b9c470 00000000`00000000 : 000005fc`00000100 00000000`00000000 fffff880`04ac8fb9 fffff880`04d87f80 : 0xfffff780`00000014

 STACK_COMMAND:  kb

 

FOLLOWUP_IP:

netw5v64+5b7d

fffff880`04ac0b7d ??              ???

 

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

 

 

-- Mike Burr
Technology


Sunday, January 15, 2012 9:02 PM

 

I'm posting only now because I wanted to make sure the errors were gone for good. I had to force installing new drivers for the Intel Wifi i had. Now everything is ok.

 

Thank you very much for the help, 

king regards,

DV


Thursday, January 31, 2013 3:28 PM

Hi Andre,

Would you please check my similar problem also?

My computer has a bsod sometimes with this error message in the log: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff80002cd6c02). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 013113-19796-01.

My dump file is here: https://skydrive.live.com/redir?resid=8DE8C666E0DC270B!103

Thank you so much: As