Applies to

Problem Event Name: BlueScreen

Rao D asked on

My computer restarted with this error two times .. this happened only when I was using internet . I'm not a great expert . I hv lots of updates are pending critical and optional both . the reason is I hv 2g internet . okay I wanna know can this error lead to corruption of  window 7 home premium ,







Problem signature:



Problem Event Name: BlueScreen

OS Version: 6.1.7601.

Locale ID: 16393

Additional information about the problem:



BCCode: d1

BCP1: 00000004

BCP2: 00000002

BCP3: 00000000

BCP4: 886F2051

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:





Read our privacy statement online:


If the online privacy statement is not available, please read our privacy statement offline:


2 people had this question

Abuse history

The answered status icon Answer
Patrick Barker replied on


The attached DMP file is of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.

A kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high.

Usual causes are a device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.

As we can see from the call stack:

bdf85690 886f2051 badb0d00 00000191 00000002 nt!KiTrap0E+0x1b3
bdf85710 886f251e 84495720 84a658ec bdf85730 NETIO!CalloutStreamDataInit+0xe
bdf85758 886f28d0 bdf857f4 84a65868 84a658d0 NETIO!StreamInvokeCalloutAndNormalizeAction+0x2f
bdf85788 886f29eb bdf857f4 84a65868 84a658d0 NETIO!StreamCalloutProcessData+0x31
bdf857c8 886f2e51 bdf857f4 84a65868 84a658d0 NETIO!StreamCalloutProcessingLoop+0x55
bdf85834 886e0f5a 00000014 8899c3f8 00000000 NETIO!StreamProcessCallout+0x128
bdf85898 886cbb3e 00000014 a51d6cd0 abe460e0 NETIO!ProcessCallout+0x120
bdf8590c 886ca21f 00000014 a51d6cd0 abe460e0 NETIO!ArbitrateAndEnforce+0xae
bdf85a1c 886f1ad9 00000014 a51d6cd0 abe460e0 NETIO!KfdClassify+0x1c7
bdf85aa8 886f3339 0001beda 00000014 a51d6cd0 NETIO!StreamInternalClassify+0x84
bdf85b04 886eec85 00000014 abe46008 844431b8 NETIO!StreamInject+0x13f
bdf85b48 8896dc40 00001e7b 00000000 00000133 NETIO!FwppStreamInject+0xde
bdf85b80 be05ea8e 865c2bf0 00000000 00000000 fwpkclnt!FwpsStreamInjectAsync0+0x93
WARNING: Stack unwind information not available. Following frames may be wrong.
bdf85bd4 be05eb68 00001578 00001e7b 00000000 UrlFilter+0x1a8e
bdf85bfc 81c7bc1e 841a5ad0 83f1e1c8 83f1e1c8 UrlFilter+0x1b68
bdf85c14 81e6fbe9 84582d70 83f1e1c8 83f1e238 nt!IofCallDriver+0x63
bdf85c34 81e72dd2 841a5ad0 84582d70 00000000 nt!IopSynchronousServiceTail+0x1f8
bdf85cd0 81eb9751 841a5ad0 83f1e1c8 00000000 nt!IopXxxControlFile+0x6aa
bdf85d04 81c828c6 000006d0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
bdf85d04 76e770f4 000006d0 00000000 00000000 nt!KiSystemServicePostCall
0d75eb90 00000000 00000000 00000000 00000000 0x76e770f4

UrlFilter.sys was called as a driver and then eventually went through a few NETIO routines but then that went into the bugcheck. UrlFilter.sys is the culprit here, and is a component of IObit's Malware Fighter.

I'd recommend removing IObit Malware Fighter ASAP for temporary troubleshooting purposes.



Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history