Computer Randomly Resets......

Hi, I'm have a real pain in the *** problem with my computer (of course why else would i post here lol).

I have no idea whats causing it, i can leave my computer on for days without it resetting but as soon as i try to install a program or a game it get to about 95% done then resets . Right now i managed to install Call of Duty 4 and Warcraft, yes I'm one of them lol, with no problems whatsoever but when i try and install any updates that's when it resets, just as its about finished the update.

I just put my computer in a new case, everything is cleaned out with new SHTC on gfx and processor. i have tested the ram with memtest, checked power connectors all is fine. (also i just reinstalled windows when i put it in the new case, it was needing done) so i know it can't be a virus or malware or even windows problem.

Sorry if its a bit long just trying to give as much info as possible.
any help would be greatly appreciated

Thanks guys

 

Anyone?

 

Hello & welcome to MG o0Toker0o :wave

Thats a very odd problem you have, even though it's a new windows install I would try Ccleaner. If you have any problems that'll get them, you need to run it until it says there are no issues just to make sure it's all gone .

If that doesn't help i'd update drivers, moniter my temps (http://www.lavalys.com/) to find them in Everest just go to computer then sensor.

Could you post you're spec, OS & system temps? Just to check everything is as it should be.

Hope this helps

:major2-Bit-Geek:major

 

thanks for the reply man.

I have ran ccleaner no avail, i thought it may have been my temps aswell but the last time i tried installing the update i was watching my temps and none of them (gpu, cpu, mobo hdd etc...) hit above 54 and it still reset, i also thought it maybe my psu but when it resets none of the fans stops or anything (exactly like hitting the reset button).

Specs attached

 

UPDATE:

I tried it again this morning, but this time i got a BSOD

Stop: 0x000000de (0x00000002, 0xe34cc8ac, 0xeb4cc8ac, 0x742108c0)

Driver corrupted pool used for holding pages destined for disk.

 

ok another update, i Debugged the mini dump and got

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


Loading Dump File [C:\WINDOWS\Minidump\Mini080309-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.090206-1316
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Aug 3 21:15:55.953 2009 (GMT+1)
System Uptime: 0 days 2:32:43.655
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DE, {2, e38fc3f0, eb8fc3f0, 742108c0}

Probably caused by : sr.sys ( sr!SrCleanup+b3 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 00000002
Arg2: e38fc3f0
Arg3: eb8fc3f0
Arg4: 742108c0

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xDE

PROCESS_NAME: Installer.exe

LAST_CONTROL_TRANSFER: from 80525207 to 8053767a

STACK_TEXT:
a9a54574 80525207 000000de 00000002 e38fc3f0 nt!KeBugCheckEx+0x1b
a9a545b8 804f7dc1 89a31d00 01000000 888aeca0 nt!MmPurgeSection+0x4f1
a9a545e4 804f8f03 89a31da4 a9a54678 00000000 nt!CcPurgeCacheSection+0x100
a9a54644 804f8e18 8887b710 a9a54678 000456ff nt!CcPurgeAndClearCacheSection+0x118
a9a54684 f7b55c6f 00000000 004f90e0 a9a54ae4 nt!CcSetFileSizes+0x249
a9a546ac f7b81c27 88825188 e14f90e0 e14f90d0 Ntfs!NtfsSetBothCacheSizes+0x71
a9a54710 f7b887f8 a9a54ae4 88825188 00000000 Ntfs!NtfsDeleteAllocation+0x380
a9a54780 f7b888a0 a9a54ae4 e14f9008 a9a54828 Ntfs!NtfsDeleteAllocationFromRecord+0x15a
a9a548ac f7b87aa1 a9a54ae4 e14f9008 e1777918 Ntfs!NtfsDeleteFile+0x245
a9a54ac8 f7b77d4d a9a54ae4 89ac7ac8 89b60348 Ntfs!NtfsCommonCleanup+0x1212
a9a54c40 804e13d9 89b31020 89ac7ac8 89b6e708 Ntfs!NtfsFsdCleanup+0xcf
a9a54c50 f7a41bbf 889429c8 89ac7ad8 a9a54ca0 nt!IopfCallDriver+0x31
a9a54c60 804e13d9 89b60290 e21b8280 89ac7ac8 sr!SrCleanup+0xb3
a9a54c70 8057b32f 889429b0 00000038 89c20ca0 nt!IopfCallDriver+0x31
a9a54ca0 8056f9a2 88996020 89b60290 00010080 nt!IopCloseFile+0x26b
a9a54cd4 8056faf5 88996020 00000001 89c20ca0 nt!ObpDecrementHandleCount+0xd8
a9a54cfc 8056fa1b e148c360 889429c8 000002dc nt!ObpCloseHandleTableEntry+0x14d
a9a54d44 8056fa65 000002dc 00000001 00000000 nt!ObpCloseHandle+0x87
a9a54d58 804dd99f 000002dc 01fdf354 7c90e514 nt!NtClose+0x1d
a9a54d58 7c90e514 000002dc 01fdf354 7c90e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01fdf354 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
sr!SrCleanup+b3
f7a41bbf 5f pop edi

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: sr!SrCleanup+b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sr

IMAGE_NAME: sr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480252c2

FAILURE_BUCKET_ID: 0xDE_sr!SrCleanup+b3

BUCKET_ID: 0xDE_sr!SrCleanup+b3

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

1: kd> lmvm sr
start end module name
f7a3d000 f7a4ef00 sr # (pdb symbols) c:\symbols\sr.pdb\9D5432B7234C4CD2A8F6275B9D9AF41F1\sr.pdb
Loaded symbol image file: sr.sys
Mapped memory image file: c:\symbols\sr.sys\480252C211f00\sr.sys
Image path: sr.sys
Image name: sr.sys
Timestamp: Sun Apr 13 19:36:50 2008 (480252C2)
CheckSum: 00012604
ImageSize: 00011F00
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0816.04b0
CompanyName: Microsoft Corporation
ProductName: Sistema operativo Microsoft® Windows®
InternalName: sr.sys
OriginalFilename: sr.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2108)
FileDescription: Controlador de filtro de sistema de ficheiros do 'Restauro do sistema'
LegalCopyright: © Microsoft Corporation. Todos os direitos reservados.


So according to that its system restore.... hmmm will switch it of and disable it, will post back with results

 

Ok tried disabling System restore, still get same BSOD and debugger still saying it was sr.sys :S

can i safely just remove the file?

this is really starting to annoy me lolz

 

I am afraid I am no good with RAM issues, LOL I am actually having some of my own atm :-D Nothing too serious though just annoying.

I am asuming you mean Celcius? 54 is fine for a GPU (well nVidia anyway :-D) but 54C is a little high for a CPU in my opinion & it way too hot for a HDD & mobo.

Heat is one of the main reasons HDD's fail, you wanna get at least an 80cm fan infront of you're HDD. If RAM is the cause then I cannot help, but if it isn't I have one last idea you're PSU. You should get yourself a digital mutimeter & start a thread in the hardware section asking how to test it, I would help but I was walked through it here myself LOL

:major2-Bit-Geek:major

 

2-Bit is right about the HDD there!!! Wow that's hot for a HDD ... my VelociRaptor only gets to 35 .... and that mobo temp isn't good either ... the CPU isn't too bad ... although it could definitely be better ... check your front to back air flow, (meaning don't leave the side off your case).

If you want, to get something to cool the HDD and don't want it to be too obvious you can go for THIS ... if you want a better one go for THIS

 

lol i think you misunderstood, i meant 54 (celcius) was the hottest temp, not that they were all at 54 lol,


Temperatures:
Motherboard 34 °C (93 °F)
CPU 33 °C (91 °F)

as for hdd i don't know but i wont imagine it will be that hot with a 140mm fan in front of it

My GFX card is sitting at 58 (celcius) (radeon hd 4850)

i managed to get it all installed by taking out one of the sticks of ram.... i still got the same error now and again but it was no where near as much as with both sticks in. do you think it still could be software related or have both my ram died? lol

bearing in mind like i said my computer runs absolutely fine, had it left on for 4 days straight, runs games no problem plays music hd movies, it just happens when i install stuff :S

 

LOL woops ... no the temps are ok lol ....... well theres always the simple solution ... format and reinstall

 

lol yea thats what i thought, when i formated and reinstalled this time, things will work perfect....... oohh how wrong i was lol.

Anyways i got Warcraft and Cod4 installed and they both running fine for now, so im happy lol, don't play any other games.

If it holds out till next month i will try reinstalling, if it still gets the same error will buy some new ram, (this stuffs pretty slow anyways lol). :-D