Random Crashes + Blue Screen of Death + Random Freezes

Hi all

My Comp has been doing alot of the following in my topic name for some time but i have had teh crashes happening ALOT, and i was directed here by a guy on another fourm as he said you should be able to help me.

Here is the error i get from my blue screen problem:

IRQL_NOT_LESS_OR_EQUAL

Technical Info:

*** STOP: 0x0000000A ( 0x 010007E8, 0x 0000001D, 0x 00000000, 0x 804D9D57 )


and as for the crashes + freezing ill tell you my comp specs:

P4 3.6ghz Prescot - with a thermaltake silent cooler
Asus P5GDC - delux
2 gig of Ammicore Ram ( took 1 gig out to see if that would stop the crashes but no luck )
160gig hdd( ide), 200gig hdd ( sata), 250gig hdd (sata )
7800GT o/c XFX
Dont no if the case will help much but its a thermaltake armor case.


O /S Windows XP with SP2 fully uptodate

Thanks, Snipe44

 

ok this is what i came up with...
Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Dr. Watson generated MiniDump'
Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Thu Aug 17 20:54:51.000 2006 (GMT+10)
System Uptime: not available
Process Uptime: 0 days 0:00:04.000
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
...........
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1300.1050): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=e8a566f3 ecx=00000001 edx=00000045 esi=0045c4a8 edi=0045c492
eip=0045c4d8 esp=0012ffc0 ebp=0012fc0c iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212
*** WARNING: Unable to verify checksum for vdj.exe
*** ERROR: Module load completed but symbols could not be loaded for vdj.exe
vdj+0x5c4d8:
0045c4d8 0000 add byte ptr [eax],al ds:0023:00000000=??
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


FAULTING_IP:
vdj+5c4d8
0045c4d8 0000 add byte ptr [eax],al

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
.exr ffffffffffffffff
ExceptionAddress: 0045c4d8 (vdj+0x0005c4d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

DEFAULT_BUCKET_ID: STACK_CORRUPTION

PROCESS_NAME: vdj.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

WRITE_ADDRESS: 00000000

BUGCHECK_STR: ACCESS_VIOLATION

LAST_CONTROL_TRANSFER: from 0045eeb3 to 0045c4d8

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012ffbc 0045eeb3 0045b6c8 0012fad4 7c90ee18 vdj+0x5c4d8
0012ffc0 0045b6c8 0012fad4 7c90ee18 7ffdf000 vdj+0x5eeb3
0045eeb3 b34ab1ef 4090784c 8f9f24b0 ccc728c2 vdj+0x5b6c8
0045eeb7 4090784c 8f9f24b0 ccc728c2 1740833c 0xb34ab1ef
0045eebb 8f9f24b0 ccc728c2 1740833c 730a51ed 0x4090784c
0045eebf ccc728c2 1740833c 730a51ed 0670e9b8 0x8f9f24b0
0045eec3 1740833c 730a51ed 0670e9b8 c67e8a94 0xccc728c2
0045eec7 730a51ed 0670e9b8 c67e8a94 97169055 0x1740833c
0045eecb 0670e9b8 c67e8a94 97169055 016888d5 0x730a51ed
0045eecf c67e8a94 97169055 016888d5 b960e9b0 0x670e9b8
0045eed3 97169055 016888d5 b960e9b0 2616dbcf 0xc67e8a94
0045eed7 016888d5 b960e9b0 2616dbcf babf3c8e 0x97169055
0045eedb b960e9b0 2616dbcf babf3c8e 00880354 0x16888d5
0045eedf 2616dbcf babf3c8e 00880354 b460a9a0 0xb960e9b0
0045eee3 babf3c8e 00880354 b460a9a0 b3a3c4a8 0x2616dbcf
0045eee7 00880354 b460a9a0 b3a3c4a8 2841bd2f 0xbabf3c8e
0045eeeb b460a9a0 b3a3c4a8 2841bd2f 1039876d 0x880354
0045eeef b3a3c4a8 2841bd2f 1039876d 7d60e9b0 0xb460a9a0
0045eef3 2841bd2f 1039876d 7d60e9b0 46de2966 0xb3a3c4a8
0045eef7 1039876d 7d60e9b0 46de2966 c670dc28 0x2841bd2f
0045eefb 7d60e9b0 46de2966 c670dc28 f3623f18 0x1039876d
0045eeff 46de2966 c670dc28 f3623f18 4788035b 0x7d60e9b0
0045ef03 c670dc28 f3623f18 4788035b 33d55a94 0x46de2966
0045ef07 f3623f18 4788035b 33d55a94 c059c674 0xc670dc28
0045ef0b 4788035b 33d55a94 c059c674 ec01785e 0xf3623f18
0045ef0f 33d55a94 c059c674 ec01785e 4660e760 0x4788035b
0045ef13 c059c674 ec01785e 4660e760 c20598c4 0x33d55a94
0045ef17 ec01785e 4660e760 c20598c4 c000d32c 0xc059c674
0045ef1b 4660e760 c20598c4 c000d32c 03caa9b7 0xec01785e
0045ef1f c20598c4 c000d32c 03caa9b7 853bb7ef 0x4660e760
0045ef23 c000d32c 03caa9b7 853bb7ef ccd55a14 0xc20598c4
0045ef27 03caa9b7 853bb7ef ccd55a14 c040c32c 0xc000d32c
0045ef2b 853bb7ef ccd55a14 c040c32c 0080785e 0x3caa9b7
0045ef2f ccd55a14 c040c32c 0080785e 4660e9b0 0x853bb7ef
0045ef33 c040c32c 0080785e 4660e9b0 ccd55a94 0xccd55a14
0045ef37 0080785e 4660e9b0 ccd55a94 c040c32c 0xc040c32c
0045ef3b 4660e9b0 ccd55a94 c040c32c 0080785e 0x80785e
0045ef3f ccd55a94 c040c32c 0080785e 4660e9b0 0x4660e9b0
0045ef43 c040c32c 0080785e 4660e9b0 ccd55a94 0xccd55a94
0045ef47 0080785e 4660e9b0 ccd55a94 c040c32c 0xc040c32c
0045ef4b 4660e9b0 ccd55a94 c040c32c 0080785e 0x80785e
0045ef4f ccd55a94 c040c32c 0080785e 4660e9b0 0x4660e9b0
0045ef53 c040c32c 0080785e 4660e9b0 ccd55a94 0xccd55a94
0045ef57 0080785e 4660e9b0 ccd55a94 c040c32c 0xc040c32c
0045ef5b 4660e9b0 ccd55a94 c040c32c 0080785e 0x80785e
0045ef5f ccd55a94 c040c32c 0080785e 4660e9b0 0x4660e9b0
0045ef63 c040c32c 0080785e 4660e9b0 eca12fdb 0xccd55a94
0045ef67 0080785e 4660e9b0 eca12fdb 8d60a563 0xc040c32c
0045ef6b 4660e9b0 eca12fdb 8d60a563 72ef153b 0x80785e
0045ef6f eca12fdb 8d60a563 72ef153b 2809c9c9 0x4660e9b0
0045ef73 8d60a563 72ef153b 2809c9c9 adb012b4 0xeca12fdb
0045ef77 72ef153b 2809c9c9 adb012b4 ac2c825c 0x8d60a563
0045ef7b 2809c9c9 adb012b4 ac2c825c 21b11b31 0x72ef153b
0045ef7f adb012b4 ac2c825c 21b11b31 aae3e9ba 0x2809c9c9
0045ef83 ac2c825c 21b11b31 aae3e9ba b85e0ccc 0xadb012b4
0045ef87 21b11b31 aae3e9ba b85e0ccc 9617a708 0xac2c825c
0045ef8b aae3e9ba b85e0ccc 9617a708 008121b6 0x21b11b31
0045ef8f b85e0ccc 9617a708 008121b6 c39862b0 0xaae3e9ba
0045ef93 9617a708 008121b6 c39862b0 93dd2f6b 0xb85e0ccc
0045ef97 008121b6 c39862b0 93dd2f6b 98844072 0x9617a708
0045ef9b c39862b0 93dd2f6b 98844072 5380709c 0x8121b6
0045ef9f 93dd2f6b 98844072 5380709c 4e60e9d8 0xc39862b0
0045efa3 98844072 5380709c 4e60e9d8 24dd3094 0x93dd2f6b
0045efa7 5380709c 4e60e9d8 24dd3094 c0405f7b 0x98844072
0045efab 4e60e9d8 24dd3094 c0405f7b 9c19900e 0x5380709c
0045efaf 24dd3094 c0405f7b 9c19900e 9eebe9b0 0x4e60e9d8
0045efb3 c0405f7b 9c19900e 9eebe9b0 d6a08111 0x24dd3094
0045efb7 9c19900e 9eebe9b0 d6a08111 b328937c 0xc0405f7b
0045efbb 9eebe9b0 d6a08111 b328937c e8803831 0x9c19900e
0045efbf d6a08111 b328937c e8803831 b99f1a62 0x9eebe9b0
0045efc3 b328937c e8803831 b99f1a62 1c3d09c4 0xd6a08111
0045efc7 e8803831 b99f1a62 1c3d09c4 aa40c3b6 0xb328937c
0045efcb b99f1a62 1c3d09c4 aa40c3b6 9a01905c 0xe8803831
0045efcf 1c3d09c4 aa40c3b6 9a01905c 460ae9b0 0xb99f1a62
0045efd3 aa40c3b6 9a01905c 460ae9b0 ccbf5afe 0x1c3d09c4


STACK_COMMAND: ~0s; .ecxr ; kb

FAULTING_THREAD: 00001050

PRIMARY_PROBLEM_CLASS: STACK_CORRUPTION

FOLLOWUP_IP:
vdj+5c4d8
0045c4d8 0000 add byte ptr [eax],al

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vdj

IMAGE_NAME: vdj.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 43bd7fe7

SYMBOL_NAME: vdj+5c4d8

FAILURE_BUCKET_ID: ACCESS_VIOLATION_vdj+5c4d8

BUCKET_ID: ACCESS_VIOLATION_vdj+5c4d8

Followup: MachineOwner
---------

eax=00000000 ebx=e8a566f3 ecx=00000001 edx=00000045 esi=0045c4a8 edi=0045c492
eip=0045c4d8 esp=0012ffc0 ebp=0012fc0c iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212
vdj+0x5c4d8:
0045c4d8 0000 add byte ptr [eax],al ds:0023:00000000=??
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0012ffbc 0045eeb3 0045b6c8 0012fad4 7c90ee18 vdj+0x5c4d8
0012ffc0 0045b6c8 0012fad4 7c90ee18 7ffdf000 vdj+0x5eeb3
0045eeb3 b34ab1ef 4090784c 8f9f24b0 ccc728c2 vdj+0x5b6c8
0045eeb7 4090784c 8f9f24b0 ccc728c2 1740833c 0xb34ab1ef
0045eebb 8f9f24b0 ccc728c2 1740833c 730a51ed 0x4090784c
0045eebf ccc728c2 1740833c 730a51ed 0670e9b8 0x8f9f24b0
0045eec3 1740833c 730a51ed 0670e9b8 c67e8a94 0xccc728c2
0045eec7 730a51ed 0670e9b8 c67e8a94 97169055 0x1740833c
0045eecb 0670e9b8 c67e8a94 97169055 016888d5 0x730a51ed
0045eecf c67e8a94 97169055 016888d5 b960e9b0 0x670e9b8
0045eed3 97169055 016888d5 b960e9b0 2616dbcf 0xc67e8a94
0045eed7 016888d5 b960e9b0 2616dbcf babf3c8e 0x97169055
0045eedb b960e9b0 2616dbcf babf3c8e 00880354 0x16888d5
0045eedf 2616dbcf babf3c8e 00880354 b460a9a0 0xb960e9b0
0045eee3 babf3c8e 00880354 b460a9a0 b3a3c4a8 0x2616dbcf
0045eee7 00880354 b460a9a0 b3a3c4a8 2841bd2f 0xbabf3c8e
0045eeeb b460a9a0 b3a3c4a8 2841bd2f 1039876d 0x880354
0045eeef b3a3c4a8 2841bd2f 1039876d 7d60e9b0 0xb460a9a0
0045eef3 2841bd2f 1039876d 7d60e9b0 46de2966 0xb3a3c4a8
0045eef7 1039876d 7d60e9b0 46de2966 c670dc28 0x2841bd2f
start end module name
00400000 0046a000 vdj vdj.exe Fri Jan 06 07:21:59 2006 (43BD7FE7)
77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 17:56:36 2004 (411096B4)
77c00000 77c08000 version version.dll Wed Aug 04 17:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 17:59:14 2004 (41109752)
77d40000 77dd0000 user32 user32.dll Thu Mar 03 05:09:29 2005 (42260159)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 17:56:23 2004 (411096A7)
77e70000 77f01000 rpcrt4 rpcrt4.dll Wed Aug 04 17:56:30 2004 (411096AE)
77f10000 77f57000 gdi32 gdi32.dll Thu Dec 29 13:54:35 2005 (43B34FEB)
77f60000 77fd6000 shlwapi shlwapi.dll Fri Jun 23 21:02:51 2006 (449BCA5B)
7c800000 7c8f4000 kernel32 kernel32.dll Wed Jul 05 20:55:00 2006 (44AB9A84)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 17:56:36 2004 (411096B4)
Closing open log file c:\debuglog.txt



**edited as i finaly got it to work **

 

sorry to bumb this but i really need help i have posted my screen dump above this post, Cheers.

 

Hi and welcome to the BBS,

The problem appears to be with the file vdj.exe. From a search this seems to be the program Virtual DJ. I would uninstall that program. If you still need it try reinstalling it, but the same problem might occur, in which case you could try find an updated version, checking the maker's website for FAQs/troubleshooting or find another similar program.

If you don't have Virtual DJ, do a search of your harddrive for vdj or vdj.exe. You may need to go Folder Options in the menu of My Computer or Windows Explorer and unhide system files and folders. When you find vdj.exe look at what program folder it is in or if it is in the Windows folder, right-click on it and select Properties, see if you can find the maker there.

Matt

 

Ok, i have removed Virtual DJ and im still getting my freezes / random reboots... no blue screen at the moment so there is 1 problem fixed i hope


More help still needed!

Cheers mattan!

 

Something seems to have changed....

Your options now, I think, are:

The Virtual DJ did not uninstall correctly. Try installing and uninstalling again, OR, if you used the listing in Add or Remove Programs, try looking under the Virtual DJ heading in All Programs, it may have a better uninstaller there.

The VDJ may have corrupted the audio drivers. Find the updated (recommended) drivers for your audio system (or just try reinstalling the current audio drivers).

VDJ may be conflicting with the audio "Contol Panel ", this is installed with your audio drivers and you should be able to reinstall it.

There may be a problem in the registry. You could try running a registry cleaner ...but I do not not trust them to only remove unnecessary listings. See if you could identify VDJ (Virtual DJ) items marked as needing to be cleaned.

Matt
Edit: make a note of when the freezes/reboots happen. Is it when a particular piece of hardware is being accessed?

You should be able to log a reboot problem in a similar manner to the way you logged the original problem. Search the Win XP forum for "log" or "logging "...I have not needed to use it with Win XP.

 

i got a blue screen whilst playing Counter Strike about 10mins ago... so i check the fourms and saw my thread.. and i have deleted Virtual DJ & i did a registery clean to.. so hopefully that pinged it lol

Im still freezing and rebooting to... and it always happens when i play games such as battlefield 2 and Counter Strike Source.... ( only 2 games i mostly play )

So i dont no if that would be causing my computer to overheat or what....


Lets hope the blue screens have finally stopped and thanks once again mattman!


** edit **

Still getting same error for my blue screens to.

 

Any ideas? more help please



* sorry to bump *

And i have also ordered a new power supply as i dont think my current 1 is coping to well

 

Sorry Snipe44 , I think I was going to put some thought into this, but ended up getting side-tracked.

What are the differences now? Do you feel this is a different problem or an extension of the original problem.

Have you tried running the logs again? You should be able to get a log/minidump when you get a blue screen, you won't when it freezes (the system has crashed).

If it relates to graphics based programs (example, games) it is HIGHLY likely to be a problem with the graphics system (and maybe drivers in particular).

If you would like to post back with the model of your graphics card, and, if it is a built-in graphics system (part of the motherboard, not an add-in card), the model of your motherboard or computer (like a Dell Dimension XXXX model).

Everest in my signature can help identify your hardware.

Have you changed/upgraded the graphics card or it's drivers?

There are some simple tests using dxdiag. Enter dxdiag at the Run command line. Do the tests under the Display tab.

If the graphics may have it's own heatsink and fan, open the case and check the fan is spinning freely, in fact, because games are quite "strenuous" on the system, check all the fans are spinning freely, including the power supply fan, and there is no build-up of dust in the heatsinks

Matt
Edit: don't hesitate to bump the thread I might put it on the backburner for further thought, then get side-tracked again

If you are concerned about the power supply, use the power calculator here:http://www.journeysystems.com/power_supply_calculator.php

 

http://www.xfxforce.com/media/seriesSpecSheet/4d56cbb0059c5e7101059e8917a30003/T70G_UDF.pdf

Theres the link to the specs of my card. It is factory o/c

I built my own pc so its certainly not a dell lol

i personally think it has gotten worse and is getting worse, and if all else fails ill try reinstalling windows *sighs*.

Ill get the logs for you when i get my blue screen ( shouldnt be to long till i get 1 )

Yea i have previously used Everest before and found it to be a very good program!

everything in the dxdiag came up clear and i ran the graphics test's and they were fine ill get back to you on the dust in my computer as im downloading a patch for a game at the moment.

Test for powersupply came in at 324watts but it didnt have my graphics card in there.

So ill get back to you soon,

Thanks once again mattman,

-Snipe44

 

Hi Snipe44,
I would try upgrading or reinstalling drivers before taking an axe to Windows. You could spend a weekend reinstalling everything only to find you are in the same position.

First see if there are updated drivers for your motherboard's chipset, otherwise try (re)installing the chipset drivers from the CD that came with the motherboard. Next the graphics drivers, you should uninstall the current drivers and find a more recent set. I have been to the XFX website before and that time they just linked to the nVidia website, check XFX first though. Put the model number and "drivers" into a Google search. Look through the results for postings in the gaming forums, they will tell you which version of the drivers will be best for your card (recent versions may be more suited to SLI motherboards), usually it is the release a version or two after the release of your graphics chipset.

If the motherboard happens to have built-in graphics as well, you should not try running drivers for that at the same time you have the nVidia drivers installed. Let me know if this is the case.

Uninstall the nVidia graphics drivers in Add/Remove Programs. When you reboot and the hardware wizard runs at startup, click Cancel and then run the nVidia drivers program when you get to the desktop.

Normally I would be more concerned about the graphics drivers, but that VDJ program would be very dependent on the audio drivers, I would guess. Look for updated drivers for the audio or reinstall those that came with the hardware (your motherboard CD if it is built-in).

After that, hopefully you will find it works correctly. Check in Device Manager that there are no problems listed.

Don't be afraid to uninstall and reinstall drivers as long as you have a set available for reinstallation. Almost every time I have installed Win XP I have found that the graphics drivers need removal and reinstallation.

Matt

 

I have uninstalled my graphic drivers reinstalled... still blue screen ( did that last nite ) i found a new update patch for my card installed and blue screen
My mobo doesnt use onboard gfx... either

Now im updating my audio drivers:
Ok there was a update for my C-Media High Definition Audio Device, and that was the only one
I also deleted my sound drivers and reinstalled them and then updated them as above. and using my CD provided with my motherboard.

So still no luck *sigh*

Sorry for taking so long to get back

 

No luck? Drat!

When you say "deleted" the drivers I suppose you mean uninstalled them in Device Manager. If you feel like another round with them, try booting into Safe Mode, go to Add/Remove programs and check for uninstallers there first, then go to Device Manager and check they are gone, or uninstall them there if they did not have an uninstaller in Add/Remove Programs (you may have done this, but try in Safe Mode next time).

Has anyone mentioned temperatures? You can use Everest in my signature, although reading the temperatures in the BIOS settings will be more accurate. Open the case and check the fan is spinning freely on the graphics card and all other fans as well, including the PSU fan. The nVidia 7800 will be outputting a lot of heat, you will need a good airflow through the case. If you suspect that there is not enough airflow, direct a desk fan into the open case and then try running the games. Check there is no build up of dust in the heatsinks under the fans.

Look at the voltages and check the power requirements here:
http://www.journeysystems.com/power_supply_calculator.php

I suppose even testing the RAM with the diagnostics in my signature would feasible as well.

Does there seem to be any pattern (yet)? If not, I might suspect one of those hardware issues like heat, power or RAM.

Matt

 

Can you post your current Memory settings re:
CAS
TRCD (RAS to CAS delay)
TRP (RAS Precharge)
TRAS (Active to Precharge)
Command Rate

Thanks.

 

OK here we go:

Went to the BIOS and left the temps without a fan going for 5mins then got my fan blowing in there and it was the same ( desk fan )

CPU : 61.5 - 62.5 degrees ( C ) steady

Memory : 35 degrees ( C )

Now according to everest my:

CPU is 52 degrees ( C )

Couldnt get one for my Memory

According to the Nvidia control panel

My GPU is 45 degrees

And everst says its 45 degrees to




ok now, Yes i deleted them threw device manager.

Ill give them a whirl later on when i get a chance.. im sorta celerbrating my 17th bday today

With my cables there absolutly everywhere i took them to a computershop to try and hide and make it look nice but they made it worse and im thinking new psu = better cables = look nice = easy to hide.

I have checked for dust with my system fans, gfx card, cpu and psu and cleaned 99.9% out

I would do the RAM test cept i dont have any blank discs as of yet but ill go shopping tonight to collect somthing and do the test so ill get back to you on that 1 mattman.

The pattern yes... Well 99% of the time now its happening during my gaming sessions its now more commomaly Blue screens which is abit of a bugger... but my random restarts seem to have stopped which is a good sign


Rockster2U and you would mean my timings with my ram yes? Ill post a screen shot of that below for you from Everst and also my a Picture of my PSU test for Mattman:

Mattman here is the PSU results ( as i said earlyer they didnt have my graphics card on there so i found a 6800 ultra somthing... so thats as close as i could get it

http://img142.imageshack.us/my.php?image=resultsforpsuwattshn4.png

Rockster2U

Here is the info on my RAM for you:

http://img178.imageshack.us/my.php?image=everestmemoryon7.jpg

http://img142.imageshack.us/my.php?image=memory2fv0.jpg

Oh and i have put my other 1 gig stick of ram back in my computer also thought i'd add that and if i remember anything else ill get back to you.. but ill add more info tonight once i do that memory test for you..

I new i forgot somthing! My CPU fan is now not reconised when i start up my computer my mobo makes a 3 beeps to tell me its not spinning but it is and its still plugged in the right spot... so maybe my mobo is dieing?

Thanks mattman & Rockster2U


-Snipe44

 

61.5 - 62.5*C in the BIOS readings (idle) would concern me (and being a Pentium processor it would concern me even more). You are now getting "temperature" related beeps, so that would sound alarm bells for me. The CPU fan may still be spinning, but the revolutions may be falling, does it seem to be spinning freely? I would look at replacing that fan, unless you can see something like a loose connection for the cable or a large build-up of dust.

If you decide it may be the fan that is the problem and you want to replace it, if you try to remove the fan be careful, do not remove the heatsink from over the processor chip, otherwise you will need to replace the thermal compound between the heatsink and the chip, so just look at the fan and how it is connected.

I can't think of other reasons why you might have higher than normal temperatures and warning beeps about the fan.

See if Rockster2U or the others may not agree.

Matt

 

I can be a little quick to pull the trigger but I'd certainly agree that the CPU temp is out of whack on the high side. I am also going to question the memory compatability with that motherboard. Your Everest post only included the one module and you should either pay for the deluxe version of Everest or download v 2.20 (the last free one) so you can get complete information. I'd like to see the specs on that other memory module but Spectek (made by Micron) may not be compatable with your motherboard and some PC3200 4x128 is not Intel compatable at all. Actually (and again I'm quick on the trigger) you'd see a big improvement with better memory, especially if you are into gaming. There is probably more to your BSOD situation than just heat and memory but heat and memory are certainly major contributors.

You might want to consider cleaning up those drivers, cleaning up the registry with something like RegSeeker or JV16 PowerTools, replacing that HSF fan and getting some decent memory.

 

Hey sorry guys! I have moved house and my ISP stuffed up our relocation

I found my bluescreen dump log i think... so here it is:

[KB925486.log]
0.593: ================================================================================
0.593: 2006/10/18 01:30:52.718 (local)
0.593: C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\d2e5583a5fd4098c4bb26352edaf419b\update\update.exe (version 6.2.29.0)
0.593: Hotfix started with following command line: /si /ParentInfo:f91c958f3c2ff242aa0f532e8319e13c
0.593: FileVersion of C:\Program Files\internet explorer\iexplore.exe is Less Than 7.0.0.0
0.593: Condition succeeded for section Test.IE7InstallBlock.Section in Line 1 of PreRequisite
0.703: DoInstallation: CleanPFR failed: 0x2
0.703: SetProductTypes: InfProductBuildType=BuildType.IP
0.703: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.718: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB925486$
0.718: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
0.734: ref tag c:\windows\system32\sp4.cab does not exist
0.734: ref tag c:\windows\system32\sp3.cab does not exist
0.734: ref tag c:\windows\system32\sp2.cab does not exist
0.734: ref tag c:\windows\system32\sp1.cab does not exist
0.734: ref tag c:\windows\system32\driver.cab does not exist
0.734: ref tag c:\windows\system32\fp40ext.cab does not exist
0.734: ref tag c:\windows\system32\fp40ext1.cab does not exist
0.734: ref tag c:\windows\system32\wms4.cab does not exist
0.734: ref tag c:\windows\system32\wms41.cab does not exist
0.734: ref tag c:\windows\system32\ims.cab does not exist
0.734: ref tag c:\windows\system32\ims1.cab does not exist
0.734: ref tag c:\windows\system32\ins.cab does not exist
0.734: ref tag c:\windows\system32\ins1.cab does not exist
0.750: Starting AnalyzeComponents
0.750: AnalyzePhaseZero used 0 ticks
0.750: No c:\windows\INF\updtblk.inf file.
0.750: OEM file scan used 0 ticks
0.890: AnalyzePhaseOne: used 140 ticks
0.890: AnalyzeComponents: Hotpatch analysis disabled; skipping.
0.890: AnalyzeComponents: Hotpatching is disabled.
0.890: FindFirstFile c:\windows\$hf_mig$\*.*
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.922: AnalyzeForBranching used 16 ticks.
0.922: AnalyzePhaseTwo used 0 ticks
0.922: AnalyzePhaseThree used 0 ticks
0.922: AnalyzePhaseFive used 0 ticks
0.922: AnalyzePhaseSix used 0 ticks
0.922: AnalyzeComponents used 172 ticks
0.922: Downloading 2 files
0.922: bPatchMode = TRUE
0.922: Inventory complete: ReturnStatus=0, 204 ticks
0.922: Num Ticks for invent : 204
0.937: [dumpDownloadTask] Update.exe posting request file to download a total of 370068 bytes (54539 bytes in patches and 315529 bytes in fallbacks)
0.937: dumpDownloadTask returned 0xf200 (more files to download)
0.937: KB925486 installation did not complete.
0.937: Update.exe extended error code = 0xf200
0.563: ================================================================================
0.563: 2006/10/18 02:24:48.156 (local)
0.563: C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\d2e5583a5fd4098c4bb26352edaf419b\update\update.exe (version 6.2.29.0)
0.563: Hotfix started with following command line: /si /ParentInfo:3a9a9536ce1ede47ab9da2b5a940e0e3
0.563: FileVersion of C:\Program Files\internet explorer\iexplore.exe is Less Than 7.0.0.0
0.563: Condition succeeded for section Test.IE7InstallBlock.Section in Line 1 of PreRequisite
0.672: DoInstallation: CleanPFR failed: 0x2
0.672: SetProductTypes: InfProductBuildType=BuildType.IP
0.672: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.688: Express: 370,068 bytes were downloaded.
0.766: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
0.782: KB925486 installation did not complete.
0.782: Update.exe extended error code = 0xf201
0.578: ================================================================================
0.578: 2006/10/18 03:01:36.078 (local)
0.578: C:\WINDOWS\SoftwareDistribution\Download\cf66607446e145f5d8c8bf3f55214656\update\update.exe (version 6.2.29.0)
0.578: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.578: Hotfix started with following command line: -q -z -er /ParentInfo:30b837203e4d68438ee1a2c02dd00799
0.578: FileVersion of C:\Program Files\internet explorer\iexplore.exe is Less Than 7.0.0.0
0.578: Condition succeeded for section Test.IE7InstallBlock.Section in Line 1 of PreRequisite
0.703: ---- Old Information In The Registry ------
0.703: Source:C:\WINDOWS\system32\_000012_.tmp.dll (5.1.2600.2180)
0.703: Destination:
0.703: Source:C:\WINDOWS\system32\SETA3.tmp (5.1.2600.2622)
0.703: Destination:C:\WINDOWS\system32\winsrv.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETA4.tmp (5.1.2600.2622)
0.718: Destination:C:\WINDOWS\system32\user32.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETA5.tmp (5.1.2600.2622)
0.718: Destination:C:\WINDOWS\system32\authz.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETBF.tmp (5.1.2600.2938)
0.718: Destination:C:\WINDOWS\system32\rasadhlp.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETC0.tmp (5.1.2600.2938)
0.718: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.0)
0.718: Destination:
0.718: Source:C:\WINDOWS\system32\SETCE.tmp (5.1.2600.2665)
0.718: Destination:C:\WINDOWS\system32\rpcss.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETCF.tmp (5.1.2600.2665)
0.718: Destination:C:\WINDOWS\system32\olecli32.dll (5.1.2600.0)
0.718: Source:C:\WINDOWS\system32\SETD0.tmp (5.1.2600.2665)
0.718: Destination:C:\WINDOWS\system32\ole32.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETDA.tmp (6.0.2900.2869)
0.718: Destination:C:\WINDOWS\system32\inetcomm.dll (6.0.2900.2180)
0.718: Source:C:\WINDOWS\system32\SETED.tmp (2001.12.4414.311)
0.718: Destination:C:\WINDOWS\system32\mtxclu.dll (2001.12.4414.258)
0.718: Source:C:\WINDOWS\system32\SETEE.tmp (2001.12.4414.311)
0.718: Destination:C:\WINDOWS\system32\msdtcuiu.dll (2001.12.4414.258)
0.718: Source:C:\WINDOWS\system32\SETF0.tmp (2001.12.4414.311)
0.718: Destination:C:\WINDOWS\system32\msdtcprx.dll (2001.12.4414.258)
0.718: Source:C:\WINDOWS\system32\SETFE.tmp (5.1.2600.2744)
0.718: Destination:C:\WINDOWS\system32\umpnpmgr.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SET102.tmp (6.0.2900.2869)
0.718: Destination:C:\WINDOWS\system32\shell32.dll (6.0.2900.2180)
0.718: Source:C:\WINDOWS\system32\SET109.tmp (6.5.2600.2749)
0.718: Destination:C:\WINDOWS\system32\quartz.dll (6.5.2600.2180)
0.718: Source:C:\WINDOWS\system32\SET116.tmp (5.1.2600.2818)
0.718: Destination:C:\WINDOWS\system32\gdi32.dll (5.1.2600.2180)
0.718: ---- New Information In The Registry ------
0.718: Source:C:\WINDOWS\system32\_000012_.tmp.dll (5.1.2600.2180)
0.718: Destination:
0.718: Source:C:\WINDOWS\system32\SETA3.tmp (5.1.2600.2622)
0.718: Destination:C:\WINDOWS\system32\winsrv.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETA4.tmp (5.1.2600.2622)
0.718: Destination:C:\WINDOWS\system32\user32.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETA5.tmp (5.1.2600.2622)
0.718: Destination:C:\WINDOWS\system32\authz.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETBF.tmp (5.1.2600.2938)
0.718: Destination:C:\WINDOWS\system32\rasadhlp.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETC0.tmp (5.1.2600.2938)
0.718: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.0)
0.718: Destination:
0.718: Source:C:\WINDOWS\system32\SETCE.tmp (5.1.2600.2665)
0.718: Destination:C:\WINDOWS\system32\rpcss.dll (5.1.2600.2180)
0.718: Source:C:\WINDOWS\system32\SETCF.tmp (5.1.2600.2665)
0.718: Destination:C:\WINDOWS\system32\olecli32.dll (5.1.2600.0)
0.734: Source:C:\WINDOWS\system32\SETD0.tmp (5.1.2600.2665)
0.734: Destination:C:\WINDOWS\system32\ole32.dll (5.1.2600.2180)
0.734: Source:C:\WINDOWS\system32\SETDA.tmp (6.0.2900.2869)
0.734: Destination:C:\WINDOWS\system32\inetcomm.dll (6.0.2900.2180)
0.734: Source:C:\WINDOWS\system32\SETED.tmp (2001.12.4414.311)
0.734: Destination:C:\WINDOWS\system32\mtxclu.dll (2001.12.4414.258)
0.734: Source:C:\WINDOWS\system32\SETEE.tmp (2001.12.4414.311)
0.734: Destination:C:\WINDOWS\system32\msdtcuiu.dll (2001.12.4414.258)
0.734: Source:C:\WINDOWS\system32\SETF0.tmp (2001.12.4414.311)
0.734: Destination:C:\WINDOWS\system32\msdtcprx.dll (2001.12.4414.258)
0.734: Source:C:\WINDOWS\system32\SETFE.tmp (5.1.2600.2744)
0.734: Destination:C:\WINDOWS\system32\umpnpmgr.dll (5.1.2600.2180)
0.734: Source:C:\WINDOWS\system32\SET102.tmp (6.0.2900.2869)
0.734: Destination:C:\WINDOWS\system32\shell32.dll (6.0.2900.2180)
0.734: Source:C:\WINDOWS\system32\SET109.tmp (6.5.2600.2749)
0.734: Destination:C:\WINDOWS\system32\quartz.dll (6.5.2600.2180)
0.734: Source:C:\WINDOWS\system32\SET116.tmp (5.1.2600.2818)
0.734: Destination:C:\WINDOWS\system32\gdi32.dll (5.1.2600.2180)
0.734: SetProductTypes: InfProductBuildType=BuildType.IP
0.734: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.734: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB925486$
0.750: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
0.750: ref tag c:\windows\system32\sp4.cab does not exist
0.750: ref tag c:\windows\system32\sp3.cab does not exist
0.750: ref tag c:\windows\system32\sp2.cab does not exist
0.750: ref tag c:\windows\system32\sp1.cab does not exist
0.750: ref tag c:\windows\system32\driver.cab does not exist
0.750: ref tag c:\windows\system32\fp40ext.cab does not exist
0.750: ref tag c:\windows\system32\fp40ext1.cab does not exist
0.750: ref tag c:\windows\system32\wms4.cab does not exist
0.750: ref tag c:\windows\system32\wms41.cab does not exist
0.750: ref tag c:\windows\system32\ims.cab does not exist
0.750: ref tag c:\windows\system32\ims1.cab does not exist
0.765: ref tag c:\windows\system32\ins.cab does not exist
0.765: ref tag c:\windows\system32\ins1.cab does not exist
0.765: Starting AnalyzeComponents
0.765: AnalyzePhaseZero used 0 ticks
0.765: No c:\windows\INF\updtblk.inf file.
0.765: OEM file scan used 0 ticks
0.859: AnalyzePhaseOne: used 94 ticks
0.859: AnalyzeComponents: Hotpatch analysis disabled; skipping.
0.859: AnalyzeComponents: Hotpatching is disabled.
0.859: FindFirstFile c:\windows\$hf_mig$\*.*
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.859: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.875: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.890: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.906: KB925486 Setup encountered an error: The update.ver file is not correct.
0.922: AnalyzeForBranching used 16 ticks.
0.937: AnalyzePhaseTwo used 15 ticks
0.937: AnalyzePhaseThree used 0 ticks
0.937: AnalyzePhaseFive used 0 ticks
0.937: AnalyzePhaseSix used 0 ticks
0.937: AnalyzeComponents used 172 ticks
0.937: Downloading 0 files
0.937: bPatchMode = TRUE
0.937: Inventory complete: ReturnStatus=0, 203 ticks
0.937: Num Ticks for invent : 203
0.953: VerifyTargetFileSize: Unable to verify size as Source = NULL for file c:\windows\inf\HFX119.tmp
0.953: Copied file: c:\windows\inf\branches.inf
1.031: Allocation size of drive C: is 4096 bytes, free space = 86395150336 bytes
1.047: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
1.047: Drive C: free 82392MB req: 12MB w/uninstall: NOT CALCULATED.
1.047: CabinetBuild complete
1.047: Num Ticks for Cabinet build : 110
1.047: DynamicStrings section not defined or empty.
1.047: FileInUse:: Detection disabled.
2.047: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
2.078: Num Ticks for Backup : 1031
2.125: Num Ticks for creating uninst inf : 47
2.125: Registering Uninstall Program for -> KB925486, KB925486 , 0x0
2.125: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
2.140: System Restore Point set.
2.172: Copied file: C:\WINDOWS\system32\spmsg.dll
2.531: PFE2: Not avoiding Per File Exceptions.
2.547: GetCatVersion: Failed to retrieve version information from C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB925486.cat with error 0x57
2.562: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\update_SP2QFE.inf -> c:\windows\$hf_mig$\KB925486\update\update_SP2QFE.inf.
2.562: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\spuninst.exe -> c:\windows\$hf_mig$\KB925486\spuninst.exe.
2.578: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\spmsg.dll -> c:\windows\$hf_mig$\KB925486\spmsg.dll.
2.593: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\spcustom.dll -> c:\windows\$hf_mig$\KB925486\update\spcustom.dll.
2.656: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\KB925486.CAT -> c:\windows\$hf_mig$\KB925486\update\KB925486.CAT.
2.656: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\update.exe -> c:\windows\$hf_mig$\KB925486\update\update.exe.
2.656: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\updspapi.dll -> c:\windows\$hf_mig$\KB925486\update\updspapi.dll.
2.672: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\update.ver -> c:\windows\$hf_mig$\KB925486\update\update.ver.
2.672: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\updatebr.inf -> c:\windows\$hf_mig$\KB925486\update\updatebr.inf.
2.687: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\eula.txt -> c:\windows\$hf_mig$\KB925486\update\eula.txt.
2.687: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\update\branches.inf -> c:\windows\$hf_mig$\KB925486\update\branches.inf.
2.718: Copied file: C:\Program Files\Common Files\microsoft shared\vgx\vgx.dll
2.828: Copied file: C:\WINDOWS\system32\DllCache\vgx.dll
2.890: Copied file: c:\windows\$hf_mig$\KB925486\SP2QFE\vgx.dll
2.984: DoInstallation: Installing assemblies with source root path: c:\windows\softwaredistribution\download\cf66607446e145f5d8c8bf3f55214656\
2.984: Num Ticks for Copying files : 859
2.984: Num Ticks for Reg update and deleting 0 size files : 0
3.000: ---- Old Information In The Registry ------
3.000: Source:C:\WINDOWS\system32\_000012_.tmp.dll (5.1.2600.2180)
3.000: Destination:
3.000: Source:C:\WINDOWS\system32\SETA3.tmp (5.1.2600.2622)
3.000: Destination:C:\WINDOWS\system32\winsrv.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETA4.tmp (5.1.2600.2622)
3.000: Destination:C:\WINDOWS\system32\user32.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETA5.tmp (5.1.2600.2622)
3.000: Destination:C:\WINDOWS\system32\authz.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETBF.tmp (5.1.2600.2938)
3.000: Destination:C:\WINDOWS\system32\rasadhlp.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETC0.tmp (5.1.2600.2938)
3.000: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.0)
3.000: Destination:
3.000: Source:C:\WINDOWS\system32\SETCE.tmp (5.1.2600.2665)
3.000: Destination:C:\WINDOWS\system32\rpcss.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETCF.tmp (5.1.2600.2665)
3.000: Destination:C:\WINDOWS\system32\olecli32.dll (5.1.2600.0)
3.000: Source:C:\WINDOWS\system32\SETD0.tmp (5.1.2600.2665)
3.000: Destination:C:\WINDOWS\system32\ole32.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SETDA.tmp (6.0.2900.2869)
3.000: Destination:C:\WINDOWS\system32\inetcomm.dll (6.0.2900.2180)
3.000: Source:C:\WINDOWS\system32\SETED.tmp (2001.12.4414.311)
3.000: Destination:C:\WINDOWS\system32\mtxclu.dll (2001.12.4414.258)
3.000: Source:C:\WINDOWS\system32\SETEE.tmp (2001.12.4414.311)
3.000: Destination:C:\WINDOWS\system32\msdtcuiu.dll (2001.12.4414.258)
3.000: Source:C:\WINDOWS\system32\SETF0.tmp (2001.12.4414.311)
3.000: Destination:C:\WINDOWS\system32\msdtcprx.dll (2001.12.4414.258)
3.000: Source:C:\WINDOWS\system32\SETFE.tmp (5.1.2600.2744)
3.000: Destination:C:\WINDOWS\system32\umpnpmgr.dll (5.1.2600.2180)
3.000: Source:C:\WINDOWS\system32\SET102.tmp (6.0.2900.2869)
3.015: Destination:C:\WINDOWS\system32\shell32.dll (6.0.2900.2180)
3.015: Source:C:\WINDOWS\system32\SET109.tmp (6.5.2600.2749)
3.015: Destination:C:\WINDOWS\system32\quartz.dll (6.5.2600.2180)
3.015: Source:C:\WINDOWS\system32\SET116.tmp (5.1.2600.2818)
3.015: Destination:C:\WINDOWS\system32\gdi32.dll (5.1.2600.2180)
3.015: ---- New Information In The Registry ------
3.015: Source:C:\WINDOWS\system32\_000012_.tmp.dll (5.1.2600.2180)
3.015: Destination:
3.015: Source:C:\WINDOWS\system32\SETA3.tmp (5.1.2600.2622)
3.015: Destination:C:\WINDOWS\system32\winsrv.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETA4.tmp (5.1.2600.2622)
3.015: Destination:C:\WINDOWS\system32\user32.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETA5.tmp (5.1.2600.2622)
3.015: Destination:C:\WINDOWS\system32\authz.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETBF.tmp (5.1.2600.2938)
3.015: Destination:C:\WINDOWS\system32\rasadhlp.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETC0.tmp (5.1.2600.2938)
3.015: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\_000008_.tmp.dll (5.1.2600.0)
3.015: Destination:
3.015: Source:C:\WINDOWS\system32\SETCE.tmp (5.1.2600.2665)
3.015: Destination:C:\WINDOWS\system32\rpcss.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETCF.tmp (5.1.2600.2665)
3.015: Destination:C:\WINDOWS\system32\olecli32.dll (5.1.2600.0)
3.015: Source:C:\WINDOWS\system32\SETD0.tmp (5.1.2600.2665)
3.015: Destination:C:\WINDOWS\system32\ole32.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SETDA.tmp (6.0.2900.2869)
3.015: Destination:C:\WINDOWS\system32\inetcomm.dll (6.0.2900.2180)
3.015: Source:C:\WINDOWS\system32\SETED.tmp (2001.12.4414.311)
3.015: Destination:C:\WINDOWS\system32\mtxclu.dll (2001.12.4414.258)
3.015: Source:C:\WINDOWS\system32\SETEE.tmp (2001.12.4414.311)
3.015: Destination:C:\WINDOWS\system32\msdtcuiu.dll (2001.12.4414.258)
3.015: Source:C:\WINDOWS\system32\SETF0.tmp (2001.12.4414.311)
3.015: Destination:C:\WINDOWS\system32\msdtcprx.dll (2001.12.4414.258)
3.015: Source:C:\WINDOWS\system32\SETFE.tmp (5.1.2600.2744)
3.015: Destination:C:\WINDOWS\system32\umpnpmgr.dll (5.1.2600.2180)
3.015: Source:C:\WINDOWS\system32\SET102.tmp (6.0.2900.2869)
3.015: Destination:C:\WINDOWS\system32\shell32.dll (6.0.2900.2180)
3.015: Source:C:\WINDOWS\system32\SET109.tmp (6.5.2600.2749)
3.015: Destination:C:\WINDOWS\system32\quartz.dll (6.5.2600.2180)
3.015: Source:C:\WINDOWS\system32\SET116.tmp (5.1.2600.2818)
3.015: Destination:C:\WINDOWS\system32\gdi32.dll (5.1.2600.2180)
4.250: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
4.250: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0



Oh and also i have been playing COD ( Call Of Duty ) without a problem... computer doesnt overheat... doesnt reboot... had 1 blue screen and thats it... so its abit strange...

Anyway sorry for the VERY late reply and thats proberly my most latest blue screen dump if it is.... i came over it by looking in my windows folder


-Snipe44

 

Annnnnnnnyone?