PC Crashes Randomly and Can't Update Error 80070002

B

Beasie

Member
Joined
Sep 28, 2013
Posts
11
- Windows 7 Ultimate
- x64bit
- I think Windows Vista
- Full Retail
- 2009

- AMD Athlon II X4 645 processor 3.81Ghz (Overclocked) But should be crashing hasn't for months until now. I think its overclocked from 3.2
- ATI Radeon HD 5670
-GA-970A-D3 motherboard
-550w
Custom Built pc

 
Hi,

Two dumps, two bugchecks:

CRITICAL_OBJECT_TERMINATION (f4)

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

BugCheck F4, {3, fffffa8008a87730, fffffa8008a87a10, fffff800043928b0}

The 1st parameter is 3 which implies it was a process rather than a thread.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

IMAGE_NAME: hardware

MODULE_NAME: hardware

Probably caused by : hardware

-------------------------------------------------------------------

1. Undo the overclock ASAP by setting everything to default via the BIOS. It is more than likely the cause of your crashes.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Keep me updated after the above recommendations.

Regards,

Patrick
 
Patrick said:
Hi,

Two dumps, two bugchecks:

CRITICAL_OBJECT_TERMINATION (f4)

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

BugCheck F4, {3, fffffa8008a87730, fffffa8008a87a10, fffff800043928b0}

The 1st parameter is 3 which implies it was a process rather than a thread.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

IMAGE_NAME: hardware

MODULE_NAME: hardware

Probably caused by : hardware

-------------------------------------------------------------------

1. Undo the overclock ASAP by setting everything to default via the BIOS. It is more than likely the cause of your crashes.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Keep me updated after the above recommendations.

Regards,

Patrick
Click to expand...

Ok let me ask this again how do i solve my Error code 80070002 I am not able to Update through windows update. Have not been able to for a long time now.... and i have done all above steps and as for the crashing eh see'in as how i been over 7 months without 1 crash while it has been overclocked i don't think that's the issue that's just the EZ answer out... Explain to me how its the issue. I know how it can be but i sent you logs did you get any Details showing that its because its overclocked??
 
Please follow my recommendations. There is no harm in either, and it will make any further troubleshooting if necessary much easier. If the overclock is not the issue, you can put it back after your issue is solved. When an overclock is not stable, it can cause a large variety of issues. An overclock can be what is thought to be 'stable' for months, maybe even a year, but if it's crashing and the crash dumps point to hardware, it's most likely not stable. Again, if you do what I asked everything will get much easier and we will get to the bottom of it all.

Troubleshooting, especially with BSOD's, requires patience and of course... troubleshooting. When you remove various troublesome variables it gets much easier and the answer becomes more clear.

In regards to Windows Update error, have you tried FixIt first? Fix the problem with Microsoft Windows Update that is not working

Here's a detailed article on steps to follow to work on fixing said error - Windows Update error 80070002

Regards,

Patrick
 
Last edited:
Patrick said:
Please follow my recommendations. There is no harm in either, and it will make any further troubleshooting if necessary much easier. If the overclock is not the issue, you can put it back after your issue is solved. When an overclock is not stable, it can cause a large variety of issues. An overclock can be what is thought to be 'stable' for months, maybe even a year, but if it's crashing and the crash dumps point to hardware, it's most likely not stable. Again, if you do what I asked everything will get much easier and we will get to the bottom of it all.

Troubleshooting, especially with BSOD's, requires patience and of course... troubleshooting. When you remove various troublesome variables it gets much easier and the answer becomes more clear.

In regards to Windows Update error, have you tried FixIt first? Fix the problem with Microsoft Windows Update that is not working

Here's a detailed article on steps to follow to work on fixing said error - Windows Update error 80070002

Regards,

Patrick
Click to expand...

6a4df505aa104b544bf7b1ea7987d5e8.png
 
Beasie, I cannot help you if you don't follow my recommendations, and neither can anyone else. It's as simple as that.

Regards,

Patrick
 
Okay:

1. Undo the overclock ASAP by setting everything to default via the BIOS. It is more than likely the cause of your crashes.
Click to expand...

^^ As I explained above, regardless of whether the overclock is stable (it's likely not) it's a variable in troubleshooting that if we removed, it would make things much easier. If we don't remove it from the equation, when we get future crashes (if any) and we see hardware causes from the crash dumps, etc, we're always going to be saying 'well.... if we removed the overclock', etc. Trust me, returning the BIOS to optimized defaults and ruling it out FOR NOW is best and will help us get to the bottom of your crashes for sure. As I said many times, it's most likely even the problem. And if it wasn't? After your crashing issue is fixed, you can put it right back to overclocked.

I am a Forum Moderator on Overclock.net with over 14,000 posts. I have been around, participated in, and helped thousands of users with overclocking their systems, even my own. I have experience with it and know what an unfortunate unstable overclock can do. I am not just recommending removing your overclock from the equation because I feel like it.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows
Click to expand...

^^ avast! is a 3rd party antivirus, and also a suite at that. It has many jobs and does various different things although it may not seem like it. Antiviruses are working all the time and making various calls in the operating system. There are many programs, devices, etc, that conflict with said antivirus suites and cause issues. I have solved many cases lately in which avast! was the cause of the crashes. Again, it's a variable in the crashes that if we removed, it makes troubleshooting much easier.

3. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
Click to expand...

^^ Self-explanatory since I explained most of it right there. Daemon Tools has always been troublesome software. If your dtsoftbus01.sys driver is dated from 2013 it has been reported that it works okay without causing any conflicts, but I personally wouldn't recommend leaving it installed. There are many alternatives that work just as well.

Regards,

Patrick
 
Patrick said:
Okay:

1. Undo the overclock ASAP by setting everything to default via the BIOS. It is more than likely the cause of your crashes.
Click to expand...

^^ As I explained above, regardless of whether the overclock is stable (it's likely not) it's a variable in troubleshooting that if we removed, it would make things much easier. If we don't remove it from the equation, when we get future crashes (if any) and we see hardware causes from the crash dumps, etc, we're always going to be saying 'well.... if we removed the overclock', etc. Trust me, returning the BIOS to optimized defaults and ruling it out FOR NOW is best and will help us get to the bottom of your crashes for sure. As I said many times, it's most likely even the problem. And if it wasn't? After your crashing issue is fixed, you can put it right back to overclocked.

I am a Forum Moderator on Overclock.net with over 14,000 posts. I have been around, participated in, and helped thousands of users with overclocking their systems, even my own. I have experience with it and know what an unfortunate unstable overclock can do. I am not just recommending removing your overclock from the equation because I feel like it.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows
Click to expand...

^^ avast! is a 3rd party antivirus, and also a suite at that. It has many jobs and does various different things although it may not seem like it. Antiviruses are working all the time and making various calls in the operating system. There are many programs, devices, etc, that conflict with said antivirus suites and cause issues. I have solved many cases lately in which avast! was the cause of the crashes. Again, it's a variable in the crashes that if we removed, it makes troubleshooting much easier.

3. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
Click to expand...

^^ Self-explanatory since I explained most of it right there. Daemon Tools has always been troublesome software. If your dtsoftbus01.sys driver is dated from 2013 it has been reported that it works okay without causing any conflicts, but I personally wouldn't recommend leaving it installed. There are many alternatives that work just as well.

Regards,

Patrick
Click to expand...

Ok everything's like you said back to 3.10 Ghz OUCH! what next?
 
I understand, overclocking is fun and achieving a stable overclock is very pleasing. No worries, you can continue to do so once we get your issues fixed. Now that you've done step #1, follow #2 and #3 and keep me updated on the system's behavior.

Regards,

Patrick
 
Patrick said:
I understand, overclocking is fun and achieving a stable overclock is very pleasing. No worries, you can continue to do so once we get your issues fixed. Now that you've done step #1, follow #2 and #3 and keep me updated on the system's behavior.

Regards,

Patrick
Click to expand...

All steps are done 2 and 3 were done before 1 :) everything seems fine like i said its usually when i just boot up i get lots of errors and stuff. all the boot ups i have done so far i have not seen any errors. No crashes yet.
 
Back
Top