Windows 10: dm_log_collector - NO FILE!

I've attached a new zip file (as before, I had to zip it manually before the second prompt removed the folder). I kept the machine off all night to avoid the constant bsod reboots.

 

I would like to see a kernel dump, which is located in C:\Windows and called MEMORY.dmp, to have a look at a few things. I'm fairly sure it is a driver causing issues, but it is quite interesting to see the memory that was referenced is everytime the same.

I do have a suggestion for you currently, although I do not know what driver is causing the issues, your memory is not seated properly.
Your memory is currently seated in Channel A & B (or slot 4,2 or 3,1) while it should be Channel A OR B (or slot 4, 3 or 2, 1), in other words the same coloured slots is how the memory should be seated.
Attachment 93188
Code: Bugcheck code 0000000A Arguments 00000000`00006000 00000000`00000002 00000000`00000000 fffff800`2f100258 Debug session time: Sun Jul 31 00:52:41.645 2016 (UTC + 2:00) System Uptime: 0 days 0:11:25.350 1: kd> !pte 00000000`00006000 VA 0000000000006000 PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000000 PTE at FFFFF68000000030 contains 04800001EF830867 contains 0000000000000000 pfn 1ef830 ---DA--UWEV not valid 1: kd> !irp ffffffffffffff88 1 ffffffffffffff88: Could not read Irp 1: kd> .trap 0xffffd00020f4be70 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000006000 rbx=0000000000000000 rcx=0000000000006000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8002f100258 rsp=ffffd00020f4c000 rbp=ffffd00020f4c140 r8=0000000000000002 r9=00000000000007ff r10=ffffd001e6435ca0 r11=ffffe0010feb59e0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!IopCompleteRequest+0xdf8: fffff800`2f100258 488b09 mov rcx,qword ptr [rcx] ds:00000000`00006000=???????????????? [Memory Device (Type 17) - Length 34 - Handle 0040h] Physical Memory Array Handle 0007h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelB-DIMM1 Bank Locator BANK 3 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 8502 Serial Number Asset Tag Number Part Number PSD34G13332 [Memory Device (Type 17) - Length 34 - Handle 0042h] Physical Memory Array Handle 0007h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelA-DIMM1 Bank Locator BANK 1 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 8502 Serial Number Asset Tag Number Part Number PSD34G13332 [Memory Device (Type 17) - Length 34 - Handle 0045h] Physical Memory Array Handle 0007h Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 0 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator ChannelB-DIMM0 Bank Locator BANK 2 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer [Empty] Serial Number Asset Tag Number Part Number [Empty] [Memory Device (Type 17) - Length 34 - Handle 0046h] Physical Memory Array Handle 0007h Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 0 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator ChannelA-DIMM0 Bank Locator BANK 0 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer [Empty] Serial Number Asset Tag Number Part Number [Empty][/quote]

Note Upload a kernel dump to a 3rd party uploader like onedrive, google drive, dropbox, or similar onces and post a share link in your next reply

 

Good catch! Can't remember the last time I put in the memory. Anyway, I have reinstalled it correctly.

Subsequent changes: probably nothing looking to do with my problem, but looking through the event log I have disabled ReadyBoot (have an SSD) and remove XPS Printer (never needed.)

Also reconfigured settings to allow Windows to manage paging and set it to a full memory.dmp. Will upload that plus a new debug zip file when it BSODs again (unless for some miracle the correct installation of the dimms did the trick.)

Thanks axe0!

 

PS - windbg says

Memory manager detected 63884 instance(s) of page corruption, target is likely to have memory corruption.

So another fingers crossed that crash was due to the improper memory installation. Is Win 10 more sensitive to this?

 

You could say it is sensitive when there is dust on a stick or in the slot, or when the stick is not properly seated, etc.

 

Crashed again. I have uploaded a full memory.dmp (zipped up) to OneDrive (wow, is the upload speed SLOW!)

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Just got some Windows update notifications; one is for the Intel HD Graphics so we'll see if a video driver was messing things up. (Doesn't hurt to hope!)

Thanks.

(PS just noticed that OneDrive links have an advert as the text. Couldn't find the HTML edit option to change.)

 

Please note, the kernel dump request was only for once *Smile

I cannot do much unfortunately, I'm not sure why though. Either there isn't much saved of what I wanted to look at or there is something going on of what I do not know much about if I know anything about it at all.

Please run below test





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Thanks. Per my earlier post, when I originally did the Driver Integrity thing I got a KMODE_EXCEPTION_NOT_HANDLED error, a reboot, another of the same error, a reboot, a "Windows couldn't load correctly" and then a Restore to Previous version.

 

Does it restore automatically or do you choose to restore?

 

Well when I tried it, I neglected to do a restore point and thus didn't get a choice.

I'll try it again and see what happens. But will pay attention and create another restore point first.

 

Please try to disable driver verifier first, a system restore is more like a plan B *Smile

 

Same thing as per my previous attempt.

kmode_exception_not_handled

And this time I turned verifier off, once at the command line, the other in the gui. To no avail. Windows couldn't load correctly. Had to revert to my restore point.

 

So what I'm trying now, fire up autoruns, start disabling non-MS drivers. Wait.

 

BSOD.
Uninstalled avast.
BSOD.
More drivers and startups to disable...

 

All non-MS device drivers have been turned off, except for Intel & Gigabyte (motherboard) ones.
BSOD.
Turned off every autorun prog except for .
BSOD.
Turned off all remaining services & drivers (except, again, Intel & Gigabyte).
BSOD.

Can't think of anything else to disable at this point.