Won't reboot after memtest86

D

dcjohnson50

Contributor
Joined
Sep 17, 2013
Posts
20
Have been getting several BSOD's over the past week or so, and have been lurking here, soaking up information in an effort to isolate/solve the problem before asking for help.

While going through the list of troubleshooting tests I ran memtest86 overnight. I checked it before going to bed, 1.5 hours in with no problems. When I got up, the machine had restarted and now it will not boot. Power light comes on, fans spool up, but nothing. Digging around found some information about resetting the CMOS. Is that the recommended way to fix that problem?? And if so, what's the proper way to perform the reset?

I'm guessing that's a pretty good sign bad memory was encountered.


Info:
2.5 year old HP box, OEM Windows 7 Home. Upgraded memory from 4gb to 16gb in January. This brand:

Pareema 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600) Desktop Memory Model MD313D81609L2 - Newegg.com

Also, updated power supply in January due to a noisy fan. And replaced the CD/DVD burner in July because the other gave up the ghost.

If I can get the box to reboot, I'll replace the memory with the old 2gb sticks to test.

Thank you for any help.
 
Swap the memory out now and see if it will boot.

What is the model number of the PC?
Usually found on a tag on the back or bottom of the PC.
 
That could be any number of issues....if you get no post, try booting with only one or the other mem stick in there and see if one will let you boot, if not try the other...if neither will let it boot, it's probably another issue (bad caps, mb failure, vga failure, etc...)

You could also try no memory, assuming your mb or chassis has a beep speaker, you should get beep codes with no mem, If not, the likely culprit is the mb....this is not certain, for example another bad device can also cause a no post scenario.
 
Running the HD diagnostic now. I ran the Seagate short test and it passed, long test running now. Will report results.
 
From the last 5 there 5 different named causes.
wdcsam64.sys Wed Apr 16 04:39:08 2008 is a known trouble maker > Driver Reference Table

DDCDrv.sys Tue Apr 8 03:50:11 2008 is part of a program called WinI2C-DDC used to control display devices I would remove it for the time being.



Debug session time: Tue Sep 17 17:56:53.875 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091713-58375-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:12:01.093
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+9f )
BugCheck 3B, {c0000005, fffff800037c72bf, fffff8800bcda0b0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800037c72bf, Address of the instruction which caused the bugcheck
Arg3: fffff8800bcda0b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!IoRemoveIoCompletion+9f
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Sep 16 20:58:49.779 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091613-50825-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:29:46.044
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BugCheck 4E, {99, 14376e, 2, 1fcd8d}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000014376e, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000001fcd8d, 0
BUGCHECK_STR: 0x4E_99
PROCESS_NAME: avgnsa.exe
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Sep 16 17:44:10.951 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091613-53898-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:13:46.590
Probably caused by : Wdf01000.sys ( Wdf01000!FxRequestFromLookaside::SelfDestruct+f )
BugCheck D1, {5b, 2, 0, fffff88000eb5187}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments:
Arg1: 000000000000005b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000eb5187, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_Wdf01000!FxRequestFromLookaside::SelfDestruct+f
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Sep 16 17:26:57.554 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091613-54381-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 19:48:48.193
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
BugCheck A, {80, 2, 1, fffff800034f9642}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800034f9642, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: DVD Shrink 3.2
FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Sep 15 14:32:53.096 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091513-54522-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 23:18:43.735
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys
BugCheck 9F, {3, fffffa800cd4fa10, fffff80000ba2748, fffffa800d0ebe10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800cd4fa10, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800d0ebe10, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_netr28x.sys
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***




AODDriver2.sys Tue Mar 6 04:55:00 2012 (4F55DEF4)
AnyDVD.sys Wed Jul 31 07:23:56 2013 (51F8F3CC)
AtiPcie64.sys Wed Mar 10 09:33:45 2010 (4B97ADC9)
AtihdW76.sys Fri May 11 04:25:40 2012 (4FACCD04)
DDCDrv.sys Tue Apr 8 03:50:11 2008 (47FB23B3)
ElbyCDIO.sys Mon Mar 4 04:21:51 2013 (513467AF)
GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1)
PxHlpa64.sys Tue Apr 24 13:26:29 2012 (4F96E245)
RTKVHD64.sys Tue Sep 7 07:17:23 2010 (4C861F43)
Rt64win7.sys Thu Apr 21 14:15:33 2011 (4DB07445)
Sftfslh.sys Tue Jun 25 17:08:39 2013 (51CA06D7)
Sftplaylh.sys Tue Jun 25 17:09:02 2013 (51CA06EE)
Sftredirlh.sys Tue Jun 25 17:08:55 2013 (51CA06E7)
Sftvollh.sys Tue Jun 25 17:08:23 2013 (51CA06C7)
VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
amd_sata.sys Fri Oct 12 05:48:36 2012 (5077E774)
amd_xata.sys Fri Oct 12 05:48:39 2012 (5077E777)
amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys Fri Nov 16 15:18:02 2012 (50A69F7A)
atikmpag.sys Fri Nov 16 14:39:13 2012 (50A69661)
avgfwd6a.sys Tue Sep 4 04:31:15 2012 (5045BC53)
avgidsdrivera.sys Fri Jul 19 19:33:34 2013 (51E9CCCE)
avgidsha.sys Fri Jul 19 19:33:32 2013 (51E9CCCC)
avgldx64.sys Fri Jul 19 19:33:11 2013 (51E9CCB7)
avgloga.sys Fri Jul 19 19:33:16 2013 (51E9CCBC)
avgmfx64.sys Sun Jun 30 19:28:29 2013 (51D0BF1D)
avgrkx64.sys Wed Sep 4 19:26:44 2013 (5227C1B4)
avgtdia.sys Wed Mar 20 21:50:47 2013 (514A6777)
avgtpx64.sys Tue May 28 10:57:10 2013 (51A4C5C6)
fxldapoc.sys Mon Mar 4 07:34:41 2013 (513494E1)
netr28x.sys Tue Nov 27 20:32:10 2012 (50B5699A)
usbfilter.sys Tue Dec 22 03:26:22 2009 (4B3082AE)
wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)






http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=AnyDVD.sys
http://www.carrona.org/drivers/driver.php?id=AtiPcie64.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
DDCDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=Sftfslh.sys
http://www.carrona.org/drivers/driver.php?id=Sftplaylh.sys
http://www.carrona.org/drivers/driver.php?id=Sftredirlh.sys
http://www.carrona.org/drivers/driver.php?id=Sftvollh.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=amdiox64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=avgfwd6a.sys
http://www.carrona.org/drivers/driver.php?id=avgidsdrivera.sys
http://www.carrona.org/drivers/driver.php?id=avgidsha.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=avgloga.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgtdia.sys
http://www.carrona.org/drivers/driver.php?id=avgtpx64.sys
http://www.carrona.org/drivers/driver.php?id=netr28x.sys
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
 
When I get home from work, I'll update wdcsam64.sys. I have two Western Digital external drives I use for backup, one mirroring the other. The 2nd drive was added along with the autobackup software about 2 months ago, so this makes sense. I'll start there, and if it does not help, I will address DDCDrv.sys.

Thanks so much for your response. With so many different named causes, I spent much of my time chasing my tail.
 
Hi. . .

Were both 2 GB RAM sticks in when you ran memtest86+ prior to problems you described in post #1? Or just 1 stick?

Is the RAM config (slots) now the same as it was prior to running memtest86+ ?

RAM config from your WMI report - https://www.sysnative.com/bsod2013/jcgriff2/RAM_info_dcjohnson50_09-17-2013.html

A BIOS update is available at HP Support -
Read More:

N-Alvorix-RS880 Motherboard BIOS Update - HP Pavilion p6710f Desktop PC | HP® Support

Your current BIOS -
Code: 
BIOS Date: [COLOR=#ff0000]09/07/10 [/COLOR]08:41:32 Ver: [COLOR=#ff0000]6.04[/COLOR]

OTHER ITEMS/ COMMENTS
1. Please uninstall Elby and any other virtual devices while BSOD thread is active -
Code: 
ElbyCDIO.sys      Mon Mar 04 04:21:51 2013 (513467AF)
http://sysnative.com/drivers/driver.php?id=ElbyCDIO.sys

2.Networking -- Both Realtek Ethernet and wifi (manufacturer is unknown at this time) are listed as active/ enabled in PERFMON -
Read More:


See "Network Interface" in PERFMON - https://www.sysnative.com/bsod2013/jcgriff2/dcjohnson50_09-17-201_perfmon.html.zip

Furthermore, both wifi & Ethernet drivers were named as "probable cause" in at least one BSOD -
Code: 
Rt64win7.sys      Thu [COLOR=#FF0000]Apr 21[/COLOR] 14:15:33 [COLOR=#FF0000]2011 [/COLOR](4DB07445) - Realtek Ethernet

netr28x.sys       Tue [COLOR=#FF0000]Nov 27[/COLOR] 20:32:10 [COLOR=#FF0000]2012 [/COLOR](50B5699A) - Wifi
netr28x.sys       Wed [COLOR=#FF0000]Jul 21 [/COLOR]07:39:22 [COLOR=#FF0000]2010 [/COLOR](4C46DC6A) - Wifi
There is no update available for Realtek from HP, so please try the update available directly from Realtek. Be sure to create a system restore point first.

http://sysnative.com/drivers/driver.php?id=netr28x.sys
http://sysnative.com/drivers/driver.php?id=Rt64win7.sys

Wifi driver netr28x.sys is listed 2x in the loaded driver summary (from BSOD dump logs) because it was updated after BSOD #7/ before the most recent BSOD #8 -
Code: 
8. Debug session time: Tue Sep 17 17:56:53.875 2013 (UTC - 4:00)
7. Debug session time: Mon Sep 16 20:58:49.779 2013 (UTC - 4:00)
6. Debug session time: Mon Sep 16 17:44:10.951 2013 (UTC - 4:00)
5. Debug session time: Mon Sep 16 17:26:57.554 2013 (UTC - 4:00)
4. Debug session time: Sun Sep 15 14:32:53.096 2013 (UTC - 4:00)
3. Debug session time: Sat Sep 14 15:12:56.632 2013 (UTC - 4:00)
2. Debug session time: Wed Sep 11 20:05:21.729 2013 (UTC - 4:00)
1. Debug session time: Wed Sep 11 19:50:45.028 2013 (UTC - 4:00)

I took special note of networking and did some additional digging in the Event Viewer logs and other system files because they go back >6 months -- meaning that IMHO, your system troubles began long before running memtest86+ a few days ago.

The BSOD file collection app dumps the last 50,000 records from the Application Log. 13,763 entries (27.5%/ 50k) are identical to this one & often occur every second:
Read More:


(13,763 *3) = 41,289 /50,000 (~ 83%) entries recorded since 6 March 2013 for Bonjour service alone. There are > 150 EVTX logs in Windows 7 (My Windows 8.1 installation lists 247 Event logs- c:\windows\system32\winevt\logs\*.evtx), so none of this may seem to matter. I certainly cannot say that Bonjour Service played a role in the BSODs at all, but it may be taxing system resources. PERFMON lists:
The average disk queue length is 1. The disk may be at its maximum transfer capacity due to throughput and disk seeks
Click to expand...
https://www.sysnative.com/bsod2013/jcgriff2/dcjohnson50_09-17-201_perfmon.html.zip

I myself don't have iTunes, but my kids do and I see first-hand how Apple taxes Windows system resources unnecessarily by keeping various apps like synching running 24/7. You may want to change the service setting(s) to "manual" v. "start-up" with an app like SysInternals AutoRuns, available free from Microsoft TechNet -

http://technet.microsoft.com/en-us/sysinternals/bb963902

I found about 80 0xc0000005 exception codes among the Event Viewer log entries. .

0xc0000005 excp code = "memory access violation". 0xc5 can be caused by hardware failure such as RAM itself or other unknown hardware failure affecting RAMs ability to properly hold kernel code. On the software side, 0xc5 may be the result of a rogue driver attempting to access memory that is off limits to it; also - it could be "access denied", which I usually see when 3rd party firewalls are installed.

0xc0000005 exceptions began appearing on 26 March 2013, which is as far back as the log dumps go back. >99% involve #1 app crashing:
1. kdbsync.exe
2. googledrivesync.exe
3. DivXUpdate.exe

Here is the actual crash info from WERCON (Event Viewer in this case as WERCON (msinfo32) was not included in the attached zip. I suspect that you received a "waiting for XYZ to complete" message when running the jcgriff2 BSOD File Collection app sand killed the app off before completion. Not a big deal -- I do it myself when I don't feel like waiting for it to complete! :0
Code: 
Event[12523]:
  Source: Application Error
  Date: 2013-03-06T17:53:46.000
  Task: Application Crashing Events
  Level: Error
  Description: 
Faulting application name: [COLOR="#FF0000"][/COLOR][COLOR="#FF0000"]kdbsync.exe[/COLOR], version: 0.0.0.0, time stamp: 0x4f67a718
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
[COLOR="#FF0000"]Exception code: 0xc0000005[/COLOR]
Fault offset: 0x00000000
Faulting process id: 0xc50
Faulting application start time: 0x01ce1ac5c05fd9d7
Faulting application path: [COLOR="#FF0000"]C:\Program Files (x86)\AMD AVT\bin\kdbsync.exe[/COLOR]
Faulting module path: unknown
Report Id: 154b7bef-86b9-11e2-8abd-c9e9189aa506

I started to look at HDD info; for now, I'm just listing this here for future reference as chkdsk, SeaTools should be run on each drive:
Read More:

Apologies, but I need to stop here as I have gone through so many files and so much info over the last few hours that I need to 'digest it' so as not to further confuse myself! :0

Also -- just to note. . . there seems to be an issue with video. I noticed that DirectX diag reported:
Code: 
  DxDiag Previously: Crashed in Direct3D (stage 2). 
Re-running DxDiag with "dontskip" command line parameter or choosing 
not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information

Video was indicated as a possible probable cause in more than one dump.

kdbsync.exe is located in C:\Program Files (x86)\AMD AVT\bin\kdbsync.exe -- so it is related to ATI video.

Google search - https://www.google.com/search?num=100&newwindow=1&safe=off&site=&source=hp&q=kdbsync.exe&oq=kdbsync.exe&gs_l=hp.3..0l10.242.242.0.699.1.1.0.0.0.0.131.131.0j1.1.0....0...1c.1.26.hp..0.1.130.6q7hB6X-sPo

I hope that some of the above helps -- and makes sense to someone! I'll have to re-read it later today after my mind 'resets'. :0

Kind Regards. . .

jcgriff2

`



BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091713-58375-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Tue Sep 17 17:56:53.875 2013 (UTC - 4:00)
System Uptime: 0 days 0:12:01.093
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+9f )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!IoRemoveIoCompletion+9f
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`037c72bf fffff880`0bcda0b0 00000000`00000000
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091613-50825-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 16 20:58:49.779 2013 (UTC - 4:00)
System Uptime: 0 days 0:29:46.044
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0014376e 00000000`00000002 00000000`001fcd8d
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091613-53898-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 16 17:44:10.951 2013 (UTC - 4:00)
System Uptime: 0 days 0:13:46.590
BugCheck D1, {5b, 2, 0, fffff88000eb5187}
Probably caused by : Wdf01000.sys ( Wdf01000!FxRequestFromLookaside::SelfDestruct+f )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_Wdf01000!FxRequestFromLookaside::SelfDestruct+f
Bugcheck code 000000D1
Arguments 00000000`0000005b 00000000`00000002 00000000`00000000 fffff880`00eb5187
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091613-54381-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 16 17:26:57.554 2013 (UTC - 4:00)
System Uptime: 0 days 19:48:48.193
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  DVD Shrink 3.2
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`00000002 00000000`00000001 fffff800`034f9642
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091513-54522-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 15 14:32:53.096 2013 (UTC - 4:00)
System Uptime: 0 days 23:18:43.735
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_netr28x.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0cd4fa10 fffff800`00ba2748 fffffa80`0d0ebe10
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091413-59030-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sat Sep 14 15:12:56.632 2013 (UTC - 4:00)
System Uptime: 2 days 18:20:41.896
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_Rt64win7.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0d13fa10 fffff800`00b9c518 fffffa80`12a2a3a0
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091113-56815-01.dmp]
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Wed Sep 11 20:05:21.729 2013 (UTC - 4:00)
System Uptime: 0 days 0:13:14.116
Probably caused by : win32k.sys ( win32k!TimersProc+73 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+73
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`00154d7f fffff880`021fc0c0 00000000`00000000
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\091113-119200-01.dmp]
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Wed Sep 11 19:50:45.028 2013 (UTC - 4:00)
System Uptime: 8 days 7:29:58.666
Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+60 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiIpiProcessRequests+60
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`0000000e 00000000`00000000 fffff800`034e29b0
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6710f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 
Last edited:
Hi jcgriff2, thank you for the lengthy examination. Lots to digest here and may require multiple revisits to address all the issues.

When I ran memtest86 and it went away, I was running with the 2-8gb sticks. After memtest86, I reset the CMOS because it would not boot. Then I swapped in the memory that originally came with the computer, 2-2gb sticks. The last few BSOD reports came after the memory was swapped.

I'll attempt a BIOS update, but may want to address the other issues first.

1. I'll uninstall Elby until this is resolved.

2. I'll check with Realtek for updated drivers. I will say, I've had connection issues in the past 7-8 months. Oftentimes, the connection will go away and I will go through the Networking Troubleshooting section to regain my connection. It will claim to have "Reset the Adapter". It will plague me for a few weeks making the computer a large unconnected paperweight, and then will magically connect flawlessly every day for a month.

I'll address kdbsync.exe as well. I treated it as innocuous for the longest, a minor annoyance, but have attempted to fix it in the past without success. Obviously is a problem.

I'll also address googledrivesync.exe and DivXUpdate.exe.

Another thing that's been troublesome is a process that spikes CPU usage, PresentationFontCache.exe. Not sure if that would cause any of the problems but it's been a frequent annoyance.
 
My main question about the networking -- which do you actually use?

i.e., Ethernet or wifi? If using Ethernet, wifi should be turned off & vice-versa.

PERFMON showed activity by both wifi & Ethernet; not sure what the duration for the PERFMON run was though. I myself switch between the 2 w/o rebooting, so that may be the case for you too. I mean -- one must be primary...? Unless an app can actually be written to use one or the other. I noticed you had SQL installed.

The Realtek driver may not be an issue at all; too difficult to tell at this time because of all of the other networking activity. You've got quite a few apps that "phone home" constantly; others that run a similar type of "updater app" that continuously phone home as well throughout the day doing nothing more than waiting to be told/ receive reply that an update is available.

In general, these type of apps are a waste -- literally -- as they tie up your Internet and can interfere with each other & you (your apps) as well. For example, there really is no need for Adobe, java, Divx, Google, TeamViewer, etc... (I know that you don't have all of those apps), to check every 15, 30, 45, 60..... minutes for updates. I suggest using SysInternals AutoRuns and un-check the boxes of unnecessary items. Doing so under the "Logon" tab disables them from start-up during boot. You can run *whatever* by 2x-click.

http://live.sysinternals.com/autoruns.exe

^^^ -- after the registry scan is complete (status - bottom-left of A/Runs screen), you can click on "user" and select another user account and check their settings.

Please be sure to create a system restore point first -- just in case!

How did you determine that PresentationFontCache.exe spikes? i.e., what app did you use?

I would suggest trying Resmon if you have not already done so.
START | resmon

Also, PERFMON is really good at capturing info that may otherwise go unnoticed. You can run perfmon /report at any time. Check the disk areas -- like which files have the highest I/O - frequency and bytes.

I would also give thought to removing AVG with removal tool - Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Reboot upon completion. Install MSE - Microsoft Security Essentials - Microsoft Windows

Or try my favorite - ESET -
- ESS has a firewall + NOD32 a/v
- NOD32 is a/v; uses Windows Firewall

I am a beta tester for ESET and although it is not a free product, you may want to give it a try in light of problems AVG has had in recent months.

I currently run both versions of ESET -- version 7 -- beta -

v7 BETA | Smart Security 7 BETA | NOD32 Antivirus 7 BETA

There is no way around the one BSOD in particular that had me fixated for quite a while -- trying to make sense of it all.

The BSOD with bugcheck 0x4e (0x99,,,) -
Code: 
PROCESS_NAME:  [COLOR=#0000ff]avgnsa.exe[/COLOR]
FAILURE_BUCKET_ID:  X64_0x4E_99_nt![COLOR=#ff0000]Mi[/COLOR]BadShareCount+4c
Process = AVG
In my world (I am not a C++ coder as many others here are) -- Mi - indicates to me that RAM is involved -- whether directly itself or other hardware failure is affecting RAM in a negative manner

However, please keep in mind that if in fact hardware failure is the cause here, it is that same failing hardware that is producing the BSOD kernel memory dumps; hence one reason that BSOD dumps are incapable of telling us the exact piece of hardware that is failing/ has failed. The best that dumps can do is point us in a direction --- and even that can be misleading.

Sometimes not, though. For example, if the bugcheck includes an exception code like 0xc185 -- I/O error, it is of course prudent to run HDD diags. Unfortunately, there is nothing like that here.

The one thing we do have here are varying bugcheks, which usually indicates unknown hardware failure.

Here are 3 different levels of bugcheck summaries for your 8 BSODs that occurred over a 6 day period -
Read More:


Your system uptimes are all over the map - ranging from 13 minutes to 23+ hours before the system BSOD'd -
Code: 
[FONT=lucida console]
System Uptime: 0 days 0:12:01.093
System Uptime: 0 days 0:29:46.044
System Uptime: 0 days 0:13:46.590
System Uptime: 0 days 19:48:48.193
System Uptime: 0 days 23:18:43.735
System Uptime: 2 days 18:20:41.896
System Uptime: 0 days 0:13:14.116
System Uptime: 8 days 7:29:58.666
[/FONT]

Regards. . .

John
 
Thanks for all the info, John. Went home for lunch and was able to update the network card's driver with a newer version via Realtek's website, Windows claimed it was using the latest. Was working on the Western Digital driver updates when I had to return to work. I checked the date on my copy of wdcsam64.sys and it showed a 2011 date, not the 2008 trouble date. Still, will attempt to update this evening. I'll also run a diag on the two WD external drives.

Wi-Fi and Ethernet, hmmmm. The box is hardwired and I wasn't aware that it was connecting to the Wi-Fi connection as well. I'll resolve that as well.

Up until a 2 weeks ago, I had McAfee Internet Suite installed, first BSOD's happened with it. Uninstalled, appeared stable, but, I did not stress system at all. Rarely used in fact. Installed AVG's Internet Suite and the BSOD's returned. I've had more problems over the years with virus software than anything else. I'll give MSE a shot. Any downside to it?

The PresentationFontCache.exe CPU spikes were easy to notice. What alerted me to something amiss was the fans going from essentially idle to full blast, up and down. Does it quite often. Viewed Process list and found it was bouncing between 25% all the way to 100% at times. I kill it, and it will eventually come back. Have read several articles about it, but, it's a minor annoyance. Just wondered if it was part of a bigger problem.

Truth be known, I'm a software developer, C++/Java, but have been away from Windows development for 3-4 years. Linux these days. When I get home after sitting behind one all day, I just want it to work so I can edit photos, surf, check email and the like. :-) But I do know memory bugs are the worst, and quite often the hardest to isolate.

I'll report more this evening. AVG will be the 1st thing on the list.
 
BIOS updated.


kdbsync.exe error fixed.


Uninstalled AVG.


Updated firmware for WD harddrive.

Used autorun to turn off a few startup items causing problems.


Uninstalled lots of old software.


Uninstalled Elby, DivX.


Disabled Wi-Fi since I am using Ethernet.


About to install MSE since I am virus protectionless. At some point, after a few days of this setup, I'll swap the memory again since it was not the problem.


Crossing fingers that these changes have the problem licked.
 
Decided to run the BSOD app. It got to the autorun portion of the test before it blue screened. WhoCrashed displayed this information:

[FONT=Segoe UI, Arial]On Thu 9/19/2013 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-42572-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (0xFFFFF88004BAE0E4)
Bugcheck code: 0x50 (0xFFFFF80004BAE0C7, 0x1, 0xFFFFF88004BAE0E4, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\atikmdag.sys
product: [FONT=Segoe UI, Arial]ATI Radeon Family[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. PAGE_FAULT_IN_NONPAGED_AREA

Off to see if an updated driver set is available for my video card. I knew it was too good to be true. :-)
[/FONT]
[/FONT]
 
Opened Adobe Lightroom, imported some photos, scrolled through photos and then the screen went black. Then just a super fast paced pulsed beeping until I powered down. No BSOD, no dump file, etc... Geee, think I am done for the night.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top