Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

problem BSOD


  • Please log in to reply

#1
mladolino

mladolino

    New Member

  • Member
  • Pip
  • 1 posts
hi all i have problem with my acer travelmate 2430 with BSOD please help me
thanx in advice
mladjo

here is my who crashed C/P report
System Information (local)
--------------------------------------------------------------------------------

computer name: JERKOVIC
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Celeron® M processor 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1540866048 total
VM: 2147352576, free: 2049323008




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 5.2.2013 20:36:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020513-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x682B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80682B, 0xFFFFFFFFB61D0514, 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 Tue 5.2.2013 18:25:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020513-01.dmp
This was probably caused by the following module: sisgrv.dll (SiSGRV+0x1AA1AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFDC5AC5C0, 0x1, 0xFFFFFFFFBF1BC1AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\sisgrv.dll
product: SiS ® Compatible Super VGA Dispaly Driver for Windows XP
company: Silicon Integrated Systems Corporation
description: SiS Compatible Super VGA 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: sisgrv.dll (SiS Compatible Super VGA Driver, Silicon Integrated Systems Corporation).
Google query: Silicon Integrated Systems Corporation CUSTOM_ERROR



On Sat 2.2.2013 21:04:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020213-01.dmp
This was probably caused by the following module: kmixer.sys (kmixer+0x133D5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFB1109C08, 0xFFFFFFFFB1109904)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
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.
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.
Google query: Microsoft Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 1.2.2013 21:18:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020113-03.dmp
This was probably caused by the following module: sisgrv.dll (SiSGRV+0x1AA1AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFD720A5C0, 0x1, 0xFFFFFFFFBF1BC1AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\sisgrv.dll
product: SiS ® Compatible Super VGA Dispaly Driver for Windows XP
company: Silicon Integrated Systems Corporation
description: SiS Compatible Super VGA 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: sisgrv.dll (SiS Compatible Super VGA Driver, Silicon Integrated Systems Corporation).
Google query: Silicon Integrated Systems Corporation CUSTOM_ERROR



On Fri 1.2.2013 18:26:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020113-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2309)
Bugcheck code: 0x10000050 (0xFFFFFFFFF4000000, 0x1, 0xFFFFFFFFBF802309, 0x2)
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 Fri 1.2.2013 15:28:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020113-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD820)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80D820, 0xFFFFFFFFBA187BC8, 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

Edited by mladolino, 06 February 2013 - 03:55 AM.

  • 0

Advertisements


#2
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,019 posts
:welcome: mladolino

Couple of questions if I may;

Had you made any software or hardware changes just before this happened.

Does the computer ever boot up successfully at present.

Have you tried booting into safe mode or last known good configuration.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP