I have attached a dump of the errors, please help me resolve this issue.
Attached Files
-
130317_031737.zip 299.12KB
182 downloads
IRQL Driver NOT LESS or EQUAL
Started by
bsod187
, Mar 16 2013 09:19 PM
#1
Posted 16 March 2013 - 09:19 PM
bsod187
-
- Member
-
- 22 posts
Member
I have attached a dump of the errors, please help me resolve this issue.
#2
Posted 16 March 2013 - 10:39 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Welcome to GTG and I will try to assist you with your issue.
First I will need some information from you.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
http://www.resplendence.com/downloads
Download Autoruns from the link in my signature below:
1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the "Autoruns.exe".
3: Click on the "Everything" tab
4: Click the Options at the top of the Window. In the new little window click the box that states Hide Microsoft Services
5: Go to File then to Export As or Save in some versions.
6: Save the file as AutoRuns.txt file instead of the default .arn to a known location like your Desktop.
7: Attach to your next reply.
8: DO NOT do anything till we have had a chance to study the log and reply with suggestions as to what to remove.
Then I need you to do the following and let me know the results.
A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.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+-4.20.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.
First I will need some information from you.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
http://www.resplendence.com/downloads
Download Autoruns from the link in my signature below:
1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the "Autoruns.exe".
3: Click on the "Everything" tab
4: Click the Options at the top of the Window. In the new little window click the box that states Hide Microsoft Services
5: Go to File then to Export As or Save in some versions.
6: Save the file as AutoRuns.txt file instead of the default .arn to a known location like your Desktop.
7: Attach to your next reply.
8: DO NOT do anything till we have had a chance to study the log and reply with suggestions as to what to remove.
Then I need you to do the following and let me know the results.
A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.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+-4.20.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.
#3
Posted 19 March 2013 - 09:19 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
Thank you in advance for your help, I have attached the autorun output as a .txt file and below is the whocrashed results:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 3/20/2013 2:54:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031913-02.dmp
This was probably caused by the following module: luafv.sys (luafv+0xB3E3)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820280D6, 0xFFFFFFFF9955FAE8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 3/19/2013 9:35:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x271AF9)
Bugcheck code: 0x10000050 (0xFFFFFFFF9C476014, 0x0, 0xFFFFFFFF82271AF9, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 3/19/2013 5:20:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031813-02.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9B4B23E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/18/2013 1:09:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031813-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9AFD33E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 3/17/2013 6:02:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031713-01.dmp
This was probably caused by the following module: unknown_module_89fa9000.sys (Unknown_Module_89fa9000+0x5053)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF89FAE053, 0xFFFFFFFF9D538A3C, 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: unknown_module_89fa9000.sys .
Google query: unknown_module_89fa9000.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3/17/2013 3:09:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-04.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5FEBC)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x1, 0xFFFFFFFF8ECB7EBC)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.
On Sat 3/16/2013 6:11:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB1423)
Bugcheck code: 0x1000000A (0xFFFFFFFFA08D8004, 0x2, 0x1, 0xFFFFFFFF820B1423)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/16/2013 5:51:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA9C92)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x8, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/16/2013 5:41:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91B0)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A91B0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/9/2013 7:03:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030913-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA92C2)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/9/2013 5:07:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91A4)
Bugcheck code: 0x1000000A (0xF60068, 0x1B, 0x1, 0xFFFFFFFF820A91A4)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3/4/2013 3:22:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-03.dmp
This was probably caused by the following module: unknown_module_82000000 (nt+0xA92C2)
Bugcheck code: 0x1000000A (0x1, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
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: unknown_module_82000000 .
Google query: unknown_module_82000000 CUSTOM_ERROR
On Sun 3/3/2013 7:42:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91AB)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x0, 0xFFFFFFFF820A91AB)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/3/2013 5:56:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x672A)
Bugcheck code: 0x100000D1 (0xE701, 0x2, 0x1, 0xFFFFFFFF89DCD72A)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 that cannot be identified at this time.
On Sun 3/3/2013 4:04:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030213-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF4820)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820F4820)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
unknown_module_82000000
unknown_module_89fa9000.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.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 3/20/2013 2:54:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031913-02.dmp
This was probably caused by the following module: luafv.sys (luafv+0xB3E3)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820280D6, 0xFFFFFFFF9955FAE8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 3/19/2013 9:35:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x271AF9)
Bugcheck code: 0x10000050 (0xFFFFFFFF9C476014, 0x0, 0xFFFFFFFF82271AF9, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 3/19/2013 5:20:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031813-02.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9B4B23E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/18/2013 1:09:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031813-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4F10)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820765A4, 0xFFFFFFFF9AFD33E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 3/17/2013 6:02:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031713-01.dmp
This was probably caused by the following module: unknown_module_89fa9000.sys (Unknown_Module_89fa9000+0x5053)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF89FAE053, 0xFFFFFFFF9D538A3C, 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: unknown_module_89fa9000.sys .
Google query: unknown_module_89fa9000.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3/17/2013 3:09:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-04.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5FEBC)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x1, 0xFFFFFFFF8ECB7EBC)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.
On Sat 3/16/2013 6:11:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB1423)
Bugcheck code: 0x1000000A (0xFFFFFFFFA08D8004, 0x2, 0x1, 0xFFFFFFFF820B1423)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/16/2013 5:51:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA9C92)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x8, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/16/2013 5:41:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini031613-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91B0)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A91B0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/9/2013 7:03:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030913-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA92C2)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 3/9/2013 5:07:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91A4)
Bugcheck code: 0x1000000A (0xF60068, 0x1B, 0x1, 0xFFFFFFFF820A91A4)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 3/4/2013 3:22:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-03.dmp
This was probably caused by the following module: unknown_module_82000000 (nt+0xA92C2)
Bugcheck code: 0x1000000A (0x1, 0x1B, 0x1, 0xFFFFFFFF820A92C2)
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: unknown_module_82000000 .
Google query: unknown_module_82000000 CUSTOM_ERROR
On Sun 3/3/2013 7:42:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA91AB)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x0, 0xFFFFFFFF820A91AB)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/3/2013 5:56:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030313-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x672A)
Bugcheck code: 0x100000D1 (0xE701, 0x2, 0x1, 0xFFFFFFFF89DCD72A)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 that cannot be identified at this time.
On Sun 3/3/2013 4:04:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030213-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF4820)
Bugcheck code: 0x1000000A (0x0, 0x1B, 0x1, 0xFFFFFFFF820F4820)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
unknown_module_82000000
unknown_module_89fa9000.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.
#4
Posted 20 March 2013 - 06:24 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
No autorun.txt attachment and from the look of the WhoCrashed log it looks to be a internal Windows issue.
SFC /Scannow Win7
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
SFC /Scannow Win7
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
#5
Posted 20 March 2013 - 08:00 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
I attached the autorun.txt file , when I ran sfc /scannow my computer crashed half way through with the dump below.
I then rebooted and ran sfc/scannow multiple times and got the following errors: “Windows Resource Protection found corrupt files but was unable to fix some of them”, attached is the sfcdetails.txt
On Thu 3/21/2013 12:17:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F89D)
Bugcheck code: 0x10000050 (0xFFFFFFFF90F6A864, 0x0, 0xFFFFFFFF8203F89D, 0x2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identifie
I then rebooted and ran sfc/scannow multiple times and got the following errors: “Windows Resource Protection found corrupt files but was unable to fix some of them”, attached is the sfcdetails.txt
On Thu 3/21/2013 12:17:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F89D)
Bugcheck code: 0x10000050 (0xFFFFFFFF90F6A864, 0x0, 0xFFFFFFFF8203F89D, 0x2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identifie
Attached Files
-
AutoRuns-3.19.2013.txt 34.51KB
173 downloads
-
sfcdetails.txt 121.95KB
174 downloads
#6
Posted 20 March 2013 - 08:53 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Hopefully this might be the issue.
Open Autoruns, click on "Logon" tab, and UN-check:
+ "rdpclip"
When done restart computer and then:
Download TFC by OldTimer to your desktop
Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:
It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged
Please do not run any other Auslogics programs other then this one as they may cause unwanted results.
Open Autoruns, click on "Logon" tab, and UN-check:
+ "rdpclip"
When done restart computer and then:
Download TFC by OldTimer to your desktop
- Please double-click TFC.exe to run it. (Note: If you are running on Vista, right-click on the file and choose Run As Administrator).
- It will close all programs when run, so make sure you have saved all your work before you begin.
- Click the Start button to begin the process. Depending on how often you clean temp files, execution time should be anywhere from a few seconds to a minute or two. Let it run uninterrupted to completion.
- Once it's finished it should reboot your machine. If it does not, please manually reboot the machine yourself to ensure a complete clean.
Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:
It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged
Please do not run any other Auslogics programs other then this one as they may cause unwanted results.
#7
Posted 21 March 2013 - 09:26 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
I followed the steps in the previous post and still getting errors, here is the latest:
On Fri 3/22/2013 1:04:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-02.dmp
This was probably caused by the following module: ecache.sys (ecache+0xB9D1)
Bugcheck code: 0x100000C5 (0x7249534E, 0x2, 0x1, 0xFFFFFFFF820E88D9)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 that cannot be identified at this time.
On Fri 3/22/2013 1:02:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3E89)
Bugcheck code: 0x1000000A (0xA0004, 0x2, 0x1, 0xFFFFFFFF823A4E89)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 that cannot be identified at this time.
On Fri 3/22/2013 1:04:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-02.dmp
This was probably caused by the following module: ecache.sys (ecache+0xB9D1)
Bugcheck code: 0x100000C5 (0x7249534E, 0x2, 0x1, 0xFFFFFFFF820E88D9)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 that cannot be identified at this time.
On Fri 3/22/2013 1:02:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3E89)
Bugcheck code: 0x1000000A (0xA0004, 0x2, 0x1, 0xFFFFFFFF823A4E89)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 that cannot be identified at this time.
#8
Posted 21 March 2013 - 10:28 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
OK we need to look at your startups to see if something there is causing it.
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
#9
Posted 22 March 2013 - 12:39 AM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
After unchecking all start ups I got the following crash:
On Fri 3/22/2013 6:36:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-04.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x165D64)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF958E298C, 0xFFFFFFFF8EE9DB18, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 187.80
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 187.80
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 187.80 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 3/22/2013 6:36:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032113-04.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x165D64)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF958E298C, 0xFFFFFFFF8EE9DB18, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 187.80
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 187.80
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 187.80 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
#10
Posted 22 March 2013 - 07:40 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
nvlddmkm.sys is the Nvidia driver most likely video driver. Try updating it and see if that corrects that issue.
#11
Posted 22 March 2013 - 12:31 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
I updated the NVIDIA driver and got the following crash:
On Fri 3/22/2013 6:25:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032213-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB38A3)
Bugcheck code: 0x1000000A (0x1, 0x1B, 0x1, 0xFFFFFFFF820B38A3)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I also got this today for the first time:
Host Process for Windows Services has been stopped:
Problem signature:
Problem Event Name: APPCRASH
Application Name: svchost.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549adc4
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c00000fd
Exception Offset: 000447f2
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311
Read our privacy statement:
http://go.microsoft....63&clcid=0x0409
On Fri 3/22/2013 6:25:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032213-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB38A3)
Bugcheck code: 0x1000000A (0x1, 0x1B, 0x1, 0xFFFFFFFF820B38A3)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I also got this today for the first time:
Host Process for Windows Services has been stopped:
Problem signature:
Problem Event Name: APPCRASH
Application Name: svchost.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549adc4
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c00000fd
Exception Offset: 000447f2
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311
Read our privacy statement:
http://go.microsoft....63&clcid=0x0409
Edited by bsod187, 22 March 2013 - 12:54 PM.
#12
Posted 22 March 2013 - 03:13 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
OK lets take a deeper look into the system and see what pops up.
Please Run the PCPitstop.com OverDrive Full Tests
Here's how:
You must use your 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 your 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
#13
Posted 23 March 2013 - 11:14 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
I ran the PCpitstop program, how do I post the test results, It did not generate a URL?
#14
Posted 24 March 2013 - 06:13 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
The results page it produced is what you Copy and paste it.
#15
Posted 24 March 2013 - 09:49 PM
bsod187
- Topic Starter
-
- Member
-
- 22 posts
Member
I attached a the summary results as a picture.
I am starting to get the BSOD more frequently to the point where the computer is becoming unusable, here are the latest crashes:
On Mon 3/25/2013 3:45:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9C095)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF8203BB5E)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 that cannot be identified at this time.
On Mon 3/25/2013 3:42:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE3D03)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/25/2013 3:39:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-02.dmp
This was probably caused by the following module: ataport.sys (ataport+0x8F39)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/25/2013 3:33:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11F9)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF8627ED08, 0x63706458, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 that cannot be identified at this time.
I am starting to get the BSOD more frequently to the point where the computer is becoming unusable, here are the latest crashes:
On Mon 3/25/2013 3:45:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9C095)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF8203BB5E)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 that cannot be identified at this time.
On Mon 3/25/2013 3:42:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE3D03)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/25/2013 3:39:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-02.dmp
This was probably caused by the following module: ataport.sys (ataport+0x8F39)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 3/25/2013 3:33:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini032413-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11F9)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF8627ED08, 0x63706458, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 that cannot be identified at this time.
Attached Thumbnails
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
