Re: shutting down problem
Could be an array of things, shutting down in general is quite bad if it's doing it itself but it's easy enough to wittle down. Does the computer actually shut down? Ie. closes all the programs, then logs you off, then shuts down the computer... or does it just stop dead and turn off?
Re: shutting down problem
just shuts down instantly
Re: shutting down problem
Is the cpu overheating? Have you checked all your temps graphics card etc? Do you have another PSU you can slap in to check to see if its a power problem?
Re: shutting down problem
Quote:
Originally Posted by
burtie
Is the cpu overheating? Have you checked all your temps graphics card etc? Do you have another PSU you can slap in to check to see if its a power problem?
what would be the best way of checking temps???
and it only shuts down if i am running more than
one program at a time other than that it stays on
until i shut it down.
Re: shutting down problem
Re: shutting down problem
have you overclocked your system? have you run memtest?
Re: shutting down problem
Quote:
Originally Posted by
circuitmonkey
have you overclocked your system? have you run memtest?
nope done nothing to it except updating the bios with abit flash menu,
and nope not done memtest.,and is there a site to downlload this?
on a side note this was a first at building a new comp,
so the temp side and mem and all that are vey new to me
so im trying to learn as much as poss.
Re: shutting down problem
Quote:
Originally Posted by
Darkclone
nope done nothing to it except updating the bios with abit flash menu
That's not from inside Windows is it?
Quote:
and nope not done memtest.,and is there a site to downlload this?
http://www.memtest.org/
Can you browse to "C:\Windows\Minidump" and tell me if you have any files in there?
Re: shutting down problem
Quote:
Originally Posted by
ezri
That's not from inside Windows is it?
http://www.memtest.org/
Can you browse to "C:\Windows\Minidump" and tell me if you have any files in there?
there are 6 files in there
and it was from inside windows
Re: shutting down problem
Okay make sure you don't update the BIOS inside Windows - always do it from DOS, either via a floppy disk or ideally from a USB stick. USB's are far more stable than floppys for doing that. I've seen so many broken motherboards in my time from updating BIOS's in Windows. Just a tip anyway.
Those files in the Mindump folder are dump files that are created when the machine reboots, and can be examined to find out what the cause of the shutdowns where. I'd say either ZIP them up and upload them somewhere so we can take a look at them for you and see what the problems are, or alternatively you can do it yourself. If you wanted to do it yourself then uou can then download the Debugging Tools for Windows. When you download and install that you can follow the next steps:
1. Open the program and click File menu, then "Symbols path"
2. Type in "SRV*c:\symbols*http://msdl.microsoft.com/download/symbols" without the quotes
3. Then click File -> Open Crash Dump and browse to C:\Windows\Minidump and open the latest crash dump
4. When you open it, it'll take a while to load in but when it does you'll be connected to the debugger
5. When you are connected type in "!anaylze -v" without the quotes to get info on why the computer rebooted.
It might take a while to reach step 5, sometimes it takes around 30 seconds so be patient. What this will do is give you a full page of information regarding the error that you have had. You should do that and paste the contents here so we can take a look at it, namely the filename that caused the problem and the actual BSOD message (such as IRQL_NOT_LESS_OR_EQUAL - it's generally near the top of the report).
Re: shutting down problem
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071208-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 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jul 12 07:46:40.703 2008 (GMT+1)
System Uptime: 0 days 0:01:39.702
Loading Kernel Symbols
.................................................................................................... ..............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {44052, 2, 1, 806e4a2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+20 )
Followup: MachineOwner
i think i done the stps right??
Re: shutting down problem
Looks like some information is missing. When you get to that point, you should type in "!analyze -v" without the quotes in the very bottom of the window that has a little text box to type into. The bottom will say " kd> " and you can type in next to that, so type it in there. When you type it in and press enter, give it about 30 seconds or up to 1 minute for it to print out more information - it sometimes takes a while to pull all the information from the dump file.
See this screenshot for what I mean.
Re: shutting down problem
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071208-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 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jul 12 07:46:40.703 2008 (GMT+1)
System Uptime: 0 days 0:01:39.702
Loading Kernel Symbols
.................................................................................................... ..............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {44052, 2, 1, 806e4a2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+20 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00044052, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806e4a2a, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00044052
CURRENT_IRQL: 2
FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLock+3a
806e4a2a 8902 mov dword ptr [edx],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from ba622849 to 806e4a2a
STACK_TEXT:
b4e5b7cc ba622849 8a4547c8 8a695601 b4e5b800 hal!KeAcquireInStackQueuedSpinLock+0x3a
b4e5b7dc ba6425b1 8a695668 e1a89988 8a695601 Ntfs!NtfsAcquireResourceExclusive+0x20
b4e5b800 ba6656df 8a695601 e1a89988 00000000 Ntfs!NtfsAcquireExclusiveFcb+0x42
b4e5b884 ba665b0a 8a695668 8a604100 00000001 Ntfs!NtfsFlushVolume+0x113
b4e5b924 ba652e37 8a695668 8a394008 b4e50000 Ntfs!NtfsCommonVolumeOpen+0x341
b4e5ba00 804ef095 8a604020 8a394008 8a6a7160 Ntfs!NtfsFsdCreate+0x14d
b4e5ba10 ba6de876 8a394018 8a633538 8a6a7160 nt!IopfCallDriver+0x31
b4e5ba5c 804ef095 8a6a6878 00000001 8a394008 sr!SrCreate+0x150
b4e5ba6c 80581f6e 8a65fe18 8a3b32c4 b4e5bc04 nt!IopfCallDriver+0x31
b4e5bb4c 805bddc0 8a65fe30 00000000 8a3b3220 nt!IopParseDevice+0xa12
b4e5bbc4 805ba448 00000000 b4e5bc04 00000040 nt!ObpLookupObjectName+0x53c
b4e5bc18 80574ec1 00000000 00000000 afd5f801 nt!ObOpenObjectByName+0xea
b4e5bc94 80575838 01cef810 80100080 01cef7b0 nt!IopCreateFile+0x407
b4e5bcf0 80577f02 01cef810 80100080 01cef7b0 nt!IoCreateFile+0x8e
b4e5bd30 8054086c 01cef810 80100080 01cef7b0 nt!NtCreateFile+0x30
b4e5bd30 7c90eb94 01cef810 80100080 01cef7b0 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01cef808 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsAcquireResourceExclusive+20
ba622849 5d pop ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsAcquireResourceExclusive+20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45cc56a7
FAILURE_BUCKET_ID: 0xA_W_Ntfs!NtfsAcquireResourceExclusive+20
BUCKET_ID: 0xA_W_Ntfs!NtfsAcquireResourceExclusive+20
Followup: MachineOwner
---------
this better
Re: shutting down problem
Quote:
Originally Posted by
Darkclone
BugCheck 1000000A, {44052, 2, 1, 806e4a2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+20 )
...
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: svchost.exe
...
SYMBOL_NAME: Ntfs!NtfsAcquireResourceExclusive+20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
That's much better thank you :) Unfortunately your BSOD (IRQL_NOT_LESS_OR_EQUAL) is one of the most common around, however the good news is it is normally a result of dodgy drivers but there is a possibility is could be hardware.
Can you go through the other dump files you have, and record the information above that I've quote'd, as those are the important bits. Some of the other dump files might help us a bit more to solve your problem.
Re: shutting down problem
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 8a6335bc, The pool entry we were looking for within the page.
Arg3: 8a6343bc, The next pool entry.
Arg4: 0bc0fbe0, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 8a6335bc
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
PROCESS_NAME: RPS.exe
LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb
STACK_TEXT:
b40ba52c 8054a583 00000019 00000020 8a6335bc nt!KeBugCheckEx+0x1b
b40ba57c 8054a95f 8a6335c4 00000000 b40ba5bc nt!ExFreePoolWithTag+0x2a3
b40ba58c b303a506 8a6335c4 89ac53c4 8a6335c8 nt!ExFreePool+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
b40ba5bc b303d99e 8a6335c8 b306232a 8a6335c8 css_dvp+0x15506
b40ba604 8054a2b1 0000004c 80563c20 80563c44 css_dvp+0x1899e
b40ba64c 8054a75f 00000001 00000000 89ad3004 nt!ExDeferredFreePool+0x2ab
b40ba68c 8054a95f 89ab8c78 00000000 b40ba6cc nt!ExFreePoolWithTag+0x47f
b40ba69c b303a506 89ab8c78 00000000 89ad3004 nt!ExFreePool+0xf
b40ba6cc 89ad3004 89ac548b 89ac53c4 00000000 css_dvp+0x15506
b40ba6d0 89ac548b 89ac53c4 00000000 01ad3004 0x89ad3004
b40ba6d4 89ac53c4 00000000 01ad3004 00000016 0x89ac548b
b40ba6d8 00000000 01ad3004 00000016 8840db75 0x89ac53c4
STACK_COMMAND: kb
FOLLOWUP_IP:
css_dvp+15506
b303a506 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: css_dvp+15506
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: css_dvp
IMAGE_NAME: css-dvp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46141550
FAILURE_BUCKET_ID: 0x19_20_css_dvp+15506
BUCKET_ID: 0x19_20_css_dvp+15506
Followup: MachineOwner
---------