Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

DRIVER IRQL NOT LESS OR EQUAL tcpip.sys Blue screen

- - - - -

  • Please log in to reply

#31
darkkuja2

darkkuja2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
Hi, I used to have memory leakage if I remember correctly I think it was my killer network driver. After updating it I think I havent had more leakage or at least as bad havent been monitoring it.

I dont know if it helps narrow something but just in case.
  • 0

Advertisements


#32
darkkuja2

darkkuja2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts

I enabled the driver verifier with all the option except the Concurrency Stress Test (new as of Windows 8) option. Does it says something when it finishes scanning the drivers or it just runs forever.


  • 0

#33
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

DV will run until you manually stop it which I recommend you do after a min/max of 72hrs if no BSOD occurs, 

 

Polite request;

 

Please avoid adding multiple posts while waiting for us to reply to your last post, edit your last post to include anything that you wish to add, this will ensure nothing gets overlooked which can sometimes happen if a thread has more than one page. 


  • 0

#34
darkkuja2

darkkuja2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts

Yeah my bad I was posting from my phone and I didn't have signal. Tried to delete them but didn't know how. My laptop crashes more during the week since I use it all day, I will let it run till tuesday night.


  • 0

#35
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

:thumbsup:


  • 0

#36
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Not heard back from you darkkuja2 , do you still require assistance or is the issue now resolved, an update would be appreciated.


  • 0

#37
darkkuja2

darkkuja2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts

It has crashed only once but it was with another error message. It looks up a lot but doesn't crash I think is mostly from the resource been used by the verifier. 

Attached is the dump.

Attached Files

  • Attached File  dump.zip   92.37KB   164 downloads

  • 0

#38
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts
Wireless device drivers again, see below in red;
 
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
BUGCHECK_STR:  0x133
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  d
 
LAST_CONTROL_TRANSFER:  from fffff80290df0fe7 to fffff80290dc9780
 
STACK_TEXT:  
ffffd001`dc8bfd48 fffff802`90df0fe7 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd001`dc8bfd50 fffff802`90cd87c7 : 00000000`00000000 00000000`00000001 fffff802`90f6ce38 ffffd001`dc895180 : nt! ?? ::FNODOBFM::`string'+0x18ee7
ffffd001`dc8bfde0 fffff802`90c169c5 : ffffe000`f4338020 ffffd001`dc895180 ffffe000`f433c0e0 ffffe000`eb2cc400 : nt!KeClockInterruptNotify+0xa7
ffffd001`dc8bff40 fffff802`90d74187 : ffffe000`ec645800 fffff802`90cccf5c ffffad80`dce7c0ab 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`dc8bff70 fffff802`90dcabaa : ffffe000`eb2cc400 ffffe000`f433c0e0 ffffcf81`b34bade0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x87
ffffd001`dc8bffb0 fffff802`90dcafd7 : 00000000`397e2015 00000000`397e1586 ffffe000`f433c0e0 fffff801`9c373123 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`216c3b80 fffff802`90cdb89f : ffffe000`f433c1f8 fffff801`9c34679b ffffcf81`ae036e70 ffffcf81`d0abcfc0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd000`216c3d10 fffff802`90d308d2 : 00000000`00000000 00000000`00000000 fffff801`9c3b0ae0 ffffcf81`ae036e70 : nt!KxWaitForSpinLockAndAcquire+0x1f
ffffd000`216c3d40 fffff801`9c34c413 : ffffe000`00000000 00000000`00000000 ffffe000`f433b010 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x32
ffffd000`216c3d70 fffff801`9988eef5 : ffffe000`f4338020 ffffd000`216c3f81 fffff801`998a2360 00000003`00000001 : nwifi!Pt6Receive+0x273
ffffd000`216c3dd0 fffff801`998a239e : ffffe000`ec645800 00000000`00000000 00000000`00000001 fffff801`9e326da4 : ndis!ndisCallReceiveHandler+0x85
ffffd000`216c3e20 fffff802`90d2de95 : ffffd000`216c3f81 ffffd000`216c3f68 00000000`00000001 fffff801`9e290000 : ndis!ndisDataPathExpandStackCallback+0x3e
ffffd000`216c3e70 fffff801`998a52a1 : ffffcf81`b34bade0 00000000`00000000 ffffcf81`bc5a0c70 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`216c3ec0 fffff801`9989150a : 00000000`00000000 00000000`00000005 00001f80`0010000f 0053002b`002b0010 : ndis!ndisExpandStack+0x19
ffffd000`216c3f00 fffff801`998ae938 : 00000000`00000000 ffffcf81`bc50cc70 ffffcf81`b34bade0 ffffe000`f2064364 : ndis!ndisInvokeNextReceiveHandler+0x29a
ffffd000`216c3fd0 fffff801`9988f0f4 : ffffcf81`bc50cc70 ffffcf81`b34bade0 00000000`00000000 00000000`00000000 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x1fe18
ffffd000`216c4070 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisFIndicateReceiveNetBufferLists+0x54
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nwifi!Pt6Receive+273
fffff801`9c34c413 448b4f10        mov     r9d,dword ptr [rdi+10h]
 
SYMBOL_STACK_INDEX:  9
 
SYMBOL_NAME:  nwifi!Pt6Receive+273
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nwifi
 
IMAGE_NAME:  nwifi.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  56fa3060
 
FAILURE_BUCKET_ID:  X64_0x133_VRF_nwifi!Pt6Receive+273
 
BUCKET_ID:  X64_0x133_VRF_nwifi!Pt6Receive+273
 
Please try updating the drivers for your wireless device and check the Device Manager for any yellow ! or red Xs.
 
In addition to the above, restart the computer to access the BIOS and check if the SATA controller is set to AHCI.
 
If not done already, disable DV - To turn Driver Verifier off - verifier /reset then re-boot 

  • 0

#39
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Not heard back from you darkkuja2, do you still require assistance or is the issue now resolved, an update would be appreciated.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP