Hardward Driver Conflict
Started by
Jason77
, Jul 30 2011 08:37 AM
#16
Posted 10 August 2011 - 03:04 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
#17
Posted 10 August 2011 - 03:10 PM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
Yep. They both ran and completed but no luck. You ever use a laptop as a Frisbee?
#18
Posted 10 August 2011 - 03:17 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
No, but I can undertsnad your frustration.
However please do not give up just yet.
Please run this
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The following image is the test results area:
The most important item here is the "errors" line. If you see ANY errors, even one, most likely, you have bad RAM.
However please do not give up just yet.
Please run this
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
- Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The following image is the test results area:
The most important item here is the "errors" line. If you see ANY errors, even one, most likely, you have bad RAM.
#19
Posted 10 August 2011 - 03:20 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Additionally I have just re-read the thread - on the 3 August you mentioned a BSOD.
Have you had others.
Please run this, click the analyse tab and scroll down to the results then copy and paste those please to a reply.
http://www.resplendence.com/whocrashed
You may most properly do this first if that suits.
Have you had others.
Please run this, click the analyse tab and scroll down to the results then copy and paste those please to a reply.
http://www.resplendence.com/whocrashed
You may most properly do this first if that suits.
#20
Posted 11 August 2011 - 07:55 PM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
I am unable to run whocrashed, becasue i can only get the computer to boot in safe mode and it needs the windows installer to install the WinDbg x86 package.
#21
Posted 12 August 2011 - 09:19 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".
For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.
If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.
Go Start and then Run
type in regedit and click OK
Navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
You will see various entries Values on the right hand side.
The one we want is called: SourcePath
It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.
Now restart your computer and try sfc /scannow again!
Thanks to Broni for the instructions
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".
For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.
If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.
Go Start and then Run
type in regedit and click OK
Navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
You will see various entries Values on the right hand side.
The one we want is called: SourcePath
It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.
Now restart your computer and try sfc /scannow again!
Thanks to Broni for the instructions
#22
Posted 17 August 2011 - 02:59 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Jason77
It has been five days since your last reply.
How are you progressing please.
Were you able to run the system file checker recommended by rshaffer61
Please let us know, if the problem is solved or you still require help.
Thanks you.
It has been five days since your last reply.
How are you progressing please.
Were you able to run the system file checker recommended by rshaffer61
Please let us know, if the problem is solved or you still require help.
Thanks you.
#23
Posted 18 August 2011 - 07:15 AM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
I will try this again tonight when i get home but i do not think it let me run this in safe mode.
#24
Posted 18 August 2011 - 04:23 PM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
This is the message I am getting.
Windows File Protection could not initiate a scan of protected system files.
The specific error code is 0x000006ba [The RPC server is unavailable.
].
I am in safe mode since noraml mode causes blue screen.
Windows File Protection could not initiate a scan of protected system files.
The specific error code is 0x000006ba [The RPC server is unavailable.
].
I am in safe mode since noraml mode causes blue screen.
#25
Posted 18 August 2011 - 04:27 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Try doing the following in Safe Mode and then reboot into Normal Mode Does the BSOD happen then? If not then continue with the next steps indicated in RED
Lets see what you have in your startup
Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
Lets see what you have in your startup
Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
#26
Posted 18 August 2011 - 09:46 PM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
Here is the log from WhoCrashe. I have updated all the drivers from the dell site multiple times.
--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: SUZY
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Celeron® M processor 1.40GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1333129216 total
VM: 2147352576, free: 2041860096
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 8/18/2011 10:34:26 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081811-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF93D3D0F3, 0x0, 0xFFFFFFFFB28995D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Thu 8/4/2011 10:23:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080411-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF93C770F3, 0x0, 0xFFFFFFFFB79225D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Tue 8/2/2011 3:17:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080111-02.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF955AF0F3, 0x0, 0xFFFFFFFFB02205D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Tue 8/2/2011 3:06:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080111-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF9252B0F3, 0x0, 0xFFFFFFFFB070D5D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Mon 8/1/2011 2:42:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073111-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF941330F3, 0x0, 0xFFFFFFFFB09D75D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sat 7/30/2011 2:55:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073011-02.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF948110F3, 0x0, 0xFFFFFFFFAF92C5D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sat 7/30/2011 2:51:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073011-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF940330F3, 0x0, 0xFFFFFFFFAFC325D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sun 7/24/2011 12:42:49 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-04.dmp
This was probably caused by the following module: mbr.sys (mbr+0xA28)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE1707000, 0xFF, 0x0, 0xFFFFFFFFBA478A28)
Error: CUSTOM_ERROR
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: mbr.sys .
Google query: mbr.sys CUSTOM_ERROR
On Sun 7/24/2011 12:08:51 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-03.dmp
This was probably caused by the following module: catchme.sys (catchme+0x2FB6)
Bugcheck code: 0xC9 (0x20E, 0xFFFFFFFFB3E47FB6, 0xFFFFFFFF9EA0EF48, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
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: catchme.sys .
Google query: catchme.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Sat 7/23/2011 6:35:35 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-02.dmp
This was probably caused by the following module: 55340009.sys (55340009+0x29C7)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFFFFB0E33560)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. 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: 55340009.sys .
Google query: 55340009.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Sat 7/23/2011 2:06:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-01.dmp
This was probably caused by the following module: 25047961.sys (25047961+0x29C7)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFFFFB1E4E560)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. 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: 25047961.sys .
Google query: 25047961.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Fri 7/22/2011 12:53:18 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072111-02.dmp
This was probably caused by the following module: aswmbr.sys (aswMBR+0x3B10)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE28FA000, 0xFF, 0x0, 0xFFFFFFFFB33ADB10)
Error: CUSTOM_ERROR
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: aswmbr.sys .
Google query: aswmbr.sys CUSTOM_ERROR
On Fri 7/22/2011 12:41:55 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072111-01.dmp
This was probably caused by the following module: aswmbr.sys (aswMBR+0x3B10)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE2C2F000, 0xFF, 0x0, 0xFFFFFFFFB0A12B10)
Error: CUSTOM_ERROR
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: aswmbr.sys .
Google query: aswmbr.sys CUSTOM_ERROR
On Sat 3/28/2009 11:59:32 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032809-01.dmp
This was probably caused by the following module: atwpkt2.sys (ATWPKT2+0xBB7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805B57EC, 0xFFFFFFFFAA0D9928, 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: atwpkt2.sys .
Google query: atwpkt2.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 3/17/2007 12:54:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031707-01.dmp
This was probably caused by the following module: hsfhwich.sys (HSFHWICH+0x1786C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x12F, 0xFFFFFFFFA98CBC7C, 0xFFFFFFFFA98CB978)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\hsfhwich.sys
product: SoftK56 Modem Driver
company: Conexant Systems, Inc.
description: HSFHWICH WDM 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: hsfhwich.sys (HSFHWICH WDM driver, Conexant Systems, Inc.).
Google query: hsfhwich.sys Conexant Systems, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
16 crash dumps have been found and analyzed. Only 15 are included in this report. 8 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:
hsfhwich.sys (HSFHWICH WDM driver, Conexant Systems, Inc.)
ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation)
atwpkt2.sys
aswmbr.sys
25047961.sys
mbr.sys
catchme.sys
55340009.sys
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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: SUZY
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Celeron® M processor 1.40GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1333129216 total
VM: 2147352576, free: 2041860096
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 8/18/2011 10:34:26 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081811-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF93D3D0F3, 0x0, 0xFFFFFFFFB28995D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Thu 8/4/2011 10:23:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080411-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF93C770F3, 0x0, 0xFFFFFFFFB79225D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Tue 8/2/2011 3:17:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080111-02.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF955AF0F3, 0x0, 0xFFFFFFFFB02205D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Tue 8/2/2011 3:06:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080111-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF9252B0F3, 0x0, 0xFFFFFFFFB070D5D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Mon 8/1/2011 2:42:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073111-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF941330F3, 0x0, 0xFFFFFFFFB09D75D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sat 7/30/2011 2:55:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073011-02.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF948110F3, 0x0, 0xFFFFFFFFAF92C5D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sat 7/30/2011 2:51:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini073011-01.dmp
This was probably caused by the following module: ialmnt5.sys (ialmnt5+0x4E5D6)
Bugcheck code: 0x100000D6 (0xFFFFFFFF940330F3, 0x0, 0xFFFFFFFFAFC325D6, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
file path: C:\WINDOWS\system32\drivers\ialmnt5.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver
Bug check description: A page fault was hit beyond the end of an allocation.
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: ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation).
Google query: ialmnt5.sys Intel Corporation DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
On Sun 7/24/2011 12:42:49 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-04.dmp
This was probably caused by the following module: mbr.sys (mbr+0xA28)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE1707000, 0xFF, 0x0, 0xFFFFFFFFBA478A28)
Error: CUSTOM_ERROR
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: mbr.sys .
Google query: mbr.sys CUSTOM_ERROR
On Sun 7/24/2011 12:08:51 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-03.dmp
This was probably caused by the following module: catchme.sys (catchme+0x2FB6)
Bugcheck code: 0xC9 (0x20E, 0xFFFFFFFFB3E47FB6, 0xFFFFFFFF9EA0EF48, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
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: catchme.sys .
Google query: catchme.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Sat 7/23/2011 6:35:35 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-02.dmp
This was probably caused by the following module: 55340009.sys (55340009+0x29C7)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFFFFB0E33560)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. 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: 55340009.sys .
Google query: 55340009.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Sat 7/23/2011 2:06:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072311-01.dmp
This was probably caused by the following module: 25047961.sys (25047961+0x29C7)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFFFFB1E4E560)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. 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: 25047961.sys .
Google query: 25047961.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Fri 7/22/2011 12:53:18 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072111-02.dmp
This was probably caused by the following module: aswmbr.sys (aswMBR+0x3B10)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE28FA000, 0xFF, 0x0, 0xFFFFFFFFB33ADB10)
Error: CUSTOM_ERROR
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: aswmbr.sys .
Google query: aswmbr.sys CUSTOM_ERROR
On Fri 7/22/2011 12:41:55 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072111-01.dmp
This was probably caused by the following module: aswmbr.sys (aswMBR+0x3B10)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE2C2F000, 0xFF, 0x0, 0xFFFFFFFFB0A12B10)
Error: CUSTOM_ERROR
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: aswmbr.sys .
Google query: aswmbr.sys CUSTOM_ERROR
On Sat 3/28/2009 11:59:32 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032809-01.dmp
This was probably caused by the following module: atwpkt2.sys (ATWPKT2+0xBB7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805B57EC, 0xFFFFFFFFAA0D9928, 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: atwpkt2.sys .
Google query: atwpkt2.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 3/17/2007 12:54:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031707-01.dmp
This was probably caused by the following module: hsfhwich.sys (HSFHWICH+0x1786C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x12F, 0xFFFFFFFFA98CBC7C, 0xFFFFFFFFA98CB978)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\hsfhwich.sys
product: SoftK56 Modem Driver
company: Conexant Systems, Inc.
description: HSFHWICH WDM 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: hsfhwich.sys (HSFHWICH WDM driver, Conexant Systems, Inc.).
Google query: hsfhwich.sys Conexant Systems, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
16 crash dumps have been found and analyzed. Only 15 are included in this report. 8 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:
hsfhwich.sys (HSFHWICH WDM driver, Conexant Systems, Inc.)
ialmnt5.sys (Intel Graphics Miniport Driver, Intel Corporation)
atwpkt2.sys
aswmbr.sys
25047961.sys
mbr.sys
catchme.sys
55340009.sys
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.
#27
Posted 18 August 2011 - 09:59 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
OK something I see is looking like you may be fighting a infection. I'm going to ask one of our malware techs to come in and look at this last log and let us know how to proceed.
#28
Posted 19 August 2011 - 05:45 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Lets see what you have in your startup services area
Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
#29
Posted 19 August 2011 - 06:58 AM
Jason77
- Topic Starter
-
- Member
-
- 17 posts
Member
I have tried this before in the past but will try it again this afternoon. (msconfig remove startup items)
Also here is a link to all the malware removal I have been through.
http://forums.spybot...ead.php?t=63371
Also here is a link to all the malware removal I have been through.
http://forums.spybot...ead.php?t=63371
Edited by Jason77, 19 August 2011 - 06:59 AM.
#30
Posted 19 August 2011 - 07:21 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
If you did the msconfig startups then that is different then the Services I am asking you to do now.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
