Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Stop 0x00000007


  • Please log in to reply
1 reply to this topic

#1 jimdsilva

jimdsilva

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:06 AM

Posted 02 March 2009 - 03:48 AM

I've been having this issue since I finished building my system. I have an Intel Core i7 chip on an EVGA X58 motherboard, 6GBs of RAM on Vista Ultimate 32-bit and everything is running perfectly. I've benchmarked it and tested it with Prime95 for over 8 hours without issues. Yet, I get this BSOD.

INVALID_SOFTWARE_INTERRUPT
Stop 0x00000007 (0x00000008 X X X)


The final three parameters I display as X's because they always seem to change, but the stop code is always 0x00000007 and the first parameter is always 0x00000008.

I installed a new sound device but had no problems. I uninstalled the sound device and still received the same error so I doubt that's related. I'm positive it's network hardware related. Whenever I use some form of dedicated network access (for example: video streaming, torrent downloads, copying files from shared network volumes, etc.) my system stops and gives me the error code.

Any help you guys can give me, I'd appreciate.
Here's my memory dump of the most recent crash:



Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82012000 PsLoadedModuleList = 0x8211f930
Debug session time: Mon Mar 2 02:52:23.978 2009 (GMT-5)
System Uptime: 0 days 0:07:24.675
WARNING: Process directory table base 3E8EF000 doesn't match CR3 00122000
WARNING: Process directory table base 3E8EF000 doesn't match CR3 00122000
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 807a3130, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for tmwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for tmtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
Probably caused by : tmwfp.sys ( tmwfp+177ee )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 807a3130
Arg3: 00000000
Arg4: 00000000

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

PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 0x28)
eax=a20b8d78 ebx=00000000 ecx=8213f300 edx=00000000 esi=00000000 edi=8fafe200
eip=8207d9b0 esp=a673cff4 ebp=a673d018 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!KiDeferredReadyThread+0xb:
8207d9b0 53 push ebx
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: spoolsv.exe

CURRENT_IRQL: 1b

LAST_CONTROL_TRANSFER: from 8207d997 to 8207d9b0

STACK_TEXT:
a673d018 8207d997 807a1120 8213f300 a673d060 nt!KiDeferredReadyThread+0xb
a673d028 8207ad1d 8fafe200 8fafe1f8 00000001 nt!KiProcessDeferredReadyList+0x1e
a673d060 8207a24e 8486ba72 00000000 00000007 nt!KiExitDispatcher+0x2a
a673d080 9d9197ee 8fafe1f8 00000000 00000000 nt!KeSetEvent+0xd4
WARNING: Stack unwind information not available. Following frames may be wrong.
a673d098 9d91c8cd 00000080 a673d35d a23297d1 tmwfp+0x177ee
a673d0b4 9d922d94 8f420be8 00000001 844622e0 tmwfp+0x1a8cd
a673d400 9d924d1d 00000000 00000001 844622e0 tmwfp+0x20d94
a673d75c 9d91e46b 00000000 962884f8 844622e0 tmwfp+0x22d1d
a673d790 9d91e4bc 00000003 00000000 00000000 tmwfp+0x1c46b
a673d7c0 88288409 a673dbb4 a673dad8 a5b7b200 tmwfp+0x1c4bc
a673d808 8828804f 00000030 a673dbb4 a673dad8 NETIO!ProcessCallout+0x10e
a673d878 882881e9 00000030 a673dbb4 a673dad8 NETIO!ArbitrateAndEnforce+0xaa
a673d95c 88335344 00000030 a673dbb4 a673dad8 NETIO!KfdClassify+0x16f
a673d984 88324b72 a673dbb4 a673dad8 a5b7b200 tcpip!WfpAleClassify+0x36
a673dc20 883245d8 9c90de88 00000030 8837b2c8 tcpip!WfpAlepAuthorizeSend+0x4c0
a673dd80 8833561c 9c90de88 a6730002 00000011 tcpip!WfpAleAuthorizeSend+0x1e0
a673dddc 88333c19 9c90de88 a6730002 00000011 tcpip!WfpAleConnectAcceptIndicate+0x56
a673de4c 883230c7 a673e05c 00000011 a6730002 tcpip!ProcessALEForTransportPacket+0xf3
a673ded0 88322c0f a673e05c 00000011 a6730002 tcpip!ProcessAleForNonTcpOut+0x5c
a673e020 88321cd4 00000011 00000000 00008900 tcpip!WfpProcessOutTransportStackIndication+0x200
a673e0a4 88321b28 00000000 9c906094 a673e208 tcpip!IppInspectLocalDatagramsOut+0xbf
a673e248 8831acab 00000000 00000004 88385c68 tcpip!IppSendDatagramsCommon+0x522
a673e268 8831bb19 84efbb30 a673e364 847d4e28 tcpip!IpNlpSendDatagrams+0x4b
a673e4b0 8f1afcf2 8486c150 84ebe218 847d4e28 tcpip!UdpSendMessages+0xc07
a673e4f8 8f1b79be 9ca68ae8 847d4e00 8451e258 tdx!TdxSendDatagramTransportAddress+0x206
a673e514 820581cd 8f63f030 847d4e28 847d4e28 tdx!TdxTdiDispatchInternalDeviceControl+0x5c
a673e52c 87ff4714 a673e5bc 10000000 9ca19364 nt!IofCallDriver+0x63
a673e540 87ff8043 8f79f288 847d4e28 847d4ee0 tmtdi+0x8714
a673e618 87ff8130 847d4e28 a673eb78 8f79f288 tmtdi+0xc043
a673eb1c 820581cd 8f79f288 847d4e28 9ca30150 tmtdi+0xc130
a673eb34 8f1dd8bf 9ca7c008 962cf5f0 8f1f7e84 nt!IofCallDriver+0x63
a673eb50 8f1dd72f 00000000 9ca7c104 00000032 netbt!TdiSendDatagram+0x14e
a673eb94 8f1dd5c5 9ca7c008 c0a801ff 00000032 netbt!UdpSendDatagram+0x14c
a673ebdc 8f1e1ed1 9ca7c008 8449ffc8 000fb008 netbt!SendNameServiceRequest+0x2a1
a673ec28 8f1e1adf a6202d1c 8f6580e8 000002ee netbt!QueryNameOnNet+0x376
a673ec6c 8f1d95bb a6202d1c 9619cc68 8f1d894a netbt!FindNameOrQuery+0x463
a673ecdc 8f1da093 00000000 00000000 9619ce90 netbt!NbtConnectCommon+0x79c
a673ecfc 8f1d9e4b a673ed24 9976a200 a61a141c netbt!NbtConnect+0x114
a673ed4c 8f1d76d2 9619cc68 848ff428 848ff428 netbt!NTConnect+0x1a2
a673ed68 87e476a5 e019cc68 848ff4e0 a61a1434 netbt!NbtDispatchInternalCtrl+0x16d
a673ed9c 820581cd 9619cc68 848ff428 00000000 sptd+0x1a6a5
a673edb4 8f1f9a64 8f1f7440 a61a1400 848ff428 nt!IofCallDriver+0x63
a673edcc 8f1d9e09 00000000 848ff428 00000000 netbt!DelayedNbtProcessConnect+0x100
a673ee1c 8f1d76d2 9619cc68 00000000 a5bfb570 netbt!NTConnect+0x160
a673ee38 87e476a5 e019cc68 a5bfb628 847b50f0 netbt!NbtDispatchInternalCtrl+0x16d
a673ee6c 820581cd 9619cc68 a5bfb570 9ca68a00 sptd+0x1a6a5
a673ee84 99760081 a61598d0 a61598e4 847b50f0 nt!IofCallDriver+0x63
a673eecc 9975f86f 00000103 00000003 a61598d0 mrxsmb!RxTdiInitiateAsynchronousConnect+0x1e8
a673eee4 9976d10f 017b50f0 3f05492b 00000000 mrxsmb!RxCeInitiateConnectRequest+0x38
a673ef44 9976cc30 8f903a68 00000000 847b50f0 mrxsmb!RxCeBuildConnectionOverMultipleTransports+0x266
a673ef8c 9976c557 8450e798 00000000 848c5a7c mrxsmb!VctEstablishConnection+0x2dd
a673efc8 99760491 848c5a30 848c5a30 848c5aec mrxsmb!SmbCeEstablishNegotiatedConnection+0x112
a673eff4 9976c8f2 848c5a30 8450e158 8450e168 mrxsmb!SmbCepEstablishServerConnection+0x54
a673f01c 9976c67a 00000000 a673f044 8fc2fa1e mrxsmb!SmbCeCreateSrvCall+0x19e
a673f028 8fc2fa1e 843e2838 8f902a38 8fc21188 mrxsmb!MRxSmbCreateSrvCall+0x23
a673f044 8fc31eb6 8f903c00 a5bdc8a8 843e2838 rdbss!RxConstructSrvCall+0xe2
a673f0b8 8fc32186 8f62b120 a5bdc8a8 a673f1e0 rdbss!RxFindOrCreateConnections+0x819
a673f100 8fc24c6d 8f62b120 a5bdc8a8 a673f1e0 rdbss!RxConstructVirtualNetRoot+0x68
a673f1b4 8fc3145b 8f62b120 a5bdc8a8 a673f1e0 rdbss!RxFindOrConstructVirtualNetRoot+0x492
a673f1fc 8fc3167f 8f62b101 8fc31521 8f62b120 rdbss!RxPrefixClaim+0x18c
a673f21c 8fc0b8e7 8f62b120 0000ec23 29b2126d rdbss!RxCommonDevFCBIoCtl+0x15e
a673f29c 8fc22897 8fc1e320 a5bdc8a8 96097028 rdbss!RxFsdCommonDispatch+0x59c
a673f2cc 9976b20e 8f903a68 0ebdc8a8 8a5bfb30 rdbss!RxFsdDispatch+0x19f
a673f2e8 820581cd 8f903a68 01bdc8a8 a673f328 mrxsmb!MRxSmbFsdDispatch+0x99
a673f300 8856351c 00000000 962b0458 a673f39c nt!IofCallDriver+0x63
a673f310 88562c37 a673f328 84769008 8450b008 mup!MupiIssueQueryRequest+0x19
a673f39c 885618f7 000d5118 a673f3c8 00000000 mup!MupLocateUncProviderForPath+0x146
a673f3cc 885611ad 8450b008 c0000016 a60d51d0 mup!MupiCallUncProvider+0xaf
a673f3e4 885621da 8450b008 2e25f5d5 00000000 mup!MupStateMachine+0x9b
a673f430 820581cd 8579e238 a60d5118 a60d5118 mup!MupCreate+0x109
a673f448 880a2ba7 a60d5118 00000000 a60d51f4 nt!IofCallDriver+0x63
a673f46c 880b5643 a673f48c 858a1db8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
a673f4b8 820581cd 858a1db8 858a1950 a60d5118 fltmgr!FltpCreate+0x2a1
a673f4d0 880a2ba7 a60d5118 00000000 a60d5218 nt!IofCallDriver+0x63
a673f4f4 880b5643 a673f514 8fbb95c8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251


STACK_COMMAND: .tss 0x28 ; kb

FOLLOWUP_IP:
tmwfp+177ee
9d9197ee 8bc6 mov eax,esi

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: tmwfp+177ee

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tmwfp

IMAGE_NAME: tmwfp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4884693e

FAILURE_BUCKET_ID: 0x7f_8_tmwfp+177ee

BUCKET_ID: 0x7f_8_tmwfp+177ee

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:06 AM

Posted 02 March 2009 - 07:36 PM

tmwfp.sys has to do with your Trend Micro software. On occasion I've seen network issues with this sort of problem - usually with an Internet Security type product (rather than an anti-virus).

Download a new copy of some sort of anti-virus application (a trial will do). Then uninstall the Trend Micro and IMMEDIATELY install the new anti-virus application. For now let Windows Defender handle your anti-spyware needs and the Windows Firewall can handle the internet access issues.

Should the BSOD's continue, and continue to point to Trend Micro - then you'll have to use the Trend Micro uninstaller that's available on the disk that the product was installed from (don't have the link handy right now - I'm traveling).

As a caveat, not all BSOD issues are solved with the first BSOD - so keep posting if you get other errors.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users