Blue Screen: Stop: 0x0000007E....
Started by
Dumb-Dumb
, Jul 01 2012 06:59 PM
#1
Posted 01 July 2012 - 06:59 PM
Dumb-Dumb
-
- Member
-
- 4 posts
New Member
#2
Posted 03 July 2012 - 05:45 PM
happyrock
-
- Retired Staff
-
- 9,285 posts
Tech Moderator
Hi Dumb-Dumb ... 
..
please use the standard font and size...I only have one eye and it don't see so good...thanks
download and install WhoCrashed from http://www.softpedia...hoCrashed.shtml ' class='bbc_url' title='External link' rel='nofollow external'>here
..
This program checks for any drivers which may have been causing your computer to crash....
click on it...then run...then next...put a tick in accept...then next..put a tick in the
don't create a start menu folder..then next...put a tick in create a desktop icon..then
install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze
...
if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not
normally installed and is not redistributable, we suggest you select the download option from below. Then the right
package will be downloaded to a temporary folder and the required files will be extracted from the package
automatically. You only need to do this once
click on download then try running it again
WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply..
..please use the standard font and size...I only have one eye and it don't see so good...thanks
download and install WhoCrashed from http://www.softpedia...hoCrashed.shtml ' class='bbc_url' title='External link' rel='nofollow external'>here
..
This program checks for any drivers which may have been causing your computer to crash....
click on it...then run...then next...put a tick in accept...then next..put a tick in the
don't create a start menu folder..then next...put a tick in create a desktop icon..then
install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze
...
if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not
normally installed and is not redistributable, we suggest you select the download option from below. Then the right
package will be downloaded to a temporary folder and the required files will be extracted from the package
automatically. You only need to do this once
click on download then try running it again
WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply..
#3
Posted 04 July 2012 - 08:01 AM
Dumb-Dumb
- Topic Starter
-
- Member
-
- 4 posts
New Member
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 7/4/2012 2:53:29 AM 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: 0x7E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFA6001BBD858, 0xFFFFFA6001BBD230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/4/2012 2:36:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070312-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x12C5)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8800CFC8C00, 0x0, 0x9DFE)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 7/3/2012 3:11:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4E9FB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800026A89FB, 0xFFFFFA6001D657E8, 0xFFFFFA6001D651C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 which cannot be identified at this time.
On Mon 7/2/2012 8:55:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070212-01.dmp
This was probably caused by the following module: ????????????????a (nt+0x178B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFA6000ABF639, 0xFFFFFA60066B6B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ????????????????a .
Google query: ????????????????a SYSTEM_SERVICE_EXCEPTION
On Mon 7/2/2012 12:18:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070112-01.dmp
This was probably caused by the following module: alg_1.sys (ALG_1+0x133F)
Bugcheck code: 0xD1 (0xFFFFFA800519C000, 0x2, 0x0, 0xFFFFFA6005358890)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alg_1.sys .
Google query: alg_1.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 6/30/2012 5:02:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini063012-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x12C5)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8800D50B890, 0x0, 0x15BAC)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/28/2012 7:51:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062812-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFA6001115552)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFA60042B50FF, 0xFFFFFA60057E19F8, 0xFFFFFA60057E13D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Tue 6/26/2012 5:23:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062612-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000000.sys (Unloaded_Unknown_Module_00000000`0000000+0x7289AAD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000292A490, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`0000000.sys .
Google query: unknown_module_00000000`0000000.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 6/19/2012 7:30:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062012-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000000.sys (Unloaded_Unknown_Module_00000000`0000000+0x0)
Bugcheck code: 0xD1 (0x60, 0xB, 0x0, 0xFFFFFA6004021A3A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`0000000.sys .
Google query: unknown_module_00000000`0000000.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Thank You soo much by the way.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 7/4/2012 2:53:29 AM 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: 0x7E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFA6001BBD858, 0xFFFFFA6001BBD230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/4/2012 2:36:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070312-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x12C5)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8800CFC8C00, 0x0, 0x9DFE)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 7/3/2012 3:11:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4E9FB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800026A89FB, 0xFFFFFA6001D657E8, 0xFFFFFA6001D651C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 which cannot be identified at this time.
On Mon 7/2/2012 8:55:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070212-01.dmp
This was probably caused by the following module: ????????????????a (nt+0x178B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFA6000ABF639, 0xFFFFFA60066B6B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ????????????????a .
Google query: ????????????????a SYSTEM_SERVICE_EXCEPTION
On Mon 7/2/2012 12:18:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini070112-01.dmp
This was probably caused by the following module: alg_1.sys (ALG_1+0x133F)
Bugcheck code: 0xD1 (0xFFFFFA800519C000, 0x2, 0x0, 0xFFFFFA6005358890)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alg_1.sys .
Google query: alg_1.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 6/30/2012 5:02:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini063012-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x12C5)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8800D50B890, 0x0, 0x15BAC)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/28/2012 7:51:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062812-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFA6001115552)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFA60042B50FF, 0xFFFFFA60057E19F8, 0xFFFFFA60057E13D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Tue 6/26/2012 5:23:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062612-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000000.sys (Unloaded_Unknown_Module_00000000`0000000+0x7289AAD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000292A490, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`0000000.sys .
Google query: unknown_module_00000000`0000000.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 6/19/2012 7:30:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062012-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000000.sys (Unloaded_Unknown_Module_00000000`0000000+0x0)
Bugcheck code: 0xD1 (0x60, 0xB, 0x0, 0xFFFFFA6004021A3A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`0000000.sys .
Google query: unknown_module_00000000`0000000.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Thank You soo much by the way.
#4
Posted 04 July 2012 - 09:58 AM
happyrock
-
- Retired Staff
-
- 9,285 posts
Tech Moderator
we may need to reinstall your chipset and video card driver so what is the make and model number of your computer...
Please Run the PCPitstop.com OverDrive Full Tests
Here's how:
You must use Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.
Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)
Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.
The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.
Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.
Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.
After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.
While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.
Please Run the PCPitstop.com OverDrive Full Tests
Here's how:
You must use Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.
Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)
Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.
The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.
Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.
Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.
After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.
While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.
#6
Posted 04 July 2012 - 11:49 AM
happyrock
-
- Retired Staff
-
- 9,285 posts
Tech Moderator
download this free tool...
CCleaner
Don't install any Toolbars, or other programs, should it ask you...Just
uncheck the option of installing the Yahoo toolbar....if you get
the slim version it does not have the toolbar
thats the one I recommend...
It will put a shortcut on your Desktop.
Click on CCleaner to start it....
Before first use...
Select Options then Advanced.
UNCHECK "Only delete files in Windows Temp folder older than 48 hours"
also UNCHECK Old Prefetch data..
The rest of the standard settings are fine...
Then click "Run Cleaner"
DO NOT USE ANY OF THE OTHER TOOLS...RUNNING THEM MAY CAUSE OTHER PROBLEMS
when thats done defrag your system...
go here...put in your service tag number or on the right side put a tick in automatically detect my service tag number...once there copy and paste the link to your drivers page in your reply and I will tell you which ones to get
CCleaner
Don't install any Toolbars, or other programs, should it ask you...Just
uncheck the option of installing the Yahoo toolbar....if you get
the slim version it does not have the toolbar
thats the one I recommend...
It will put a shortcut on your Desktop.
Click on CCleaner to start it....
Before first use...
Select Options then Advanced.
UNCHECK "Only delete files in Windows Temp folder older than 48 hours"
also UNCHECK Old Prefetch data..
The rest of the standard settings are fine...
Then click "Run Cleaner"
DO NOT USE ANY OF THE OTHER TOOLS...RUNNING THEM MAY CAUSE OTHER PROBLEMS
when thats done defrag your system...
go here...put in your service tag number or on the right side put a tick in automatically detect my service tag number...once there copy and paste the link to your drivers page in your reply and I will tell you which ones to get
#8
Posted 04 July 2012 - 05:35 PM
happyrock
-
- Retired Staff
-
- 9,285 posts
Tech Moderator
thats the same link I gave you...you need to put in your service tag number...click on submit...its going to make you select the operating system you have then its going to take you to your drivers page...thats the url I need
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
