XP pro BSOD errors please help!!!!

Status
Not open for further replies.

Hendryy

Posts: 6   +0
It hapens during play,few days ago it also hapend during normal work on my pc.
Comp. just reboot itself and brings out a windows error report saying:
"Windows has recovered from a serious error"
The error report sends me on McSoft page witch tells me that it is a problem with a driver, but I can not find any clue to identify it, neither some documentation about that problem.
I done some things you said on the sticky posts!!!
Cleaned my system physical,checked with memtest,no errors,checked the disk also ok!!!
Recently I bought a new PSU.
Speedfan monitor showes:+3.3V- 3.36V,+5V- 5.00V,+12V- 11.43V dont know is this enough power on rails for my system????


This is the last chrash from today:
Category:(102)
Event ID: 1003
File name:faultrep.dll
File Version:5.1.2600.2180
Source:System Error

Error code: STOP:0x0000008e(0x0000001d,0x804e3908,0xa82a7c70,0x00000000)

Here is the last two minidumps files!!!
 
These minidumps both point to a i8024prt.sys mouse port system file being the cause. Does this bring anything to mind?
 
Hmm!!!!
Really I dont know,now Im having my new logitech MX-1000,didnt install any drivers,but the BSOD also happened before with my old mouse.
This mouse port system file on what is the problem exact relating,my corrupt xp-windows system files or a driver??????
Im not a big expert so I cant understand your pointing to a problem so good!!!

What should I try???

I put 3 more minidump files maybe that helps better!!!!
 
c000001d is the NT Status code and it stands for illegal instruction. Usually it is caused by mis-aligned instruction due to hardware error. i8042prt is the Microsoft device driver of keyboard and mouse. I don't think it is software problem. Probably the ram or m/b is faulty.

Mini011007-01.dmp BugCheck 1000008E, {c000001d, 804e398b, f7c4ae64, 0}
Probably caused by : hardware ( mouclass!MouseClassServiceCallback+189 )

Mini011407-01.dmp BugCheck 1000000A, {7ec82cfe, 2, 1, 804dbc9a}
Probably caused by : ntoskrnl.exe ( nt!KiUnlinkThread+c )

Mini012207-01.dmp BugCheck 1000008E, {c000001d, 804e38ad, a7d0fc78, 0}
Probably caused by : i8042prt.sys ( i8042prt!I8xQueueCurrentMouseInput+67 )

Mini012407-01.dmp BugCheck 19, {20, 864be8e0, 864be9b0, a1a000d}
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+29 )

Mini012907-01.dmp BugCheck 1000008E, {c000001d, 804e3908, a82a7c70, 0}
Probably caused by : i8042prt.sys ( i8042prt!I8xQueueCurrentMouseInput+67 )
 
Hey!!!!
I tryed this tool and it didnt found any Rootkit Trojan virus...
It found some other stuff,Im gona attach it.
I dont think its faulty RAM because it is quite new and I tested it so....
Faulty m/b yes maybe, but how can I be sure for the m/b?????

Well I hope that it is not either one of these two things,hope,hope heh!!!
Is there anything to try more or this is the last objective diagnosis for this problem!!!????
 
Heya!!!
Im using Ad-Aware SE-Professional,zonealarm-firewall,spyware doctor,NoD 32 as my antivirus aplication.
 
Yes Hendryy,
some think it's hardware... Your -12 volts looks a little low, but there's not much on that source. In my searches for your problem, I came twice across the "rootkit" hijacking scheme. I had never heard of this before... The other "stuff" you attached pointed to a hijacking or hiding of some drivers, AKA Rootkit malware. I don't have anything else to offer. Good luck
 
Status
Not open for further replies.
Back