Hello, papasmerf767. I will try to help you, but I need you to do something for me.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html. Please list the as detailed as possible with Manufacturer and Model number. Also, please include your PSU and CPU Cooler.
You had 2 dump files
Code:
[COLOR=red]REFERENCE_BY_POINTER (18)[/COLOR]
Arguments:
Arg1: fffffa800c7da570, Object type of the object whose reference count is being lowered
Arg2: fffffa8013ccf3a0, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000001000000000, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object’s reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
And
Code:
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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8015627100, The pool entry we were looking for within the page.
Arg3: fffffa80156276d0, The next pool entry.
Arg4: 000000000c5d0010, (reserved)
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c1100
GetUlongFromAddress: unable to read from fffff800032c11c0
fffffa8015627100 Nonpaged pool
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: WiFi GO! Serve
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8015627100, fffffa80156276d0, c5d0010}
[COLOR=red]Probably caused by : afd.sys[/COLOR] ( afd!AfdPoll32+864 )
Followup: MachineOwner
afd.sys is the Ancillary Function Driver for WinSock supplied by Windows Update. It has to do with network connectivity.
Please reinstall your Graphics driver following this tutorial, install only the Graphics Driver and the PhysX driver.
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html
Also, please open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Also, please make sure your system is configured for small memory dumps,
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Please make sure all of your Windows Updates are current.
