The Windows 10 April 2018 update has arrived! Get the new Dell XPS 15, starting at $999.99
08-17-2016 11:03 AM
150 ... 3456
tools
  1. Aaargh Zombies's Avatar
    So many post here, I did not read them all. But this is a fairly common issue. Put all your memory in, download memtest MemTest86 - Offical Site of the x86 Memory Testing Tool and create a bootdisk of boot flashdrive for it, and run it, and test the memory. You will find out you have a bad memory stick, and can stop doing all kinds of crazy things to fix it and move on with your life.
    I did that before starting the thread.

    I tried once with each of the memory modules in place, and twice with them both in place. I ran for the recommended amount of time and came up empty.

    It couldn't find any errors.

    The fact that this only happens on a boot from power down, after a clean shut down, suggest that this isn't a memory problem. It has never done it on a reboot, or from a shut down that was dirty.
    07-01-2016 02:10 AM
  2. Aaargh Zombies's Avatar
    Ok, I just read what you have.. Two single 8GB modules. Which I assume are not identical. That makes life more interesting.

    Memory is normally used in pairs to utilize dual channel modes (more performance), but for that it is critical that the pairs are identical.

    Looking at your motherboard manual, I suggest you should not try and use the memory in a manner that tries to enable dual channel mode. So don't have modules in ddr3_2/ddr3_1 or ddr3_4/ddr3_2. Try the modules in say ddr3_3/ddr3_2 or ddr3_4/ddr3_1.

    Saying that, it may not work as 16gb in single channel mode.

    General rule is always buy pairs of memory at the same time.
    Both modules are identical, they are the original modules that were supplied with the computer from new.
    07-01-2016 02:11 AM
  3. Aaargh Zombies's Avatar
    I've ruled out the soundcard as being the cause.

    I had the normal Memory_Management error when I booted this morning.

    The stupid thing is that this almost never happens during the day. I shut my computer down cleanly and switched it off at the mains a dozen times yesterday while I was checking things suggested on this forum, and there were absolutely no problems. Then it BSOD the first time that I switched it on this morning.

    It's almost as if the computer will only BSOD if it's been shut down for a couple of hours or more.

    Could it be something as simple as a service or software package detecting that it hasn't been run in X hours, and checking online for updates?
    07-01-2016 02:15 AM
  4. Aaargh Zombies's Avatar
    I've switched on Boot logging.

    Here is the latest record from when it last BSOD

    BOOTLOG_LOADED \SystemRoot\system32\ntoskrnl.exe
    BOOTLOG_LOADED \SystemRoot\system32\hal.dll
    BOOTLOG_LOADED \SystemRoot\system32\kd.dll
    BOOTLOG_LOADED \SystemRoot\system32\mcupdate_GenuineIntel.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\werkernel.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\CLFS.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tm.sys
    BOOTLOG_LOADED \SystemRoot\system32\PSHED.dll
    BOOTLOG_LOADED \SystemRoot\system32\BOOTVID.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\cmimcext.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ntosext.sys
    BOOTLOG_LOADED \SystemRoot\system32\CI.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\msrpc.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\FLTMGR.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ksecdd.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\clipsp.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\Wdf01000.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WDFLDR.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\acpiex.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\WppRecorder.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\cng.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ACPI.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WMILIB.SYS
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WindowsTrustedRT.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WindowsTrustedRTProxy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pcw.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\msisadrv.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pci.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vdrvroot.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\pdc.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\CEA.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\partmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\spaceport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgrx.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mountmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\iaStorA.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\storport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\EhStorClass.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\fileinfo.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Wof.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\PxHlpa64.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\NTFS.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Fs_Rec.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ndis.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\NETIO.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\ksecpkg.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tcpip.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\fwpkclnt.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\wfplwfs.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\fvevol.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volsnap.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rdyboost.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\mup.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\hwpolicy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\disk.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\CLASSPNP.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\cdrom.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\filecrypt.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Null.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Beep.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\BasicDisplay.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\BasicRender.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Npfs.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Msfs.SYS
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\tdx.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\netbt.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\afd.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vwififlt.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pacer.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\netbios.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avkmgr.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avipbb.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\rdbss.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nsiproxy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\npsvctrig.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mssmbios.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\gpuenergydrv.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\dfsc.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ahcache.sys
    BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\compositebus.inf_amd64_912dfdedc3d2f520\CompositeBus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kdnic.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\umbus.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\HDAudBus.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ucx01000.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\USBXHCI.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\TeeDriverW8x64.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbehci.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rt640x64.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\serial.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\serenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\parport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\intelppm.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nvvad64v.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ksthunk.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\busenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\NdisVirtualBus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\swenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vmulti.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mshidkmdf.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rdpbus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbhub.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mouhid.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mouclass.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nvhda64v.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\UsbHub3.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbccgp.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\hidusb.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdhid.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdclass.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\monitor.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    7 1 2016 06:40:07.495
    BOOTLOG_LOADED \SystemRoot\system32\ntoskrnl.exe
    BOOTLOG_LOADED \SystemRoot\system32\hal.dll
    BOOTLOG_LOADED \SystemRoot\system32\kd.dll
    BOOTLOG_LOADED \SystemRoot\system32\mcupdate_GenuineIntel.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\werkernel.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\CLFS.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tm.sys
    BOOTLOG_LOADED \SystemRoot\system32\PSHED.dll
    BOOTLOG_LOADED \SystemRoot\system32\BOOTVID.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\cmimcext.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ntosext.sys
    BOOTLOG_LOADED \SystemRoot\system32\CI.dll
    BOOTLOG_LOADED \SystemRoot\System32\drivers\msrpc.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\FLTMGR.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ksecdd.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\clipsp.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\Wdf01000.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WDFLDR.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\acpiex.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\WppRecorder.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\cng.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\ACPI.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WMILIB.SYS
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WindowsTrustedRT.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WindowsTrustedRTProxy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pcw.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\msisadrv.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pci.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vdrvroot.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\pdc.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\CEA.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\partmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\spaceport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgrx.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mountmgr.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\iaStorA.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\storport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\EhStorClass.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\fileinfo.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Wof.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\PxHlpa64.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\NTFS.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Fs_Rec.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ndis.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\NETIO.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\ksecpkg.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tcpip.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\fwpkclnt.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\wfplwfs.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\fvevol.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\volsnap.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rdyboost.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\mup.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\hwpolicy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\disk.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\CLASSPNP.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\cdrom.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\filecrypt.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Null.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Beep.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\BasicDisplay.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\BasicRender.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Npfs.SYS
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\Msfs.SYS
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\tdx.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\netbt.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\afd.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vwififlt.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\pacer.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\netbios.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avkmgr.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avipbb.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\rdbss.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nsiproxy.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\npsvctrig.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mssmbios.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\gpuenergydrv.sys
    BOOTLOG_LOADED \SystemRoot\System32\Drivers\dfsc.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ahcache.sys
    BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\compositebus.inf_amd64_912dfdedc3d2f520\CompositeBus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kdnic.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\umbus.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\HDAudBus.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ucx01000.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\USBXHCI.SYS
    BOOTLOG_LOADED \SystemRoot\System32\drivers\TeeDriverW8x64.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbehci.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rt640x64.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\serial.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\serenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\parport.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\intelppm.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nvvad64v.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\ksthunk.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\busenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\NdisVirtualBus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\swenum.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\vmulti.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mshidkmdf.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\rdpbus.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbhub.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mouhid.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mouclass.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\nvhda64v.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\UsbHub3.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\usbccgp.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\hidusb.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdhid.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdclass.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\monitor.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\luafv.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\storqosflt.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avgntflt.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\lltdio.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\mslldp.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\rspndr.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\HTTP.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WudfPf.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\bowser.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\mrxsmb.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\mrxsmb20.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\mpsdrv.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\avnetflt.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\Ndu.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srvnet.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\mrxsmb10.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\mmcss.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tcpipreg.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\peauth.sys
    BOOTLOG_LOADED \SystemRoot\system32\drivers\WinisoCDBus.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srv2.sys
    BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srv.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\tunnel.sys
    BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\avgntflt.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\condrv.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WSDPrint.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\WSDScan.sys
    BOOTLOG_LOADED \SystemRoot\System32\drivers\WSDPrint.sys
    BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\WSDScan.sys

    This is my anti-virus I did a clean install some months ago and deliberately didn't install it. The PC ran perfectly all day but BSOD when I switched it on the next morning exactly like it is doing now, even without the anti-virus installed, so we can rule this out as being an issue.

    BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\avgntflt.sys

    This seems to come up several times.

    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    Last edited by Aaargh Zombies; 07-05-2016 at 02:12 AM.
    07-01-2016 02:28 AM
  5. Aaargh Zombies's Avatar
    I've run WinDbg, and have found the following in the Memory.dmp

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: SearchIndexer.

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DARKNESS

    ANALYSIS_SESSION_TIME: 07-01-2016 09:29:41.0798

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre


    I also found this in the MiniDump file. It says "SanDiskSSDDash", which is the SSD that I did the clean install on. I previously had the exact same error on a regular disc that I did an upgrade from Windows 7 on. So it's unlikely that the driver for this specific disc is the problem, but maybe it's a clue to the real issue.

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: SanDiskSSDDash

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: DARKNESS

    ANALYSIS_SESSION_TIME: 07-01-2016 09:28:54.0524

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    LAST_CONTROL_TRANSFER: from fffff800579f338b to fffff800579c37a0

    STACK_TEXT:
    ffffd000`2126c708 fffff800`579f338b : 00000000`0000001a 00000000`00005200 ffffe001`897b7000 af3cb48e`fbbb4690 : nt!KeBugCheckEx
    ffffd000`2126c710 fffff800`57ab1e28 : ffffe001`897b8590 ffffd000`2126c7c0 00000000`66626353 fffff800`57b96cc0 : nt! ?? ::FNODOBFM::`string'+0x2118b
    ffffd000`2126c750 fffff800`57c844ff : 00000000`0000001a 00000000`00001000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x4c8
    ffffd000`2126c830 fffff800`57cb5d48 : 00000000`00000020 ffffe001`897b8590 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x63f
    ffffd000`2126c950 fffff800`57cb5820 : 00000000`03dae698 00000000`00000000 00000000`03daeef0 00000000`03dae638 : nt!IopCreateFile+0x3d8
    ffffd000`2126ca00 fffff800`579ce0a3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x58
    ffffd000`2126ca90 00007ff9`83e85744 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03dae5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`83e85744


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 583d16091444eb751da7fcff192b9c16cdb45ff4

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a86dfa57b714cbf260f89d009031780f3d52649e

    THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+2118b
    fffff800`579f338b cc int 3

    FAULT_INSTR_CODE: e9c033cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2118b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5749178b

    IMAGE_VERSION: 10.0.10586.420

    BUCKET_ID_FUNC_OFFSET: 2118b

    FAILURE_BUCKET_ID: 0x1a_5200_nt!_??_::FNODOBFM::_string_

    BUCKET_ID: 0x1a_5200_nt!_??_::FNODOBFM::_string_

    PRIMARY_PROBLEM_CLASS: 0x1a_5200_nt!_??_::FNODOBFM::_string_

    TARGET_TIME: 2016-06-23T06:57:56.000Z

    OSBUILD: 10586

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-05-28 04:59:07

    BUILDDATESTAMP_STR: 160527-1834

    BUILDLAB_STR: th2_release_sec

    BUILDOSVER_STR: 10.0.10586.420.amd64fre.th2_release_sec.160527-1834

    ANALYSIS_SESSION_ELAPSED_TIME: 320

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1a_5200_nt!_??_::fnodobfm::_string_

    FAILURE_ID_HASH: {1e854523-2333-b9e7-8239-75ad626b9127}

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


    TRAP_FRAME: ffffd00183db0530 -- (.trap 0xffffd00183db0530)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000800000000000 rbx=0000000000000000 rcx=8000000000000000
    rdx=0000007ffffffff8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8004811b340 rsp=ffffd00183db06c0 rbp=ffff000000000000
    r8=ffffe0006d8c9a40 r9=0000098000000000 r10=0000000fffffffff
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po cy
    nt!MiCaptureAndResetWorkingSetAccessBits+0x130:
    fffff800`4811b340 488b1f mov rbx,qword ptr [rdi] ds:00000000`00000000=????????????????
    Resetting default scope
    07-01-2016 03:34 AM
  6. Aaargh Zombies's Avatar
    I ran Driver Verifier, and selected only Microsoft services, and rebooted.

    It gave me the following dump file
    Attached Files
    07-01-2016 04:55 AM
  7. slooksterpsv's Avatar
    See if there is a firmware update for the Sandisk, it could be a bad firmware version. i would also check your BIOS and see what your drive settings are set to. You would want AHCI (this may require a reinstall) and not IDE. In addition, I would uninstall Avira - according to the driver that didn't load it may be Avira's antivirus service. From the stack trace in the previous post (not 106), it shows that a file was opened and a bug check tried to occur when it crashed. It makes me think overall, something is up with either the drive configuration, the drive firmware, or there's an issue with the motherboard and how it interfaces with the drives.
    07-01-2016 03:47 PM
  8. Robbie_Jardine's Avatar
    BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\avgntflt.sys is a driver for AntiVir, run the remover tool from http://forums.windowscentral.com/e?l...token=RSrpn_Gn

    The SSD driver could either be corrupt, contain bugs or just not playing right with the system. Have u tried install Win10 from and HDD an then trying to replicate the issue, I know not ideal but at least you will know for sure what the issue may be.

    Read this http://www.solvusoft.com/en/files/bs.../avgntflt-sys/
    07-01-2016 08:56 PM
  9. PCCalixto's Avatar
    I've ruled out the soundcard as being the cause.

    I had the normal Memory_Management error when I booted this morning.

    The stupid thing is that this almost never happens during the day. I shut my computer down cleanly and switched it off at the mains a dozen times yesterday while I was checking things suggested on this forum, and there were absolutely no problems. Then it BSOD the first time that I switched it on this morning.

    It's almost as if the computer will only BSOD if it's been shut down for a couple of hours or more.

    Could it be something as simple as a service or software package detecting that it hasn't been run in X hours, and checking online for updates?
    Do you have any Norton product installed? I had a lot of page_file errors because of a Norton product. They always happened during boot. Something about Norton products trying to scan your computer during cold boot. I solved uninstalling them. The problems happened a lot in past builds of Windows 10. Recently they had it solved but that on the anniversary update (I'm in insider preview). Symantec also had it updated so maybe that's the case.
    07-02-2016 05:01 AM
  10. Aaargh Zombies's Avatar
    Do you have any Norton product installed?
    I don't have any Norton products at all, When I was first trying ot resolve this problem I did a fresh install on an brand new SSD.

    It BSOD before I installed my Anti-Virus (Avira).
    07-03-2016 02:16 AM
  11. Aaargh Zombies's Avatar
    BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\avgntflt.sys is a driver for AntiVir
    I did a fresh install and there was a BSOD before I had installed the anti-virus.
    07-03-2016 02:17 AM
  12. Aaargh Zombies's Avatar
    See if there is a firmware update for the Sandisk, it could be a bad firmware version. i would also check your BIOS and see what your drive settings are set to. You would want AHCI (this may require a reinstall) and not IDE. In addition, I would uninstall Avira - according to the driver that didn't load it may be Avira's antivirus service. From the stack trace in the previous post (not 106), it shows that a file was opened and a bug check tried to occur when it crashed. It makes me think overall, something is up with either the drive configuration, the drive firmware, or there's an issue with the motherboard and how it interfaces with the drives.
    This actually happened for the first time on a regular disc when I did an upgrade. I then did a fresh install form an SSD.

    The first DSOB on the new disc was before I installed my anti-virus.

    It's set to AHCI, I'm not certain which other motherboard settings to check.

    I'm using BIOS rather than UEFI, if that's a clue to anything. I tried setting the motherboard to UEFI in the bios, but although my bios claims to support UEFI it couldn't find any UEFI devices to boot from so my install of Windows 10 doesn't seem to have been set up for it.

    I'm pretty certain that when I did the install I just used the default settings for everything, except for the privacy settings.
    07-03-2016 02:21 AM
  13. Aaargh Zombies's Avatar
    There were only 35 events before the BSOD, 33 of them were Windows Security Auditing events.

    The other two were "The Event log service was started." and "Microsoft (R) Windows (R) 10.00. 10586 Multiprocessor Free."

    This is the last record in the system event log before the last BSOD:

    An account was successfully logged on.

    Subject:
    Security ID: SYSTEM
    Account Name: DARKNESS$
    Account Domain: WORKGROUP
    Logon ID: 0x3E7

    Logon Information:
    Logon Type: 5
    Restricted Admin Mode: -
    Virtual Account: No
    Elevated Token: Yes

    Impersonation Level: Impersonation

    New Logon:
    Security ID: SYSTEM
    Account Name: SYSTEM
    Account Domain: NT AUTHORITY
    Logon ID: 0x3E7
    Linked Logon ID: 0x0
    Network Account Name: -
    Network Account Domain: -
    Logon GUID: {00000000-0000-0000-0000-000000000000}

    Process Information:
    Process ID: 0x314
    Process Name: C:\Windows\System32\services.exe

    Network Information:
    Workstation Name:
    Source Network Address: -
    Source Port: -

    Detailed Authentication Information:
    Logon Process: Advapi
    Authentication Package: Negotiate
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0

    This event is generated when a logon session is created. It is generated on the computer that was accessed.

    The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

    The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

    The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The impersonation level field indicates the extent to which a process in the logon session can impersonate.

    The authentication information fields provide detailed information about this specific logon request.
    - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    The previous event was:

    The Windows Firewall Driver started successfully.
    07-03-2016 02:24 AM
  14. Jason Rosenthal's Avatar
    It BSOD before I installed my Anti-Virus
    I'm surprised it lets you finish installing Windows before it BSOD. If both sticks of RAM are identical, then I'm leaning towards a weak power supply that someone already suggested. It seems like you're getting enough good power for one stick, but not two. Try under clocking the RAM, turn off xmp, and/or increasing the voltage slightly if your BIOS allows.

    If this is a desktop, pull all cards and turn off all unnecessary devices in BIOS. Don't have anything extra going until the CPU, RAM and Video are working stable.
    07-04-2016 03:36 PM
  15. Aaargh Zombies's Avatar
    I'm surprised it lets you finish installing Windows before it BSOD. If both sticks of RAM are identical, then I'm leaning towards a weak power supply that someone already suggested. It seems like you're getting enough good power for one stick, but not two. Try under clocking the RAM, turn off xmp, and/or increasing the voltage slightly if your BIOS allows.

    If this is a desktop, pull all cards and turn off all unnecessary devices in BIOS. Don't have anything extra going until the CPU, RAM and Video are working stable.
    Sorry, I wasn't clear.

    I originally thought that it might be the anti-virus, so I didn't install it.

    The first BSOD was the next day. It ran perfectly when I was using the PC for the first day, and BSOD when I turned it on the next morning. I didn't install the anti-virus until after I'd ruled it out.

    It's 100% not the power supply. A faulty power supply would create general instability in use, especially during gaming. This BSOD ONLY happens after the Pc has been cleanly shut down, and ONLY after it has been left powered off for some time. I went out for a couple of hours during the day and left my PC switched off, and it booted perfectly. Then I left it switched off over night and it BSOD.

    It's a consistent pattern. It looks like a software or program service is causing a BSOD if the time that it was shut down is significantly different from the time when it is turned back on. It sounds weird, but it's the only pattern that I can find other than the whole 8GB V 16GB thing. Which is why I thought that it might b e the paging file at first. If the software finds that the time in the paging file is significantly different from the actual time it BSOD.

    Why this only happens with 16gb of RAM I don't know, but one of the other people who commented said that Windows 10 splits the load between two sticks. Maybe whatever software or service this is can't retrieve it if it's split, or some weird thing like that?
    07-05-2016 02:09 AM
  16. slooksterpsv's Avatar
    Sorry, I wasn't clear.
    ...
    It's 100% not the power supply. A faulty power supply would create general instability in use, especially during gaming. This BSOD ONLY happens after the Pc has been cleanly shut down, and ONLY after it has been left powered off for some time. I went out for a couple of hours during the day and left my PC switched off, and it booted perfectly. Then I left it switched off over night and it BSOD.

    It's a consistent pattern. It looks like a software or program service is causing a BSOD if the time that it was shut down is significantly different from the time when it is turned back on. It sounds weird, but it's the only pattern that I can find other than the whole 8GB V 16GB thing. Which is why I thought that it might b e the paging file at first. If the software finds that the time in the paging file is significantly different from the actual time it BSOD.
    ...
    First, yes a power supply can cause issues like you've experienced. Usually it would happen more often under heavy load, but if its having difficulty maintaining a current, it can cause issues. I don't think that's the issue though.

    Second, do you know what your specs are for each stick? I mean you advise they're identical, however, are they? What is the CAS latency, what is the timing, the speed, etc.? Is one being over clocked or another being under clocked? Are there multiple slots (more than 2), if so have you tried a different channel?

    If you put in one chip and not the other, does the issue still occur?

    There's something we're all missing.... something very trivial....
    07-05-2016 08:53 PM
  17. D21K's Avatar
    Man... cant read all the post just to be sure, the hiberfill.sys was already ruled out? have you tried shutting down in the night them unplugging the power supply them checking how it boot in the morning? to check if there's something getting stored in the ram after the shutting down, also the windows fast startup thing.
    07-05-2016 09:12 PM
  18. Aaargh Zombies's Avatar
    do you know what your specs are for each stick? I mean you advise they're identical, however, are they? What is the CAS latency, what is the timing, the speed, etc.? Is one being over clocked or another being under clocked? Are there multiple slots (more than 2), if so have you tried a different channel?

    If you put in one chip and not the other, does the issue still occur?

    There's something we're all missing.... something very trivial....
    I think that I've covered most of that already.

    The RAM sticks were factory installed, they exact same make, model and specification.

    I have four slots on my MB. One is inaccessible because the CPU fan overlaps the slot, and I'm not willing to remove it. I've tried each stick individually in each of the three available slots and everything was perfect. I've tried both sticks together in each of the available slots and whatever configuration I used I got the BSOD.

    Memtest couldn't find any errors with either stick, individually or together.

    I ran CPU-Z and that said that the RAM sticks CAS Latency etc is identical. My Motherboard is set to Auto so if one stick were running at a lower speed it would simply clock the other one down to match. I favor stability over performance so nothing is overclocked.

    I have attatched a screen shot from CPU-Z with the specifications.

    EDIT: I've upgraded to the lasted version of the BIOS, so the one in the image is now out of date.
    Attached Thumbnails cpu-z.jpg  
    Last edited by Aaargh Zombies; 07-07-2016 at 03:01 AM.
    07-06-2016 02:19 AM
  19. Aaargh Zombies's Avatar
    Man... cant read all the post just to be sure, the hiberfill.sys was already ruled out? have you tried shutting down in the night them unplugging the power supply them checking how it boot in the morning? to check if there's something getting stored in the ram after the shutting down, also the windows fast startup thing.
    Sleep, Hybernate and fast boot all disabled.

    PC is always shut down and unplugged at night as the room that it's in is also used for sleeping and this cuts own on noise and heat.
    07-06-2016 02:23 AM
  20. Jason Rosenthal's Avatar
    Windows 10 splits the load between two sticks
    Load between the two sticks is configured by putting the RAM in the same coloured memory slots, the OS can't mess with that.. CPU-Z says you're in dual mode which is good.

    Your BIOS version does not look good. It says you are on F5b, but support for 4th gen started with F7. I would go with F8 as it has enhancements for your K processor.

    If Intel burn test runs fine and it only blue screens on shutdown, its probably not a hardware issue. BTW I have 2500k with a Gigabyte board and 32GB of Crutial RAM and it's rock solid running Windows 7 through to 10. I did switch to UEFI when moving to 8.0. Don't install any of the Gigabyte utilities.
    07-06-2016 01:04 PM
  21. Aaargh Zombies's Avatar
    Load between the two sticks is configured by putting the RAM in the same coloured memory slots, the OS can't mess with that.. CPU-Z says you're in dual mode which is good.

    Your BIOS version does not look good. It says you are on F5b, but support for 4th gen started with F7. I would go with F8 as it has enhancements for your K processor.

    If Intel burn test runs fine and it only blue screens on shutdown, its probably not a hardware issue. BTW I have 2500k with a Gigabyte board and 32GB of Crutial RAM and it's rock solid running Windows 7 through to 10. I did switch to UEFI when moving to 8.0. Don't install any of the Gigabyte utilities.
    Hi

    Sorry, a small mistake on my part. The CPU-Z is from when I first began trying to fix this problem. I've since upgraded the BIOS and have been on the latest version for a couple of weeks.

    The BSOD is on startup only, rather than shutdown, it's rock solid and stable during usage. Even intense gaming doesn't produce any instabilities.
    07-07-2016 02:55 AM
  22. pkcable's Avatar
    DAMN you still haven't resolved this! :(
    07-07-2016 08:30 AM
  23. Aaargh Zombies's Avatar
    The error only seems to happen if the PC is switched off for a while, if I shut down now and come back in an hour it will boot perfectly. If I leave it off overnight it will BSOD when I switch the PC on first think in the morning.

    This means that I'm essentially only able to try one possible solution per day, and it's why I'm sure that this is a software issue.

    It's almost as if the PC BSOD if the date that I switched it on is different form the date that I switched it off. For example, if a service detects that it hasn't updated for 12 hours and then check for a new version and brings the system down with it.
    07-07-2016 08:49 AM
  24. Jason Rosenthal's Avatar
    You have the weirdest problem I've ever heard of. With 8GB of RAM installed, you never get a BSOD and with 16 GB it will BSOD but only after a very cold boot. I'm back to thinking it is power related. Are you by chance turning the power bar off? Perhaps there is a capacitor that is getting drained overnight and isn't getting charged in time during first boot. Will it boot properly after pressing reset or does it require a full power off reboot?

    I would still try swapping power supplies. What power supply do you have in there now and how old is it?

    I always have a spare power supply on the shelf ready to go, sadly I've had to buy new ones more times than I like to admit. I can't say which one is a good one, I just go by bronze or better efficiency and then physical weight. The heavier the better.

    Have you disabled the onboard Intel video? It shares system RAM that could be affected by the second stick.
    07-07-2016 03:01 PM
  25. Aaargh Zombies's Avatar
    You have the weirdest problem I've ever heard of. With 8GB of RAM installed, you never get a BSOD and with 16 GB it will BSOD but only after a very cold boot. I'm back to thinking it is power related. Are you by chance turning the power bar off? Perhaps there is a capacitor that is getting drained overnight and isn't getting charged in time during first boot. Will it boot properly after pressing reset or does it require a full power off reboot?

    I would still try swapping power supplies. What power supply do you have in there now and how old is it?

    I always have a spare power supply on the shelf ready to go, sadly I've had to buy new ones more times than I like to admit. I can't say which one is a good one, I just go by bronze or better efficiency and then physical weight. The heavier the better.

    Have you disabled the onboard Intel video? It shares system RAM that could be affected by the second stick.
    I originally thought that it was the paging file, and that the file for 16GB was getting corrupted due to it's size and it not writing properly.

    Yes, the PC is connected using a power bar which is unplugged at the wall, but if I shut the PC down for a couple of hours it boots up OK, it's only after being shut down for long periods of time that is BSOD.

    If it's the PSU I'm going to have to wait until it totally fails, as I can't justify spending the money on it right now on the off-chance. It always BSOD in the exact same place, right to the absolute second. If it were a PSU problem I doubt that ti would be so predictable.

    I've tried enabling and disabling the onboard graphics and the onboard sound. Neither effects the BSOD.
    07-07-2016 03:07 PM
150 ... 3456

Similar Threads

  1. Anyone has not been able to get notifications like me?
    By Zhenren Zhou in forum Windows 10
    Replies: 6
    Last Post: 06-28-2016, 12:17 PM
  2. Cumulative Update for Windows 10 does not work. What do I do?
    By Windows Central Question in forum Windows 10
    Replies: 3
    Last Post: 06-27-2016, 04:42 PM
  3. Mobile Outlook not working (error 80004005)
    By r0st4 in forum Windows 10 Mobile
    Replies: 4
    Last Post: 06-23-2016, 01:48 PM
  4. Platinum Games would love Metal Gear Rising on backwards compatibility, but it's up to Konami
    By WindowsCentral.com in forum Windows Central News Discussion
    Replies: 0
    Last Post: 06-23-2016, 06:20 AM
  5. Why isn't my Lumia 630 turning on?
    By Windows Central Question in forum Nokia Lumia 630
    Replies: 1
    Last Post: 06-23-2016, 05:15 AM
LINK TO POST COPIED TO CLIPBOARD