Sign in with
Sign up | Sign in
Your question

Blue screens whle playing minecraft.

November 17, 2012 8:17:52 PM

i used WhoCrashed to show the crash dumps------------------------------------------------------------------------------------------------------



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: MINECRAFT
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) M processor 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 2146746368 total
VM: 2147352576, free: 2046115840




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 11/17/2012 8:22:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111712-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x5233)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF805233, 0xFFFFFFFFB1E127B4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_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 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 Sat 11/17/2012 5:29:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111712-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x9AA96)
Bugcheck code: 0x10000050 (0xFFFFFFFFAD020304, 0x0, 0xFFFFFFFFBD0ACA96, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.58
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.58
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 285.58 , NVIDIA Corporation).
Google query: NVIDIA Corporation CUSTOM_ERROR



On Sat 11/17/2012 12:24:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111612-01.dmp
This was probably caused by the following module: rtkhdaud.sys (RtkHDAud+0x39271)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\rtkhdaud.sys
product: Realtek(r) High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function 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.
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: rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: Realtek Semiconductor Corp. UNEXPECTED_KERNEL_MODE_TRAP_M



On Fri 11/16/2012 4:04:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111512-01.dmp
This was probably caused by the following module: mrxsmb.sys (mrxsmb+0x981)
Bugcheck code: 0x100000D1 (0x330063, 0x2, 0x0, 0xFFFFFFFFB3FAE981)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\mrxsmb.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows NT SMB Minirdr
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 11/11/2012 2:13:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111012-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1746)
Bugcheck code: 0x1000000A (0xFFFFFFFFF000EEF3, 0x2, 0x1, 0xFFFFFFFF80500D38)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 11/10/2012 9:18:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111012-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x29D2C)
Bugcheck code: 0x1000000A (0x479A929F, 0x2, 0x1, 0xFFFFFFFF80500D2C)
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 11/10/2012 6:53:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111012-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x42799)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFB3EEF799, 0xFFFFFFFFB2E43CA4, 0xFFFFFFFFB2E439A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 11/4/2012 9:17:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110412-01.dmp
This was probably caused by the following module: portcls.sys (portcls+0x1807)
Bugcheck code: 0x100000D1 (0x1000000, 0x2, 0x0, 0xFFFFFFFFB4395807)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
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 11/3/2012 10:19:38 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110312-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x549E)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x0, 0xFFFFFFFF80500CF3)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 9/10/2012 11:29:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091112-01.dmp
This was probably caused by the following module: Unknown (0x00000001)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x1, 0xFFFFFFFFB010EB38, 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.
Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Wed 8/29/2012 10:22:24 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082912-03.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x71C3)
Bugcheck code: 0xFC (0xFFFFFFFFAF81F068, 0x3F95D163, 0xFFFFFFFFAF81EF78, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: AVAST Software ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



On Wed 8/29/2012 10:16:24 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082912-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2995C)
Bugcheck code: 0x1000000A (0x128, 0x2, 0x1, 0xFFFFFFFF8050095C)
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 Wed 8/29/2012 8:07:00 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082912-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x5C0F)
Bugcheck code: 0xFC (0xFFFFFFFFAFEE5714, 0x7DEC4163, 0xFFFFFFFFAFEE5624, 0x1)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: AVAST Software ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



On Sat 8/25/2012 1:44:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x29CEC)
Bugcheck code: 0x1000000A (0xFFFFFFFFED0C3963, 0x2, 0x1, 0xFFFFFFFF80500CEC)
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 Fri 8/24/2012 3:48:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082412-03.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x131FD0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBD143FD0, 0xFFFFFFFFAF441A3C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.58
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.58
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 285.58 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




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

20 crash dumps have been found and analyzed. Only 15 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:

aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
nv4_disp.dll (NVIDIA Windows XP Display driver, Version 285.58 , NVIDIA Corporation)
aswsp.sys (avast! self protection module, AVAST Software)
rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)

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