Question
Applies to
263 views

BLUESCREEN ERROR in WINDOWS 7 32 BIT

SHRAVANPARSHURAM PURIA asked on

this problem is since last 2 months. The system crashes once or twice in a day or may be once or twice in a week! And I get this error report when i log in to the system again.

Problem signature:

  Problem Event Name:                        BlueScreen

  OS Version:                                          6.1.7601.2.1.0.768.2

  Locale ID:                                             1033

 

Files that help describe the problem:

  C:\Windows\Minidump\050814-14929-01.dmp

  C:\Users\SHYAM\AppData\Local\Temp\WER-51339-0.sysdata.xml

2 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Thanks!

All of the attached DMP files are of the IRQL_NOT_LESS_OR_EQUAL (a) bug check.

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

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

0: kd> k
ChildEBP RetAddr  
8d7971e0 83287ef3 nt!KiTrap0E+0x2cf
8d79725c 9172eac9 nt!memcpy+0x33
WARNING: Stack unwind information not available. Following frames may be wrong.
8d797298 916d3c69 afd+0x37ac9
8d797384 8ba8ffe5 tdx!TdxEventReceiveConnection+0x23f
8d797414 8ba8c56f tcpip!TcpIndicateData+0x203
8d7974a8 8ba8e456 tcpip!TcpDeliverDataToClient+0x2fa
8d7974fc 8bac1ca7 tcpip!TcpDeliverReceive+0x96
8d797594 8bac0214 tcpip!TcpTcbCarefulDatagram+0x1769
8d797600 8baa37c8 tcpip!TcpTcbReceive+0x228
8d797668 8baa3ffa tcpip!TcpMatchReceive+0x237
8d7976b8 8baa403b tcpip!TcpPreValidatedReceive+0x293
8d7976d4 8ba9e335 tcpip!TcpReceive+0x2d
8d7976e4 8baa659b tcpip!TcpNlClientReceiveDatagrams+0x12
8d797710 8baa5ee6 tcpip!IppDeliverListToProtocol+0x49
8d797730 8baa42a8 tcpip!IppProcessDeliverList+0x2a
8d797788 8baa5d8f tcpip!IppReceiveHeaderBatch+0x1fb
8d79781c 8bab41db tcpip!IpFlcReceivePackets+0xbe5
8d797898 8baae80d tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
8d7978cc 832d7d74 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
8d797934 8baae97b nt!KeExpandKernelStackAndCalloutEx+0x132
8d797970 8b87918d tcpip!FlReceiveNetBufferListChain+0x7c
8d7979a8 8b8675be ndis!ndisMIndicateNetBufferListsToOpen+0x188
8d7979d0 8b8674b2 ndis!ndisIndicateSortedNetBufferLists+0x4a
8d797b4c 8b812c2d ndis!ndisMDispatchReceiveNetBufferLists+0x129
8d797b68 8b867553 ndis!ndisMTopReceiveNetBufferLists+0x2d
8d797b90 8b812c88 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
8d797bb8 91ccd6b7 ndis!NdisMIndicateReceiveNetBufferLists+0x52
8d797bd8 91cc8730 tunnel!TeredoWfpIndicationWorker+0xa9
8d797bec 8346457c tunnel!LwWorker+0x12
8d797c00 832cc1eb nt!IopProcessWorkItem+0x23
8d797c50 8345907a nt!ExpWorkerThread+0x10d
8d797c90 832ff819 nt!PspSystemThreadStartup+0x9e
00000000 00000000 nt!KiThreadStartup+0x19

We have many different network related routines being called, such as ndis.sys, tunnel.sys, tcpip.sys, etc. With this said, we likely have a 3rd party driver causing NETBIOS conflicts.

-----------------------

I took a look at your loaded modules list and I saw QuickHeal. Please remove and replace QuickHeal with MSE as QuickHeal known to cause corruption and conflicts:

QuickHeal removal - http://www.quickheal.com/prod-rem

Regards,

Patrick

MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress