Svar till Toffe [
Gå till post]:
Nu då? :$ Googla? :D
Visa spoiler
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:WINDOWSMinidump
Crash dumps are enabled on your computer.
On Mon 2011-10-24 13:54:17 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-10.dmp
This was probably caused by the following module: viahduaa.sys (viahduaa+0x280D8)
Bugcheck code: 0x100000D1 (0xFFFFFFFFAF126000, 0x2, 0x0, 0xFFFFFFFFB1E540D8)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32driversviahduaa.sys
product: VIA High Definition Audio Driver
company: VIA Technologies, Inc.
description: VIA High Definition Audio Function Driver
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: viahduaa.sys (VIA High Definition Audio Function Driver, VIA Technologies, Inc.).
Google query: viahduaa.sys VIA Technologies, Inc. CUSTOM_ERROR
On Mon 2011-10-24 11:24:29 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-09.dmp
This was probably caused by the following module: viahduaa.sys (viahduaa+0x280D8)
Bugcheck code: 0x100000D1 (0xFFFFFFFFAE556000, 0x2, 0x0, 0xFFFFFFFFB2A6E0D8)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32driversviahduaa.sys
product: VIA High Definition Audio Driver
company: VIA Technologies, Inc.
description: VIA High Definition Audio Function Driver
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: viahduaa.sys (VIA High Definition Audio Function Driver, VIA Technologies, Inc.).
Google query: viahduaa.sys VIA Technologies, Inc. CUSTOM_ERROR
On Mon 2011-10-24 09:54:13 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-08.dmp
This was probably caused by the following module: viahduaa.sys (viahduaa+0x280D8)
Bugcheck code: 0x100000D1 (0xFFFFFFFFAF2F8000, 0x2, 0x0, 0xFFFFFFFFB27230D8)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32driversviahduaa.sys
product: VIA High Definition Audio Driver
company: VIA Technologies, Inc.
description: VIA High Definition Audio Function Driver
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: viahduaa.sys (VIA High Definition Audio Function Driver, VIA Technologies, Inc.).
Google query: viahduaa.sys VIA Technologies, Inc. CUSTOM_ERROR
On Sun 2011-10-23 23:26:31 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-07.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB1581050, 0xFFFFFFFFB1580D4C, 0xFFFFFFFF804EFAC0)
Error: NTFS_FILE_SYSTEM
file path: C:WINDOWSsystem32drivers
tfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Sun 2011-10-23 23:17:33 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-06.dmp
This was probably caused by the following module: win32k.sys (win32k+0x285D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80285D, 0xFFFFFFFFB265EC2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:WINDOWSsystem32win32k.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 which cannot be identified at this time.
On Sun 2011-10-23 22:56:25 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x200000, 0xFFFFFFFFE1066468)
Error: BAD_POOL_CALLER
file path: C:WINDOWSsystem32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
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 which cannot be identified at this time.
On Sun 2011-10-23 22:49:43 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE35)
Bugcheck code: 0x1000000A (0x10, 0x1C, 0x1, 0xFFFFFFFF804FA17E)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32drivers
tfs.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 which cannot be identified at this time.
On Sun 2011-10-23 22:46:28 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8A1F1DA0, 0xFFFFFFFF8A1F1F14, 0xFFFFFFFF805D29E4)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:WINDOWSsystem32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
On Sun 2011-10-23 22:36:03 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C963)
Bugcheck code: 0x100000BE (0xFFFFFFFF805028C5, 0x502121, 0xFFFFFFFFAF461C4C, 0xA)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32
toskrnl.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 which cannot be identified at this time.
On Sun 2011-10-23 22:33:48 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C963)
Bugcheck code: 0x1000000A (0x20C, 0x1C, 0x1, 0xFFFFFFFF80503963)
Error: CUSTOM_ERROR
file path: C:WINDOWSsystem32
toskrnl.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 which cannot be identified at this time.
On Sat 2011-10-22 07:35:14 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102211-03.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1DB0EC)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFB8450925, 0xFFFFFFFFB006E2F8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:WINDOWSsystem32
v4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.38
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.38
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.38 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 2011-10-22 06:57:59 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102211-02.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x8CD31)
Bugcheck code: 0x100000EA (0xFFFFFFFF8A37D500, 0xFFFFFFFF8A45AAB0, 0xFFFFFFFFB84E7CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32
v4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.38
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.38
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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.38 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER_M
On Sat 2011-10-22 06:52:44 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102211-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1DB0EC)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFB8460925, 0xFFFFFFFFB26432F8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:WINDOWSsystem32
v4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.38
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.38
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.38 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 2011-10-21 10:15:58 GMT your computer crashed
crash dump file: C:WINDOWSMinidumpMini102111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x489FE)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:WINDOWSsystem32
toskrnl.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 which cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nv4_disp.dll (NVIDIA Windows XP Display driver, Version 285.38 , NVIDIA Corporation)
viahduaa.sys (VIA High Definition Audio Function Driver, VIA Technologies, Inc.)
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.
