Hello all,
I've been having BSODs lately on a fresh installation of Windwos 8.1x64 on my Dell Optiplex 7020 (1TB + 500GB HDD, 4GBx4 = 16GB RAM)
Attached log along with mini dump files zipped in it.
This first hapenned in a rather strange way, when I connected a usb pen drive to the PC and while copying files the screen went all static color and I powered it off immediately. Powered on again, started copying files to same pen drive and bam! Crashed again. Thought maybe the pen drive has a problem. Connected an External HDD and same thing PC crashes and restarts. It then stopped for some time, and been happening again and again since.
I've noticed that it happens when I'm copying anything to a USB drive.
Nothing happens when I'm using the PC or even gaming.
I'm suspecting RAM/ HDD problem though don't know which one.
Dell ePSA tests reveal no error, netiher does windows memory diagnostic, neither does crystal disk info, nor SeaTools for Windows (short and DST tests pass).
Dump Analysis from WhoCrashed:
I've been having BSODs lately on a fresh installation of Windwos 8.1x64 on my Dell Optiplex 7020 (1TB + 500GB HDD, 4GBx4 = 16GB RAM)
Attached log along with mini dump files zipped in it.
This first hapenned in a rather strange way, when I connected a usb pen drive to the PC and while copying files the screen went all static color and I powered it off immediately. Powered on again, started copying files to same pen drive and bam! Crashed again. Thought maybe the pen drive has a problem. Connected an External HDD and same thing PC crashes and restarts. It then stopped for some time, and been happening again and again since.
I've noticed that it happens when I'm copying anything to a USB drive.
Nothing happens when I'm using the PC or even gaming.
I'm suspecting RAM/ HDD problem though don't know which one.
Dell ePSA tests reveal no error, netiher does windows memory diagnostic, neither does crystal disk info, nor SeaTools for Windows (short and DST tests pass).
Dump Analysis from WhoCrashed:
[FONT=Segoe UI, Arial]Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 9/25/2015 3:10:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-15750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14F9A0)
Bugcheck code: 0x7A (0xFFFFF6E800DDDA58, 0xFFFFFFFFC000000E, 0x31E887BE0, 0xFFFFD001BBB4B000)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 9/25/2015 3:10:17 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0xFFFFF6E800DDDA58, 0xFFFFFFFFC000000E, 0x31E887BE0, 0xFFFFD001BBB4B000)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 9/21/2015 2:18:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092015-21906-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14F9A0)
Bugcheck code: 0xEF (0xFFFFE0011CEBD8C0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_PROCESS_DIED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 9/21/2015 1:51:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092015-19109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14F9A0)
Bugcheck code: 0xEF (0xFFFFE001145FC380, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_PROCESS_DIED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]
My Computer
System One
-
- OS
- Windows 8.1 x64