Forum Home
Press F1
 
Thread ID: 138121 2014-10-07 20:16:00 New Business Desktop dpDesignz (15919) Press F1
Post ID Timestamp Content User
1385835 2014-10-09 04:17:00 Just reading / Analizing the Bug Check -- You may want to uninstall Networx as well ( network Monitor)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: networx.exe


Notice the number 0x133 -- That's the cause of every 0x133 Crash according to the check. Had that happen on my W7 a while back so its been uninstalled. 		wainuitech (129)
1385836 2014-10-09 19:30:00 Just reading / Analizing the Bug Check -- You may want to uninstall Networx as well ( network Monitor)


Notice the number 0x133 -- That's the cause of every 0x133 Crash according to the check. Had that happen on my W7 a while back so its been uninstalled.

Oh bugger :(. I use that to monitor the traffic and usage from our staff. Do you know any alternatives you would recommend? 		dpDesignz (15919)
1385837 2014-10-09 19:59:00 Oh bugger :(. I use that to monitor the traffic and usage from our staff. Do you know any alternatives you would recommend? Nope, its a bit of a bugger as I used Networx for ages. Then one day I did an update on it and the crashing started. Try removing it and see if the crashing stops.

Went through the following dumps, 20953,17093,27484 all which had the 0x133 message, all say the exact same thing. The only exception is 55781, which has 0x19.

Below are the actual reports or part of.

As you can see by the first, 0x19, its already on its way to crashing - In bold:
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 000000000000000e,
Arg2: ffffd000215f4290
Arg3: fffff8019fa15900
Arg4: 376ba0ac27377022

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


BUGCHECK_STR: 0x19_e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

And the full report for every 0x133 you posted, look for the crash Error 0x133 and the exe that caused it ( under debugging details - Bug Check and process Name) --- networx.


Bugcheck Analysis *
* *
************************************************** *****************************

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:
------------------


DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: networx.exe

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff8030d391d18 to fffff8030d368ca0

STACK_TEXT:
ffffd001`f1565c98 fffff803`0d391d18 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt! KeBugCheckEx
ffffd001`f1565ca0 fffff803`0d277115 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff803`0d36a500 : nt! ?? ::FNODOBFM::`string'+0x18b68
ffffd001`f1565d30 fffff803`0d9a67b5 : 00000000`00400a02 ffffd001`ed97e470 fffff800`6f1a11c0 ffffd000`00006101 : nt! KeClockInterruptNotify+0x95
ffffd001`f1565f40 fffff803`0d2ee0e3 : ffffd001`f1565f60 00000000`00000008 ffffd001`f1565f50 00000000`0000000c : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`f1565f70 fffff803`0d36a12a : fffff803`0d9f2d00 ffffd000`236122a0 ffffd000`236124c0 00000000`00000000 : nt! KiCallInterruptServiceRoutine+0xa3
ffffd001`f1565fb0 fffff803`0d36a50f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`23611e90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! KiInterruptDispatchLBControl+0x11f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+18b68
fffff803`0d391d18 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+18b68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0b7c3

IMAGE_VERSION: 6.3.9600.17238

BUCKET_ID_FUNC_OFFSET: 18b68

FAILURE_BUCKET_ID: 0x133_ISR_ nt! _ ?? _::FNODOBFM::_string_

BUCKET_ID: 0x133_ISR_ nt! _ ?? _::FNODOBFM::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_ nt! _ ?? _::fnodobfm::_string_

FAILURE_ID_HASH: {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}

Followup: MachineOwner
--------- 		wainuitech (129)
1385838 2014-10-09 20:38:00 Would a router with gargoyle on it do what networx does and if so wouldn't that be a better way?
I have never actually played with it but seen it recommended here a lot and looked at some info that makes me think it would do the trick.
Of course that might mean a new router etc. 		dugimodo (138)
1385839 2014-10-09 20:41:00 Nope, its a bit of a bugger as I used Networx for ages. Then one day I did an update on it and the crashing started. Try removing it and see if the crashing stops.

Went through the following dumps, 20953,17093,27484 all which had the 0x133 message, all say the exact same thing. The only exception is 55781, which has 0x19.

Below are the actual reports or part of.

As you can see by the first, 0x19, its already on its way to crashing - In bold:

And the full report for every 0x133 you posted, look for the crash Error 0x133 and the exe that caused it ( under debugging details - Bug Check and process Name) --- networx.

Hmm, well that sucks. :(. Weird though as it's deployed across over 20 workstations on site and mine's the only one crashing. Will remove and see how that goes. So far no crashes since 11:30am yesterday so fingers crossed :). I really do appreciate the help! 		dpDesignz (15919)
1385840 2014-10-09 20:43:00 Would a router with gargoyle on it do what networx does and if so wouldn't that be a better way?
I have never actually played with it but seen it recommended here a lot and looked at some info that makes me think it would do the trick.
Of course that might mean a new router etc.

Thanks. Will look in to that. Pretty much all I need is to be able to monitor usage per device, how much per app, and a bandwidth monitor. 		dpDesignz (15919)
1385841 2014-10-09 20:50:00 Hmm, well that sucks. :(. Weird though as it's deployed across over 20 workstations on site and mine's the only one crashing. Will remove and see how that goes. So far no crashes since 11:30am yesterday so fingers crossed :). I really do appreciate the help!

Looks like I'm not the only one! www.softperfect.com Fingers crossed these fixes help. :) 		dpDesignz (15919)
1385842 2014-10-09 22:08:00 Hopefully it is just networx -- When relooking at the previous files posted, 0x19 which was already on its way says:


Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+147900
File Description : TCP/IP Driver



Networxs of course uses the TCP/IP which would make sense and relate to the 0x133 		wainuitech (129)
1385843 2014-10-19 23:59:00 It's happened again :(. 3 times today. Would you be able to check my latest logs please? www.dropbox.com dpDesignz (15919)
1385844 2014-10-20 02:26:00 According to the bug checks / Dumps

18515 error 0x19 was caused by Chrome: ( probably triggered by the others as it says Bad Pool header - The pool is already corrupt at the time of the current request.)



Bugcheck Analysis *
* *
************************************************** *****************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 000000000000000d,
Arg2: ffffd00023f4d290
Arg3: fffff80100000000
Arg4: 4326c8d322c2f6d0

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


BUGCHECK_STR: 0x19_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800c9f17ced to fffff800c9dd5ca0

22046 & 91859, both the same error 0x133 Caused again By networx.exe -- Under process Name (which would make sense since chrome uses TCPIP protocols and network monitors them --- So if networx is causing troubles, then chrome may have said bugger you I'm going AWOL :) ).


Bugcheck Analysis

************************************************** *****************************

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:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: networx.exe

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff8008f1f6d18 to fffff8008f1cdca0

STACK_TEXT:
ffffd001`47b8fc98 fffff800`8f1f6d18 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt! KeBugCheckEx
ffffd001`47b8fca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x18b68


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+18b68
fffff800`8f1f6d18 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+18b68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0b7c3

FAILURE_BUCKET_ID: X64_0x133_ nt! _ ?? _::FNODOBFM::_string_+18b68

BUCKET_ID: X64_0x133_ nt! _ ?? _::FNODOBFM::_string_+18b68

Followup: MachineOwner
--------- 		wainuitech (129)
1 2 3 4 5 6