PROBLEMA Driver IRQL schermo blu

[van Kuss]

Questa domanda ve l'avranno fatta in milioni, molto probabilmente. Purtroppo, non c'è una soluzione unica: ho provato a fare tutto quello che c'era da fare, e il fantomatico schermo blu della morte continua a comparire.

Quando uso programmi peer 2 peer, specialmente uTorrent, da un momento all'altro può comparire questa schermata. L'errore è sempre lo stesso: DRIVER IRQL NOT LESS OR EQUAL e poi una sfilza di informazioni e altre cose. Ho formattato non una, ma ben due volte, e l'errore non ha accennato a rimuoversi.

Quando si entra in questo campo preferisco chiedere aiuto piuttosto che cavarmela da solo, rischiando di compromettere seriamente qualcosa. Per questo, ecco il file nella cartella \Windows\Minidump che genera l'errore. Spero che qualcuno più esperto riesca a leggerlo.

Ciao e grazie a tutti!

Spoiler

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Primary Analysis


Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`030a1670
Debug session time: Mon Apr 16 13:46:35.827 2012 (UTC - 4:00)
System Uptime: 0 days 4:40:20.952
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800197bb2d, address which referenced memory


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




READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b100
0000000000000028


CURRENT_IRQL: 2


FAULTING_IP:
NETIO!RtlCopyBufferToMdl+1d
fffff880`0197bb2d 448b5228 mov r10d,dword ptr [rdx+28h]


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


BUGCHECK_STR: 0xD1


PROCESS_NAME: System


TRAP_FRAME: fffff880035a0520 -- (.trap 0xfffff880035a0520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880035a0740 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800197bb2d rsp=fffff880035a06b0 rbp=fffff880035a07e0
r8=00000000ffffffbc r9=0000000000000044 r10=0000000000000000
r11=fffffa800425a170 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
NETIO!RtlCopyBufferToMdl+0x1d:
fffff880`0197bb2d 448b5228 mov r10d,dword ptr [rdx+28h] ds:0010:00000000`00000028=????????
Resetting default scope


LAST_CONTROL_TRANSFER: from fffff80002ed81e9 to fffff80002ed8c40


STACK_TEXT:
fffff880`035a03d8 fffff800`02ed81e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`035a03e0 fffff800`02ed6e60 : fffffa80`06594140 fffff880`01ab9dd2 fffff880`035a0570 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`035a0520 fffff880`0197bb2d : 00000000`00000072 fffff880`01a70fec 00000000`0000000b fffffa80`041f72e8 : nt!KiPageFault+0x260
fffff880`035a06b0 fffff880`01af8bac : 00000000`00000000 fffff880`01ac7906 00000000`00000001 00000000`00000000 : NETIO!RtlCopyBufferToMdl+0x1d
fffff880`035a0710 fffff880`01ac4ef3 : fffffa80`0425a170 00000000`00000001 fffffa80`09b8ebc0 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d5cf
fffff880`035a0780 fffff880`01ab7d54 : fffff880`035a0c38 00000000`00000029 fffffa80`09b8ebc0 00000000`00000001 : tcpip!TcpTcbCarefulDatagram+0x543
fffff880`035a0930 fffff880`01ab667a : fffffa80`06459f00 fffff880`01aaeb34 fffffa80`06420448 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`035a0ae0 fffff880`01ab82ab : fffff880`05165512 fffffa80`0657b000 00000000`00000000 fffff880`035a0e00 : tcpip!TcpMatchReceive+0x1fa
fffff880`035a0c30 fffff880`01aaf1c7 : fffffa80`06459f00 fffffa80`064683ee fffffa80`0000ff5b 00000000`0000ff5b : tcpip!TcpPreValidatedReceive+0x36b
fffff880`035a0d00 fffff880`01aaed3a : 00000000`00000000 fffff880`01bc9800 fffff880`035a0ec0 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x97
fffff880`035a0dc0 fffff880`01aae339 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`035a0eb0 : tcpip!IppProcessDeliverList+0x5a
fffff880`035a0e60 fffff880`01aac0af : 00000000`00000000 00000000`06cf0000 fffff880`01bc9800 fffff880`01bc9800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`035a0f40 fffff880`01aab6a2 : fffffa80`06ceade0 00000000`00000000 fffffa80`06cf0000 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`035a1140 fffff880`01b2a34a : fffffa80`087fa080 00000000`00000004 fffffa80`06cf0010 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`035a1220 fffff800`02ee5618 : 00000000`00000000 fffff880`01bc0800 fffffa80`03cd5040 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x55122
fffff880`035a1270 fffff880`01aab202 : fffff880`01aaaa60 fffff880`05049ba2 fffffa80`06de7000 fffff880`01977e01 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`035a1350 fffff880`019360eb : fffffa80`06cf1010 00000000`00000000 fffffa80`069121a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`035a13c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb




STACK_COMMAND: kb


FOLLOWUP_IP:
NETIO!RtlCopyBufferToMdl+1d
fffff880`0197bb2d 448b5228 mov r10d,dword ptr [rdx+28h]


SYMBOL_STACK_INDEX: 3


SYMBOL_NAME: NETIO!RtlCopyBufferToMdl+1d


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: NETIO


IMAGE_NAME: NETIO.SYS


DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381


FAILURE_BUCKET_ID: X64_0xD1_NETIO!RtlCopyBufferToMdl+1d


BUCKET_ID: X64_0xD1_NETIO!RtlCopyBufferToMdl+1d


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




This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Crash Code Links


Information About Address 0x28


Loaded Module List


Raw Stack Contents


Dump Header Information


Strings

 

[Federico83]

segui questa guida in inglese Fix Damaged Pagefile




The page file may be corrupt. To fix this:
Boot into the Recovery Console command prompt from the Windows boot installation CD/DVD.
Delete the Page File, which is in the system root directory by typing: del pagefile.sys
Next you need to run the check disk by typing: chkdsk /r
Exit the recovery console and reboot into Windows.
You'll need to create a new pagefile and/or verify the settings.
For Windows 7, Vista and Server 2008:
Select Start, then right-click on Computer, and select Properties.
Select Advanced system settings.
In System Properties, select the Advanced Tab, and under Performance, select the Settings button.
In Performance Options, select the Advanced Tab. The lower box Virtual Memory shows the paging file size. If it is off or set wrong, you can change the options using the Change button. Typically the "Automatically manage ... " option is best.
For Windows XP Server 2003:
Select Start, then right-click on My Computer, and select Properties.
In System Properties, select the Advanced Tab, and under Performance, select the Settings button.
In Performance Options, select the Advanced Tab. The lower box Virtual Memory shows the paging file size. If it is off or set wrong, you can change the options using the Change button. Use either System managed size or custom

 

[van Kuss]

Provo e faccio sapere... prima che trovo il CD di Windows 7... :D
Grazie.

 

[Federico83]

poi guarda anche questo link DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[van Kuss]

Ho provato tutte le soluzioni, e tutte risultano non aver toccato il problema... l'unica cosa di quella procedura è che il "chdksk /r" non me lo fa eseguire, dice che è protetto in sola lettura. Forse c'è un modo per poterlo eseguire lo stesso?

 

[Federico83]

non te lo fa eseguire subito ma al riavvio è del tutto normale un comportamento del genere

 

[Diego Sepe]

non te lo fa eseguire subito ma al riavvio è del tutto normale un comportamento del genere

mmmm ho un problema simile, solo che il mio sony vaio non ha il lettore ottico, come faccio?

 

[Federico83]

mmmm ho un problema simile, solo che il mio sony vaio non ha il lettore ottico, come faccio?

apri una nuova discussione grazie