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 and computer hangs every second


  • Please log in to reply
8 replies to this topic

#1 sety7000

sety7000

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:10 PM

Posted 04 August 2010 - 07:44 PM

I was playing a game and every now and then my computer starts to hang and then it got bad enough that it was just skipping/hanging every second, and then after about 10 minutes it finally blue screened. I dont know what the problem is, sometimes I was just browsing a website and it was starting to skip a little, I used the debugger tools and copy the dump to the clipboard here it is

oh my computer is gigabyte p55 usb 3 motherboard
cpu is intel i3 clarkdale dual core

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
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: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Wed Aug 4 15:50:27.934 2010 (UTC - 7:00)
System Uptime: 0 days 0:27:05.385
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
.....
*** ERROR: Symbol file could not be found. Defaulted to export symbols for fwpkclnt.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {b2000000520000, b2000000520000, 520000, 0}

*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for vwififlt.sys -
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+3d3e )

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

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

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 00b2000000520000, Actual security check cookie from the stack
Arg2: 00b2000000520000, Expected security check cookie
Arg3: 0000000000520000, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002c15000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc164

DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE: Expected 00b2000000520000 found 00b2000000520000

BUGCHECK_STR: 0xF7_ONE_BIT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800134ab7e to fffff80002c85600

STACK_TEXT:
fffff880`0781ec98 fffff880`0134ab7e : 00000000`000000f7 00b20000`00520000 00b20000`00520000 00000000`00520000 : nt!KeBugCheckEx
fffff880`0781eca0 fffff880`01349341 : fffffa80`037c1000 fffffa80`037be5b0 00000000`00000110 fffff880`0781f210 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x3d3e
fffff880`0781ece0 fffff880`0133ee9e : fffff880`0781f110 00000000`00000000 fffff880`0781f110 00000000`00000000 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x2501
fffff880`0781eee0 fffff880`018d43cf : fffff880`0781f210 00000000`00000000 00000000`00000000 00000000`0000000d : fwpkclnt!FwpmEventProviderFireNetEvent0+0x122
fffff880`0781f0d0 fffff880`018fef2a : 00000000`0000000d fffff880`0781f640 fffff880`0781f640 fffff880`0781f4c0 : tcpip+0xd33cf
fffff880`0781f1c0 fffff880`018fefbd : fffff880`0781f610 00000000`00000000 00000000`00005000 fffff880`06350034 : tcpip+0xfdf2a
fffff880`0781f410 fffff880`0188f5dc : fffffa80`060af030 00000000`00000006 fffff880`078147ef fffff880`0781f4e8 : tcpip+0xfdfbd
fffff880`0781f460 fffff880`01830339 : fffffa80`0474d000 fffffa80`04615cc0 00000000`00000014 fffffa80`054a6830 : tcpip+0x8e5dc
fffff880`0781f830 fffff880`0183041d : fffffa80`04615cc0 fffff880`0781fad8 fffffa80`0474d000 fffff880`0635003c : tcpip+0x2f339
fffff880`0781f9c0 fffff880`0187a4b0 : 00000000`00000000 fffffa80`0474d000 fffffa80`045ee718 fffffa80`045ee718 : tcpip+0x2f41d
fffff880`0781fa10 fffff880`01879c17 : fffff880`0635003c fffffa80`0474d000 00000000`00000000 fffff880`0185d400 : tcpip+0x794b0
fffff880`0781fb60 fffff880`0185c3c7 : fffffa80`04745000 fffffa80`045e35c2 fffffa80`04615000 00000000`00000000 : tcpip+0x78c17
fffff880`0781fc10 fffff880`0185c499 : fffff880`0781fd90 fffff880`0196c9a0 fffff880`0781fda0 fffff880`01835aeb : tcpip+0x5b3c7
fffff880`0781fcd0 fffff880`0185c990 : fffffa80`0474d000 fffffa80`052fba00 00000000`00000011 fffff880`0781fd90 : tcpip+0x5b499
fffff880`0781fd40 fffff880`0185b821 : fffffa80`0474d000 fffffa80`0474d000 fffff880`0196c9a0 00000000`052ce001 : tcpip+0x5b990
fffff880`0781fe20 fffff880`0185a272 : fffffa80`05c8d300 00000000`00000000 fffffa80`052ce001 fffff880`00000001 : tcpip+0x5a821
fffff880`07820020 fffff880`018736ba : fffffa80`052ce010 fffff880`07820150 fffffa80`052ce010 fffff880`00000000 : tcpip+0x59272
fffff880`07820100 fffff800`02c94d4a : fffffa80`060af030 fffff880`0781b000 00000000`00004800 00000000`00000000 : tcpip+0x726ba
fffff880`07820150 fffff880`018730e2 : fffff880`018735e0 fffff880`07820260 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`07820230 fffff880`0178e0eb : fffffa80`05cc68d0 00000000`00000000 fffffa80`04eaa1a0 fffffa80`04eaa1a0 : tcpip+0x720e2
fffff880`078202a0 fffff880`01757fc6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisIMInitializeDeviceInstance+0xb5b
fffff880`07820310 fffff880`016daa24 : fffffa80`04eaa1a0 00000000`00000002 00000000`00000001 fffffa80`060af030 : ndis!NdisIMNotifyPnPEvent+0x1926
fffff880`07820790 fffff880`016da9e9 : 00000000`00000000 00000000`00000000 fffffa80`05c9d810 00000000`00000001 : ndis!NdisFIndicateReceiveNetBufferLists+0xf4
fffff880`078207d0 fffff880`016da980 : fffff880`066405c0 fffffa80`059f1010 fffffa80`05c9d810 00000000`00000001 : ndis!NdisFIndicateReceiveNetBufferLists+0xb9
fffff880`07820810 fffff880`066097ee : fffffa80`059f1010 00000000`00000000 fffffa80`060af030 fffff880`066405c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`07820850 fffff880`016da9e9 : fffffa80`056b0a10 00000000`00000000 00000000`00000001 fffff880`044c1e6d : nwifi+0x97ee
fffff880`078208b0 fffff880`016da980 : 00000000`00000001 fffff880`02fb20bc fffffa80`0371e328 fffff880`0624f2e4 : ndis!NdisFIndicateReceiveNetBufferLists+0xb9
fffff880`078208f0 fffff880`02fae9c0 : fffff880`02fb5110 00000000`00000001 00000000`00000001 fffffa80`0371ed78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`07820930 fffff880`016f22b7 : fffffa80`04eaa1a0 fffffa80`054a6830 fffffa80`054a6830 00000000`00000001 : vwififlt!DllInitialize+0x3e30
fffff880`07820990 fffff880`04445e11 : fffffa80`04eaa1a0 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisIfAllocateNetLuidIndex+0xe467
fffff880`078209e0 fffff880`04445613 : fffffa80`05278040 fffff880`0444874d 00000000`00000000 fffff880`044e5d66 : athrx+0x17e11
fffff880`07820a60 fffff880`044c1f6b : fffffa80`05278040 fffffa80`05297030 fffffa80`054b8950 00000000`00000000 : athrx+0x17613
fffff880`07820aa0 fffff880`044c8981 : fffffa80`05297030 00000000`00000000 fffffa80`054b8950 fffffa80`04eaa1a0 : athrx+0x93f6b
fffff880`07820ad0 fffff880`04450847 : fffffa80`05297030 fffff880`031d3180 fffffa80`037d5060 fffff880`031d3180 : athrx+0x9a981
fffff880`07820b30 fffff880`0442f9ba : fffffa80`04868030 00000000`00000000 fffffa80`037d5168 fffff800`02c8c752 : athrx+0x22847
fffff880`07820b60 fffff880`0175ce4b : fffffa80`05278040 00000000`00000000 fffff880`07820c18 00000000`00000000 : athrx+0x19ba
fffff880`07820ba0 fffff880`016e2bfd : fffffa80`054b8c58 00000000`0000000a 00000000`00000003 00000000`00000003 : ndis!NdisMPauseComplete+0x263b
fffff880`07820c10 fffff880`01709b0c : 00000000`00000000 fffffa80`054b8c58 00000000`00000080 fffffa80`045ce910 : ndis!NdisFreeFragmentNetBufferList+0x36d
fffff880`07820cb0 fffff800`02f2aa86 : 00000000`1409bb9e fffffa80`037d5060 00000000`00000080 fffffa80`037d5060 : ndis!NetDmaAllocateChannel+0x56c
fffff880`07820d40 fffff800`02c63b06 : fffff880`031d3180 fffffa80`037d5060 fffff880`031ddfc0 fffff880`0145abf0 : nt!PsCreateSystemThread+0x6f2
fffff880`07820d80 00000000`00000000 : fffff880`07821000 fffff880`0781b000 fffff880`07820a00 00000000`00000000 : nt!KeTestAlertThread+0x93a


STACK_COMMAND: kb

FOLLOWUP_IP:
fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+3d3e
fffff880`0134ab7e cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+3d3e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fwpkclnt

IMAGE_NAME: fwpkclnt.sys

BUCKET_ID: WRONG_SYMBOLS

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,748 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:10 PM

Posted 04 August 2010 - 08:21 PM

Try the following.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#3 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:07:10 PM

Posted 04 August 2010 - 08:25 PM

Hello and welcome to Bleepingcomputer.


First off lets call attention to this part of your log.

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 00b2000000520000, Actual security check cookie from the stack
Arg2: 00b2000000520000, Expected security check cookie
Arg3: 0000000000520000, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

I would have to strongly advise you to download, update and run MalwareBytes to scan your computer for possible malware you may have aquired from a malicious web site.

http://www.malwarebytes.org/ Download the FREE version.

Also try this program Spybot search @ destroy http://www.safer-networking.org/en/ownmirrors1/index.html

Good luck and keep us informed.

Bruce.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#4 sety7000

sety7000
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:10 PM

Posted 04 August 2010 - 09:58 PM

here is what was in the BSOD.txt


==================================================
Dump File : 080410-21606-01.dmp
Crash Time : 8/4/2010 3:51:57 PM
Bug Check String : DRIVER_OVERRAN_STACK_BUFFER
Bug Check Code : 0x000000f7
Parameter 1 : 00b20000`00520000
Parameter 2 : 00b20000`00520000
Parameter 3 : 00000000`00520000
Parameter 4 : 00000000`00000000
Caused By Driver : fwpkclnt.sys
Caused By Address : fwpkclnt.sys+db7e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\080410-21606-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 070810-18766-01.dmp
Crash Time : 7/8/2010 8:24:40 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`967ab5fb
Parameter 2 : b3b7465e`e8f8c78d
Parameter 3 : fffff880`016680cc
Parameter 4 : 00000000`00000000
Caused By Driver : ndis.sys
Caused By Address : ndis.sys+570cc
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\070810-18766-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

#5 sety7000

sety7000
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:10 PM

Posted 04 August 2010 - 10:28 PM

holy wow......ok I used malware bytes and it found nothing, I used spybot and it says it found 123 problems......so now what do I do?

#6 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:07:10 PM

Posted 05 August 2010 - 12:11 AM

If it found 123 problems you should allow it to fix those problems, if you haven't already.

Some may be tracking cookies some may be what are called PUPS, or they may be malicious entries.

I suggest you allow SpyBot search & destroy to fix those issues, buy clicking the tab to FIX those.

Please keep us posted.

Bruce.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#7 sety7000

sety7000
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:10 PM

Posted 05 August 2010 - 12:37 AM

they were all tracking cookies, and the problem I seem to be experiencing is when I play a game called ragnarok online maybe its having issues running on win7 and then my computer hangs for some reason, I can play other games and they work just fine. for instance crysis

#8 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:07:10 PM

Posted 05 August 2010 - 06:26 PM

You can try two things that might work for you.

Locate the executable that starts your video game, right click it so a menu pops up, scroll down to where you see properties.
Click properties, the properties box will pop up, look for the compatibility tab. Look for Run As Administrator and put a check-mark in the empty box. Then click Apply.

Try running the game again, if it still does not run correctly, try going back to the properties window again and click the box next to Run in XP Mode and try the game again.

This has worked with a few games I had issues with, so its worth a try with your situation.

Please let me know if this has also worked for you.

Bruce.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#9 sety7000

sety7000
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:10 PM

Posted 05 August 2010 - 06:39 PM

if I run it in win xp compatibility mode and as admin or either or it still messed up and hangs a certain amount of time in the game but if I play the game in full screen then it wont, but when switching maps in the game sometimes I cant move and I have to alt+tab out of the game then go back in to be able to move my character with the mouse again.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users