[rshaffer61]

OK according to your dmp file it is a windows file but I am suspicious since it also states another driver could be the issue.

I want to try Driver Verifier to see if it shows anything causing the issue.
After running it you can disable it if you wish. Just follow the instructions on the page to enable, run and then disable it.

[Advertisements]

will repost after i start driver verifier again. i did see a blue screen (i will try to get that info) but upon restart it would not and startup repair kept asking for system restore.. this is the info from whocrashedit

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 11/4/2013 6:12:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110413-01.dmp
This was probably caused by the following module: ousbehci.sys (ousbehci+0x4BC0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82717610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ousbehci.sys
product: USB 2.0 Enhanced Host Controller Driver
company: OrangeWare Corporation
description: USB 2.0 Enhanced Host Controller Driver
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.
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: ousbehci.sys (USB 2.0 Enhanced Host Controller Driver, OrangeWare Corporation).
Google query: OrangeWare Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 11/4/2013 6:12:45 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF82717610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Mon 10/28/2013 6:12:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102813-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DCD1)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF805D3130, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
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 Tue 10/22/2013 8:41:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102213-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98292)
Bugcheck code: 0x1A (0x41287, 0x4D842E6D, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/25/2013 4:59:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092513-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0x210, 0xFF, 0x0, 0xFFFFFFFF824F4DCB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 9/13/2013 8:00:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x238A42)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82673A42, 0xFFFFFFFF9F14912C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ousbehci.sys (USB 2.0 Enhanced Host Controller Driver, OrangeWare Corporation)
ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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 actually 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.

[xppc]

will repost after i start driver verifier again. i did see a blue screen (i will try to get that info) but upon restart it would not and startup repair kept asking for system restore.. this is the info from whocrashedit

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 11/4/2013 6:12:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110413-01.dmp
This was probably caused by the following module: ousbehci.sys (ousbehci+0x4BC0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82717610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ousbehci.sys
product: USB 2.0 Enhanced Host Controller Driver
company: OrangeWare Corporation
description: USB 2.0 Enhanced Host Controller Driver
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.
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: ousbehci.sys (USB 2.0 Enhanced Host Controller Driver, OrangeWare Corporation).
Google query: OrangeWare Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 11/4/2013 6:12:45 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF82717610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Mon 10/28/2013 6:12:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102813-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DCD1)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF805D3130, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
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 Tue 10/22/2013 8:41:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102213-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98292)
Bugcheck code: 0x1A (0x41287, 0x4D842E6D, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/25/2013 4:59:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092513-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0x210, 0xFF, 0x0, 0xFFFFFFFF824F4DCB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 9/13/2013 8:00:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x238A42)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82673A42, 0xFFFFFFFF9F14912C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ousbehci.sys (USB 2.0 Enhanced Host Controller Driver, OrangeWare Corporation)
ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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 actually 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.

[rshaffer61]

Your laast error on WhoCrashed showed this:

file path: C:\Windows\system32\drivers\ousbehci.sys
product: USB 2.0 Enhanced Host Controller Driver

This is your USB driver which looks to either have failed, is faulty or needs updating.

[xppc]

when i retried to get the blue screen, the only one that can up was saying if this is the first time you have seen this screen. it went thru system repair and restore again. drivermax shows just a realtek high definition audio is not current. i will google search the one you just listed


this was the last crash


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 11/4/2013 6:34:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110413-01.dmp
This was probably caused by the following module: ousbehci.sys (ousbehci+0x4BC0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82716610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ousbehci.sys
product: USB 2.0 Enhanced Host Controller Driver
company: OrangeWare Corporation
description: USB 2.0 Enhanced Host Controller Driver
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.
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: ousbehci.sys (USB 2.0 Enhanced Host Controller Driver, OrangeWare Corporation).
Google query: OrangeWare Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 11/4/2013 6:34:59 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF82716610, 0xFFFFFFFF8596964C, 0xFFFFFFFF85969348)
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

[xppc]

i am finding lots of driver places but not actual driver.. even at http://orangeware-co...s.informer.com/

http://www.intel.com.../support/detect (i ran this twice and the pc crashed blue screen) below is the whocrashed log. i will go to the hp website and check drivers for this model desk top and see if the correct usb driver is there

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/6/2013 4:53:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110613-02.dmp
This was probably caused by the following module: cpudrv.sys (cpudrv+0x674)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA1D4B674, 0xFFFFFFFFA36F8B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: cpudrv.sys .
Google query: cpudrv.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Wed 11/6/2013 4:53:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cpudrv.sys (cpudrv+0x56F)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA1D4B674, 0xFFFFFFFFA36F8B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application 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: cpudrv.sys .
Google query: cpudrv.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED



On Wed 11/6/2013 4:40:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110613-01.dmp
This was probably caused by the following module: cpudrv.sys (cpudrv+0x674)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA13FA674, 0xFFFFFFFF9A769B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: cpudrv.sys .
Google query: cpudrv.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

[rshaffer61]

Are you using DriverMax or the motherboard manufacturers website?
If a branded system then the branded names web site.

[xppc]

the crash report the other day said orange ware dealing with the intel usb drivers. i just thought intel site would have that. the automatic program said... HP was unable to verify that you have this product, but did find other products. i have been using driver max until this, there is a usb driver that failed to update and rolled back to the previous version.

Edited by xppc, 06 November 2013 - 11:30 AM.

[rshaffer61]

Normally the manufacturer is the best course of action but sometimes we have to look else where for the most current.

[xppc]

driver max scan just claimed all it up to date. when i try to scan it says no communication to scanner. and an information box comes up on the bottom right saying it can preform better if it is plugged into a hi speed port, then says i must add a hi speed usb host controller to this computer to obtain maximum performance.

i take it that is what we are looking for.. correct?

Edited by xppc, 06 November 2013 - 11:38 AM.

[rshaffer61]

Correct the USB controller or the USB Hub controller.

[xppc]

under device manager there were two individual lines showing usb controllers. the second showed USB 2.0 Enhanced Host Controller Driver. i clicked on it and updated the driver and device manager changed to just one line od usb controllers and "standard enhanced pci to usb host controller" showed up there as well as " standard openhcd usb host controller"
all the individual driver when i clickd on them claimed to be up to date.

the scanner still says it is not communicating. should i try to unimstall and reinstall the printer again?

[rshaffer61]

Yep uninstall and reinstall.

[xppc]

i just uninstalled and reinstalled the printer. printing works but not the scanner. according to the desktop incon..scanner communication cannot be established. when i try thru the start menu hp icon for the scanner it says the same thing.

ideas?

[rshaffer61]

What make and model is the printer\scanner?

[xppc]

HP deskjet 1050 J410 series. i did try another printer cord the other day with no luck. i can bring my laptop and try and see if the scan option works on it. i do know the scan option has worked previously on moms pc.