BSOD Problem

#1
Hello,

I have a dump file attached. Could someone please look at this.

Thanks,


Nevica View attachment 14326
 


Trouble

Noob Whisperer
#2
While not conclusive the single dump file that you have posted would seem to point at Abyssus.sys 10/29/2009 which would seem to be a driver for a specific USB optical mouse. You should try updating that driver and see if blue screens persist.
Code:
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image [COLOR=#b22222]Abyssus.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#b22222]Abyssus.sys
[/COLOR]*** ERROR: Module load completed but symbols could not be loaded for Abyssus.sys
Probably caused by : [COLOR=#b22222]Abyssus.sys[/COLOR] ( Abyssus+6af )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+3231323165653330
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800030796be to fffff80003081cd0
STACK_TEXT: 
fffff800`00b9bb48 fffff800`030796be : fffffa80`093325b0 fffff880`0f4943c8 fffff800`00b9c350 fffff800`030ad890 : nt!KeBugCheck
fffff800`00b9bb50 fffff800`030ad55d : fffff800`03288968 fffff800`031c5cbc fffff800`03002000 fffff800`00b9c2b0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bb80 fffff800`030ac335 : fffff800`031c90fc fffff800`00b9bbf8 fffff800`00b9c2b0 fffff800`03002000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bbb0 fffff800`030af632 : fffff800`00b9c2b0 fffff800`00b9c350 fffffa80`00000001 fffff880`00000005 : nt!RtlDispatchException+0x415
fffff800`00b9c290 fffff800`0303c6ea : 00000000`00000000 fffffa80`08751a18 fffffa80`087511a0 fffff880`04072783 : nt!RtlRaiseStatus+0x4e
fffff800`00b9c830 fffff880`05b5d6af : fffffa80`087ae800 fffffa80`00000000 fffffa80`094c9701 fffffa80`08ed0c00 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff800`00b9c8b0 fffffa80`087ae800 : fffffa80`00000000 fffffa80`094c9701 fffffa80`08ed0c00 fffffa80`09f0d010 : [COLOR=#b22222]Abyssus[/COLOR]+0x6af
fffff800`00b9c8b8 fffffa80`00000000 : fffffa80`094c9701 fffffa80`08ed0c00 fffffa80`09f0d010 00000000`00000000 : 0xfffffa80`087ae800
fffff800`00b9c8c0 fffffa80`094c9701 : fffffa80`08ed0c00 fffffa80`09f0d010 00000000`00000000 fffffa80`09456400 : 0xfffffa80`00000000
fffff800`00b9c8c8 fffffa80`08ed0c00 : fffffa80`09f0d010 00000000`00000000 fffffa80`09456400 fffffa80`094c9760 : 0xfffffa80`094c9701
fffff800`00b9c8d0 fffffa80`09f0d010 : 00000000`00000000 fffffa80`09456400 fffffa80`094c9760 fffffa80`087ae8c0 : 0xfffffa80`08ed0c00
fffff800`00b9c8d8 00000000`00000000 : fffffa80`09456400 fffffa80`094c9760 fffffa80`087ae8c0 fffff800`03085091 : 0xfffffa80`09f0d010

STACK_COMMAND: kb
FOLLOWUP_IP: 
[COLOR=#b22222]Abyssus[/COLOR]+6af
fffff880`05b5d6af ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: [COLOR=#b22222]Abyssus[/COLOR]+6af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: [COLOR=#b22222]Abyssus[/COLOR]
IMAGE_NAME: [COLOR=#b22222]Abyssus.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP: 4aea553c
FAILURE_BUCKET_ID: X64_0x1E_0_[COLOR=#b22222]Abyssus[/COLOR]+6af
BUCKET_ID: X64_0x1E_0_[COLOR=#b22222]Abyssus[/COLOR]+6af
Followup: MachineOwner
 


#3
Hello,

I tried running the SF Diagnostic Tool but it crashed when:

System.IO.FileNotFoundException: Could not find file ' C:\msinfo32.nfo'.

I have uploaded what I can run. ie the text file.

Nevica
 


Trouble

Noob Whisperer
#4
you need to right click the SF Diagnostic Tool and choose run as administrator from the context menu. And update the driver I mentioned above.
 


#5
OK, extra files are uploaded.

Nevica
 


#6
Hi There,

I think by re-installing Abyssus software it has solved the problem............................ So-far.................

Thanks,

Nevica
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top