Windows 7 Forums

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
 
 
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 SpecsSystem Spec
.
15 Aug 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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 SpecsSystem Spec
16 Aug 2014   #3
kinshingz

Windows 7 Ultimate x64
 
 

Attached is the zip file.
My System SpecsSystem Spec
.

16 Aug 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
fffff880`0c75da68  fffff880`03dd53efUnable 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:
fffff880`0c75d508  fffffa80`093f3fa2Unable 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 SpecsSystem Spec
16 Aug 2014   #5
HarriePateman

Windows 7 Ultimate 64-bit
 
 

Quote   Quote: Originally Posted by Arc View Post
Code:
fffff880`0c75da68  fffff880`03dd53efUnable 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:
fffff880`0c75d508  fffffa80`093f3fa2Unable 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 SpecsSystem Spec
16 Aug 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Thank you mate.
My System SpecsSystem Spec
Reply

 BSOD Suddenly




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Suddenly Surfing Net
Hi Sevenforums I got a BSOD suddenly yesterday, I was just surfing on the internet and then when I went into this site: Tech Made Easy - I got the BSOD. When the PC started again I did only have 4GB RAM? But I have 8GB installed. I've attached the zip file. kfrandsen
BSOD Help and Support
Getting BSOD suddenly windows 7
Hi, i was playing some Guild Wars 2 a yesterday and after exiting the game a BSOD flashed up. I think after looking a little i found it might of been my drivers (radeon 5770) hadn't been updated in awhile. I tried to download it but my computer was getting a BSOD after 5 minutes. I managed to...
BSOD Help and Support
BSOD suddenly
Hi, I don't know from what apper this BSOD, but it persist for couple of months. I'll apreciate your help. king regards.
BSOD Help and Support
BSOD Err suddenly
driver power state failure (BSOD) Attached files, no idea what they mean. System, Asus Formula V MB, 16g memory, Win 7 x64
BSOD Help and Support
I got BSOD suddenly
Hi,while I was working on my pc,suddenly monitor has blinked (2-3 times),I got this error ,and a second after that I get a BSOD. Here are the attached files. I restarted the computer,and when I login I got this: Windows has recovered from an unexpected shutdown I got the latest version of Nvidia...
BSOD Help and Support
Suddenly getting BSOD's
For the past day have been getting BSOD's was all fine up till then this is the latest one The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 20:08.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App