Jump to content

aparsons

Honorary Members
  • Posts

    26
  • Joined

  • Last visited

Reputation

0 Neutral

About aparsons

  • Birthday 10/26/1969

Profile Information

  • Location
    /var/dev/null
  1. Mate, Thanks for providing that information, I appreciate it. Could you try the 2nd chance exception by changing the -e 1 to -e 2 procdump -e 2 <processid> c:\Windows e.g procdump -e 2 2944 c:\Windows
  2. Mate, This might provide more information. Could you please download procdump from HERE. Run a command prompt as Administrator and type in: procdump -e 1 <processid> c:\Windows e.g procdump -e1 2944 c:\Windows If/When the mbamservice.exe process crashes procdump should catch the 1st chance exception. Which, I'm hoping will contain more information.
  3. Mate, Just to cover bases there is a Intel Driver update utility HERE. You didn't state whether or not you had checked the Intel web site or not. So I apologize if you already had. The only crash dump file that I had access to was in your post number 4. It didn't have Special Pool or Pool tracking enabled. (See Below) Verify Flags Level 0x00000000 STANDARD FLAGS: [X] (0x00000000) Automatic Checks [ ] (0x00000001) Special pool [ ] (0x00000002) Force IRQL checking [ ] (0x00000008) Pool tracking [ ] (0x00000010) I/O verification [ ] (0x00000020) Deadlock detection [ ] (0x00000080) DMA checking [ ] (0x00000100) Security checks [ ] (0x00000800) Miscellaneous checks ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [ ] (0x00000040) Enhanced I/O checking [ ] (0x00000200) Force pending I/O requests [ ] (0x00000400) IRP logging [X] Indicates flag is enabled If Special Pool was enabled we *might* have found the culprit, because verifier additionally checks the padding that is used when an allocation is rounded up to an even page boundary, that allocation is then surrounded by Invalid pages. Do you have a crash dump with just Special Pool enabled? If does work it would be worth tagging all non-microsoft drivers. I can't see what, if any, drivers were tagged because it is a mini kernel dump. To be fair testing on another 64bit box is not a real help, unless it was a 64 bit version of your Gateway FX530. I don't have access to your IRQL crashes or even the one where Special Pool was enabled, unless you want to make them available, so I can't comment on those. Another possible problem is that you appear to have multiple AV / Malware products installed. (F-Secure, Spybot - Search & Destroy 2, McAfee and of course Malwarebytes.) As a suggestion, you could uninstall them and just use Microsoft Windows Defender and Malwarebytes Pro just to see if the problem persists. Sometime some AV / Malware products get over zealous. *if* the Dev's find that it is Driver related, you might not be able to get a fix because your hardware is now 7 years old and some vendors may have marked your hardware end-of-life.
  4. Mate, I am just an amateur, but I would suggest that you update your network drivers. Looking at the stack mwac was doing something then Windows tried to "Construct IP Header For Transport" and then free some memory. # ChildEBP RetAddr 00 c3516844 82ef9184 nt!KeBugCheckEx+0x1e01 c35168bc 89a9f2d2 nt!ExFreePoolWithTag+0x17f02 c3516a4c 89af1835 tcpip!IppInspectBuildHeaders+0x56703 c3516a9c b16f03d1 fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x161WARNING: Stack unwind information not available. Following frames may be wrong.04 c3516af0 b16f076e mwac+0x53d105 c3516b0c b16f06d7 mwac+0x576e06 c3516b38 b16f0e34 mwac+0x56d707 c3516b54 b16ee833 mwac+0x5e3408 c3516b6c b16edea4 mwac+0x383309 c3516bc0 b16edad2 mwac+0x2ea40a c3516be0 b16ee6f0 mwac+0x2ad20b c3516bfc b16f338a mwac+0x36f00c c3516c1c b16f2293 mwac+0x838a0d c3516c2c 82e5097a mwac+0x72930e c3516c44 83052e25 nt!IofCallDriver+0x630f c3516c64 830535ca nt!IopSynchronousServiceTail+0x1d910 c3516d00 83054694 nt!IopXxxControlFile+0x6b711 c3516d34 82e56c96 nt!NtDeviceIoControlFile+0x2a12 c3516d34 77da5d14 nt!KiSystemServicePostCall13 13faf798 00000000 0x77da5d14 If your going to run Driver Verifier, then perhaps Select: ---- Special Pool ---- Pool Tracking In regards to the IRQL_NOT_LESS_OR_EQUAL that could be another problem. Driver Verifier makes sure that Drivers are behaving correctly. So if a driver is poorly written then it will trip Driver Verifier. Hope this helps.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.