BSOD driving me mad!

[jetfire]

hello,
im new to this forum so im sorry if i do things wrong but my problem is that on august 12 i did something very wrong because ever since my computer has been giving me BSOD every time i turn it on, sometimes 1 minute after i turn it on sometimes 2 sometimes 3 but it always happens, i put it in safe mode and thats when it works witout BSOD though i did get a BSOD in safe mode once witch really scared me because i tought to myself :boy i really effed up my comp. wht i did on the 12th was i downloaded the system updates (i think) and then i downloaded another program witch allows me to convert videos in iPod readalbe formats, i also downloaded these very suspicius patches for it witch i am 100% sure put somting bad on my comp, i did not hav any antivirus when that happend. (later i got the antivirus and it found like 170 bad files 165 being cookies the rest being infected. my antivirus does not work propperly though due to all this system failure or somtin els) then i activated the patches n all and then my compp got realll sloowwww, i was running another converter program at the time and it got reallll sloowww (when it was blazing fast!) so i was like ok ill just turn it off cuz its geting real bad and ill go to sleep and see it tomorrow (i know, im stupid) the next morgning , everyting is excrutiaingly slow and i get BSOD wen i got in my user account. i panicked and i didnt know what to do. a few days later i found out some more info and got some advice as to how to deal with it. what the bluescreen said was someting realted to IRQL i do not recall what came after IRQL because some time ago, the blue screen stopped showing me this IRQL message. a litle lower in the blue screen i had this code saying STOP: 0x0000008E (0x0000005 and i dont know the rest because the screen dissapears too fast but what i DO know is that sometimes the code that comes after is different from one BSOD to another. i later learned that this problem can be caused by RAM, i am pretty sure that's not it because my rams seem functionnal. second i heard it could be from the Video Card. i have some thoughts leanig towards the vid card because exaclty where it is on my laptop, it gott reallllyy really hot on the night of the 12th and it may have melted or someting and also a heatsink passes over it but then, i tried this handy tool i found from the nets tht is called bsrecover.exe and wat it says is to run it in safe mode and then run it in normal mode, i did that and wen i went to normal mode agen, NO BSOD!!! BUTTTT, everyting waaaaas SLOOOOOOOOOOOWWWWWWWWWWWWWWWW and my net did not respond, i restarted the comp and then BSOD agen so that makes me think that it is not the vid card's fault but instead someting software related like a virus maybe. i have all the minidumps in a zip attached to this post if anyone is interested to help me they are at his disposal. there is also another thing i noticed in the mindump files, files made in august of this year like on the 22 per se, it says they were last modified in 2009......it confueses me......

thanks in advance and sorry if i make mistakes

i would probably be able to supply more info if it is asked for

 

[richc46]

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE Usual Causes: Device driver

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp17_Minidump[1].zip\Mini070310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82245000 PsLoadedModuleList = 0x8235cc70
Debug session time: Sat Jul  3 23:32:19.888 2010 (GMT-4)
System Uptime: 4 days 7:40:43.604
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 84bdeb70, 862c1380, 846b80b0}
*** WARNING: Unable to verify timestamp for yk60x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x86.sys
Probably caused by : yk60x86.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 84bdeb70, Physical Device Object of the stack
Arg3: 862c1380, Functional Device Object of the stack
Arg4: 846b80b0, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  846b80b0
DEVICE_OBJECT: 862c1380
DRIVER_OBJECT: 86237620
IMAGE_NAME:  yk60x86.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  465580c9
MODULE_NAME: yk60x86
FAULTING_MODULE: 8c596000 yk60x86
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  SYSTEM
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from 822763fb to 82312b8d
STACK_TEXT:  
8233aacc 822763fb 0000009f 00000003 84bdeb70 nt!KeBugCheckEx+0x1e
8233ab28 82276018 8233ab94 8233ac50 84772801 nt!PopCheckIrpWatchdog+0x1ad
8233ab68 822ef30b 823534e0 00000000 8200a300 nt!PopCheckForIdleness+0x343
8233ac88 822eeecb 8233acd0 8baeeb02 8233acd8 nt!KiTimerListExpire+0x367
8233ace8 822ef635 00000000 00000000 016d13d6 nt!KiTimerExpiration+0x22a
8233ad50 822ed89d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8233ad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  0x9F_IMAGE_yk60x86.sys
BUCKET_ID:  0x9F_IMAGE_yk60x86.sys
Followup: MachineOwner
---------

Yk60x86.sys file description
Productname: Marvell Yukon Ethernet Controller.
Description: Miniport Driver for Marvell Yukon Ethernet Controller.
Company: Marvell
File size: Various


Outdated Drivers

 DMICall.sys  Tue Dec 05 02:14:23 2000 
lvusbsta.sys Mon Jan 31 13:12:46 2005 
LV561AV.SYS  Mon Jan 31 13:20:03 2005 
mdmxsdk.sys  Mon Jun 19 17:26:59 2006 
peauth.sys   Mon Oct 23 04:55:32 2006 
xaudio.sys   Tue Nov 28 19:44:50 2006 
HSX_CNXT.sys Fri Dec 22 14:48:52 2006 
HSXHWAZL.sys Fri Dec 22 14:49:02 2006 
HSX_DPV.sys  Fri Dec 22 14:50:21 2006 
iaStor.sys   Mon Feb 12 15:46:47 2007 
regi.sys     Mon Apr 16 11:19:05 2007 
ti21sony.sys Mon Apr 23 14:27:48 2007 
yk60x86.sys  Thu May 24 08:10:49 2007 
igdkmd32.sys Tue Jun 26 12:53:33 2007 
SFEP.sys     Fri Aug 03 01:36:08 2007 
NETw4v32.sys Wed Sep 26 09:12:18 2007 
PxHelp20.sys Mon Dec 10 18:48:39 2007 
Apfiltr.sys  Wed Dec 12 04:01:21 2007 
intelppm.sys Sat Jan 19 00:27:20 2008 
cdfs.sys     Sat Jan 19 00:28:02 2008 
bowser.sys   Sat Jan 19 00:28:26 2008 
luafv.sys    Sat Jan 19 00:30:35 2008 
BATTC.SYS    Sat Jan 19 00:32:45 2008 
CmBatt.sys   Sat Jan 19 00:32:47 2008 
compbatt.sys Sat Jan 19 00:32:47 2008 
msisadrv.sys Sat Jan 19 00:32:51 2008 
mssmbios.sys Sat Jan 19 00:32:55 2008 
fileinfo.sys Sat Jan 19 00:34:27 2008 
Dxapi.sys    Sat Jan 19 00:36:12 2008 
Beep.SYS     Sat Jan 19 00:49:10 2008 
mountmgr.sys Sat Jan 19 00:49:13 2008 
kbdclass.sys Sat Jan 19 00:49:14 2008 
mouclass.sys Sat Jan 19 00:49:14 2008 
mouhid.sys   Sat Jan 19 00:49:16 2008 
i8042prt.sys Sat Jan 19 00:49:17 2008 
swenum.sys   Sat Jan 19 00:49:20 2008 
intelide.sys Sat Jan 19 00:49:42 2008 
volmgr.sys   Sat Jan 19 00:49:51 2008 
crcdisk.sys  Sat Jan 19 00:50:29 2008 
vga.sys      Sat Jan 19 00:52:06 2008 
VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 
monitor.sys  Sat Jan 19 00:52:19 2008 
WDFLDR.SYS   Sat Jan 19 00:52:19 2008 
Wdf01000.sys Sat Jan 19 00:52:21 2008 
WUDFPf.sys   Sat Jan 19 00:52:49 2008 
WUDFRd.sys   Sat Jan 19 00:53:04 2008 
WMILIB.SYS   Sat Jan 19 00:53:08 2008 
HIDPARSE.SYS Sat Jan 19 00:53:16 2008 
USBD.SYS     Sat Jan 19 00:53:17 2008 
usbuhci.sys  Sat Jan 19 00:53:20 2008 
1394BUS.SYS  Sat Jan 19 00:53:27 2008 
umbus.sys    Sat Jan 19 00:53:40 2008 
mpsdrv.sys   Sat Jan 19 00:54:45 2008 
rspndr.sys   Sat Jan 19 00:55:03 2008 
lltdio.sys   Sat Jan 19 00:55:03 2008 
tunmp.sys    Sat Jan 19 00:55:40 2008 
ndisuio.sys  Sat Jan 19 00:55:40 2008 
netbios.sys  Sat Jan 19 00:55:45 2008 
nsiproxy.sys Sat Jan 19 00:55:50 2008 
ipfltdrv.sys Sat Jan 19 00:56:23 2008 
ndistapi.sys Sat Jan 19 00:56:24 2008 
NDProxy.SYS  Sat Jan 19 00:56:28 2008 
wanarp.sys   Sat Jan 19 00:56:31 2008 
rasacd.sys   Sat Jan 19 00:56:31 2008 
rasl2tp.sys  Sat Jan 19 00:56:33 2008 
raspptp.sys  Sat Jan 19 00:56:34 2008 
TDI.SYS      Sat Jan 19 00:57:10 2008 
modem.sys    Sat Jan 19 00:57:16 2008 
RDPCDD.sys   Sat Jan 19 01:01:08 2008 
rdpencdd.sys Sat Jan 19 01:01:09 2008 
drmk.sys     Sat Jan 19 01:53:02 2008 
BOOTVID.dll  Sat Jan 19 02:27:15 2008

If any of the above drivers are from Microsoft, you can disregard them.


You had quite a few reports. I checked many and they show Bug Check 9F. It appears tha the Marvell Driver shown above is the problem.


Suggested Action
Update aged drivers
Update the Marvel Yukon Driver
Scan with your antivirus. Download and scan with malwarebytes.


Update Marvel First and test. This may solve the problem. If it does, the old drivers should still be updated to avoid future problems.

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



It is rather late here, I cannot do anymore detail at this time. Update the drivers. If BSOD continue after the install, post the new dump report. I will give you an analyis in greater detail..

 

[jetfire]

thanks i will try to do so and i will write again thanks a lot again

 

[richc46]

Im signing off for the night. Wish you luck Jetfire. I think that you will not have anymore BSOD, if you follow instructions.

 

[jetfire]

awwsome man it worked though i got 2 more dmp files but in the end i did the latest update and no more BSOD buutt, my comp is still slow as hell and it seems tht i cant connect to the internet it says tht theres some sort of problem with the ports or somn and it dosnt work ill have more on tht tomrro and if u want ill attach the 2 other dmps

 

[jetfire]

dude i updated it but im still having problems like really slow system and i cant connect to the internet i also had one more BSOD after the latest update and i tink u shuld check it out i also got 2 more dumps tht i got during the updating
thanx a lot man!

 

[richc46]

I checked the last dump file that you presented. The old drivers that I listed are still present. You must update them. Yes, it will take time, but that is the only way your system will run properly.

I will give you some immediate relief by giving you the information for driver verifier. It will show you which are the drivers that are causing immediate problems. All the old drivers should still be updated.

Enable the Driver Verifier
http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

For your information the dump that you had after you updated the one driver is:
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,


The probable cause given is a driver, again. This report is not the same as the previous, but driver is a potential cause, again.
tdx.sys

Update graphics driver.
You can also do a memory test. With so many different codes,
memory may be the source of the problem.
Download memtest86 and test RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html?filter

 

[jetfire]

ok all was going well i was getting stuff to update my drivers and around 2-3 times my comp froze so i had to reboot it and then a litle later it gave me a completely difrent bluescreen that said KERNEL_STACK_INPAGE_ERROR code STOP:0x00000077 and it took it way longer to do the memory dump than usual like 10-15 secnds longer
i got the dump file attached
thnx agen

 

[richc46]

When you get so many dumps with different numbers, its usually hardware. Drivers must be updated as they can be part of the problem
Follow these instructions
Follow the instructions for BC 124 excluding numbers 4 6 7 9 and background
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
As you can see the list of old drivers is extensive and it would be impractical to update each at this point, but it should be done eventually. In lieu of updating, take the driver verifier test
http://www.sevenforums.com/crash-loc...s-drivers.html
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Repost if you get new BSODs or have questions

 

[jetfire]

so u mean somn mite have shorted/burned out?

 

[richc46]

That I cannot answer, yet. You have received 3 entirely diferent mini dumps. This is the third, which usually means hardware. As you follow my instructions and we eliminate causes, I should be able to tell more.
STOP 0x00000077: KERNEL_STACK_INPAGE_ERROR Usual causes: Memory, Corrupt paging file, File system errors, Disk errors, Bad cables, BIOS, Missing Service Pack, Bad motherboard, Virus infection (particulary in the MBR), Improperly seated cards

As shown above Code 77 can be memory (hardware) Disc errors (possibly hardware)
cables (hardware) Mother Board, etc.
Make sure that you have SP2 installed. Run AntiVirus
Reseat cards.

Many different codes often indicate hardware (may be memory) but always update drivers.

 

[richc46]

This is not as hard as it seems. Lets do one thing at a time and then test.
Lets concentrate on drivers and memory.
When you are done with that, test the computer. If more BSOD post them and we can continue with the suggestions, which may vary due to the additional BSOD. If none for a week, just let me know.