Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

# Windows 7: BSOD Suddenly

 15 Aug 2014 #1 kinshingz Windows 7 Ultimate x64 2 posts BSOD Suddenly My PC is running on Windows 7 x64 bit. A few days back my PC starts to get BSOD once awhile and suddenly today, every few minutes it gets BSODed. This is the crash log i can retrieve can anyone assists me? Code:  -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 15/8/2014 3:56:19 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-78140-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A13EB30, 0xFFFFFA800A13EE10, 0xFFFFF800039DD270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 3:56:19 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A13EB30, 0xFFFFFA800A13EE10, 0xFFFFF800039DD270) Error: CRITICAL_OBJECT_TERMINATION Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 3:49:41 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-88421-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A28BB30, 0xFFFFFA800A28BE10, 0xFFFFF8000397B270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 3:26:49 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-86814-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008F5FB30, 0xFFFFFA8008F5FE10, 0xFFFFF80003986270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 3:18:54 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-81245-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009BB7B30, 0xFFFFFA8009BB7E10, 0xFFFFF800039DF270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 3:11:25 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-80200-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF8A010B23010) Error: BAD_POOL_CALLER file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the current thread is making a bad pool request. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 2:53:30 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-32339-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A035950, 0xFFFFFA800A035C30, 0xFFFFF8000398B270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 2:44:15 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-40981-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009EED270, 0xFFFFFA8009EED550, 0xFFFFF80003981270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 2:36:09 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-37003-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800A828690, 0x0) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 15/8/2014 2:22:00 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081514-45599-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009B50B30, 0xFFFFFA8009B50E10, 0xFFFFF800039D9270) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Thanks, Ben. My System Specs
 .
 15 Aug 2014 #2 Arc Microsoft Windows 10 Pro Insider Preview 64-bit 36,037 posts Click on the button below .... It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip. Screenshots and Files - Upload and Post in Seven Forums My System Specs
 16 Aug 2014 #3 kinshingz Windows 7 Ultimate x64 2 posts Attached is the zip file. My System Specs
 .
 16 Aug 2014 #4 Arc Microsoft Windows 10 Pro Insider Preview 64-bit 36,037 posts Code: fffff8800c75da68 fffff88003dd53efUnable to load image \SystemRoot\system32\DRIVERS\ehdrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ehdrv.sys *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys ehdrv+0x1c3ef What is ehdrv.sys ? | System Explorer Code: fffff8800c75d508 fffffa80093f3fa2Unable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat, Win32 error 0n2 *** WARNING: Unable to verify timestamp for em018_64.dat *** ERROR: Module load completed but symbols could not be loaded for em018_64.dat em018_64+0x19fa2 The path is: C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat Most probably it is the ESET antivirus that is causing the issue. Or it may be not. But elimination of this factor is needed for troubleshooting. Uninstall ESET. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner. Then let us know the situation. My System Specs
 16 Aug 2014 #5 HarriePateman Windows 7 Ultimate 64-bit 3,914 posts South UK, Bournemouth Quote: Originally Posted by Arc Code: fffff8800c75da68 fffff88003dd53efUnable to load image \SystemRoot\system32\DRIVERS\ehdrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ehdrv.sys *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys ehdrv+0x1c3ef What is ehdrv.sys ? | System Explorer Code: fffff8800c75d508 fffffa80093f3fa2Unable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat, Win32 error 0n2 *** WARNING: Unable to verify timestamp for em018_64.dat *** ERROR: Module load completed but symbols could not be loaded for em018_64.dat em018_64+0x19fa2 The path is: C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat Most probably it is the ESET antivirus that is causing the issue. Or it may be not. But elimination of this factor is needed for troubleshooting. Uninstall ESET. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner. Then let us know the situation. Good Spot Arc My System Specs
 16 Aug 2014 #6 Arc Microsoft Windows 10 Pro Insider Preview 64-bit 36,037 posts Thank you mate. My System Specs