hi thanks for the quick reply.
1. system manufacturer: micro-star international co., ltd
system model: MS-7529
2. Intel (R) G33/G31 express chipset family possibly incorporated in the motherboard.
3. updated video driver with Intel (R) G33/G31 express chipset family successfully.
i have not tried the other options yet.
System Information (local)
Computer name: MICHELLE-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7529, MICRO-STAR INTERNATIONAL CO.,LTD, G31TM-P35 (MS-7529)
CPU: GenuineIntel Genuine Intel(R) CPU 2140 @ 1.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3479429120 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 30/11/2015 04:33:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113015-17406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38AF1)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801C7000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 30/11/2015 04:33:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!Kei386EoiHelper+0x17D4)
Bugcheck code: 0x7F (0x8, 0xFFFFFFFF801C7000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/11/2015 14:03:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112615-14953-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2AB7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82C92C1D, 0xFFFFFFFF80DE3E04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Thu 26/11/2015 01:14:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112615-15375-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0xC888)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82C9CC1D, 0xFFFFFFFF80DDFA74, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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 Wed 25/11/2015 14:11:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112515-14609-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0xF8A8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82CAAC1D, 0xFFFFFFFF977FBBE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode 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.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 24/11/2015 23:11:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112415-16750-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1813)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82CAFC1D, 0xFFFFFFFF80DDFB2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 24/11/2015 14:14:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112415-17546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD31E0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFFFF821CA880, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/11/2015 14:10:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112415-14578-01.dmp
This was probably caused by the following module: i8042prt.sys (i8042prt+0x3F97)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82CA4C1D, 0xFFFFFFFF97F0BC14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\i8042prt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: i8042 Port 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 Mon 23/11/2015 23:21:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112315-14937-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1F645)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C3D4645, 0xFFFFFFFF80E1D778, 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 23/11/2015 23:07:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112315-13812-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1F63C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C45063C, 0xFFFFFFFF912C46BC, 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.
Conclusion
50 crash dumps have been found and analyzed. Only 10 are included in this report. 4 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:
igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
tffsmon.sys
pctcore.sys
avipbb.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.