Morning Guy's
there is something odd in that system and comparing the three dumps beside other information provided,
showed pretty differences.
the dump mentioned by xer with memory corruption shows
Code:
Built by: 10586.[COLOR=#ff0000]212[/COLOR].amd64fre.th2_release_sec.160328-1908
Seems Fast Ring win10 Track, right? :smile9:
That Dump 041716-7953-01.dmp also told us this:
Code:
CHKIMG_EXTENSION: !chkimg -lo 50 -d !pci
fffff80016df4c30-fffff80016df4c3a 11 bytes - pci!PciBus_QueryDeviceRelations
[ 40 57 41 56 48 83 ec 68:21 50 a0 5c 4d 00 00 00 ]
fffff80016df4c3c-fffff80016df4c45 10 bytes - pci!PciBus_QueryDeviceRelations+c (+0x0c)
[ 49 8b f8 4c 8b f1 0f 85:53 00 00 00 00 00 00 00 ]
fffff80016df4c48-fffff80016df4c5c 21 bytes - pci!PciBus_QueryDeviceRelations+18 (+0x0c)
[ ba 04 00 00 00 48 89 74:81 0c fe 16 71 02 00 00 ]
fffff80016df4c5f-fffff80016df4c6d 15 bytes - pci!PciBus_QueryDeviceRelations+2f (+0x17)
[ 48 8b cf e8 c1 0d fd ff:00 03 00 00 00 00 00 00 ]
fffff80016df4c6f-fffff80016df4c75 7 bytes - pci!PciBus_QueryDeviceRelations+3f (+0x10)
[ 48 85 c0 0f 85 65 db:00 a9 0c fe 16 71 02 ]
fffff80016df4c78-fffff80016df4c86 15 bytes - pci!PciBus_QueryDeviceRelations+48 (+0x09)
[ 8b 47 04 4c 89 6c 24 48:d9 51 bb f9 54 00 00 00 ]
fffff80016df4c88-fffff80016df4ca4 29 bytes - pci!PciBus_QueryDeviceRelations+58 (+0x10)
[ 00 48 89 6c 24 60 8d 50:03 00 00 00 53 00 00 00 ]
fffff80016df4ca7-fffff80016df4cae 8 bytes - pci!PciBus_QueryDeviceRelations+77 (+0x1f)
[ 45 33 c9 48 89 9c 24 80:00 21 50 a0 5c 4d 00 00 ]
fffff80016df4cb0 - pci!PciBus_QueryDeviceRelations+80 (+0x09)
[ 00:03 ]
fffff80016df4cb2-fffff80016df4cb9 8 bytes - pci!PciBus_QueryDeviceRelations+82 (+0x02)
[ 45 33 c0 48 c7 44 24 20:00 00 00 00 00 00 00 00 ]
fffff80016df4cbc-fffff80016df4cc5 10 bytes - pci!PciBus_QueryDeviceRelations+8c (+0x0a)
[ 00 00 33 d2 48 8d 8f 90:77 0c 00 00 f9 0c fe 16 ]
fffff80016df4cc7-fffff80016df4ce5 31 bytes - pci!PciBus_QueryDeviceRelations+97 (+0x0b)
[ ff 15 73 38 ff ff 48 8d:00 69 9a ad b7 ee 00 00 ]
fffff80016df4ce7-fffff80016df4cfe 24 bytes - pci!PciBus_QueryDeviceRelations+b7 (+0x20)
[ 33 d2 8b f0 ff 15 47 38:00 21 0d fe 16 71 02 00 ]
fffff80016df4d00-fffff80016df4d1c 29 bytes - pci!PciBus_QueryDeviceRelations+d0 (+0x19)
[ 00 48 8b 05 f8 d2 fe ff:03 00 00 00 00 00 00 00 ]
fffff80016df4d1e-fffff80016df4d28 11 bytes - pci!PciBus_QueryDeviceRelations+ee (+0x1e)
[ 0f 85 3e db 00 00 44 8b:00 00 21 50 a0 5c 4d 00 ]
fffff80016df4d2c-fffff80016df4d2f 4 bytes - pci!PciBus_QueryDeviceRelations+fc (+0x0e)
[ 48 85 ed 0f:ee 00 00 00 ]
234 errors : !pci (fffff80016df4c30-fffff80016df4d2f)
MODULE_NAME: memory_corruption
My guess, happened during swapping / paging into memory and an unknown Filterdriver may be responsible for this.
while the corresponding Eventlog says problems with the
Code:
Event[17]:
Log Name: System
Source: [COLOR=#ff0000]Service Control Manager[/COLOR]
Date: 2016-04-18T18:29:13.696
Event ID: 7023
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer:{whiped out}
Description:
The User Data Access_4a47a service terminated with the following error:
[COLOR=#ff0000]Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk[/COLOR].
each time the DB is opened, not a normal feature.
What is loaded into the System differs heavily depending on your started applications, it is just a snappshot from one CPU-Kernel, you have 8 of them
going with intels latest Generation
Intel(R) Core(TM) i7-6700HQ and Chipset. :cool3:
As you also have Logitech Setpoint running on your System with the fameous
KHALMNPR.exe (hooking on ntdll and others) including several DLL's which is worth for troubles since XP, i really fear for stability, get rid of or update to the latest Version.
Your latest Dump shows Built by:
10586.0.amd64fre.th2_release.151029-1700
what is going on here?
personaly i would likely see / have an full Kerneldump (memory.dmp) to see whats going on in the machine.
Several Networkingproblems are also present in your machine (not responsible for the BSOD) like that below, the cause may be
KillerService.exe brought to you by Qualcomm
Code:
Event[13]:
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 2016-04-18T18:31:23.096
Event ID: 8020
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-20
User Name: NT AUTHORITY\NETWORK SERVICE
Computer: {whiped}
Description:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:
Adapter Name : {721082FE-9F93-4AC3-986C-2095FF0ECA28}
Host Name : {whiped}
Primary Domain Suffix : mit.edu
DNS server list :
209.18.47.61, 209.18.47.62
Sent update to server : <?>
IP Address(es) :
2604:2000:80cb:2100:713d:53e0:fbd5:44ca, 192.168.0.14
The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
regards
Michael
