wierd sudden reboot

Kanifee

Kanifee

Kanifee

Soldato
Joined
13 May 2007
Posts
7,004
Location
On the wagon, sorta
Hi all need some advice againso im here cap in hand once more.
today my pc just shut itself down for no apparent reason all of a sudden with no warning bosh black screen, and this is while i was sitting next to it on my second pc/server.
there was nothing runniong at the time and its pretty much a fresh install a week old with nothing but games, drivers, and some codecs installed it doesnt even get used to browse the net. so anyway ive checked the error logs and the only thing there is a warning that the last shut down was unexpectad and that its though i dont think i need informed of that!
one thing that sprung to mind is the vcore i have set on the cpu may be the problem as when i first got the cpu i was sure that i had wread the core was 1.25 but mine defaulted at 1.325 so i promptly knocked it back to 1.25 and it ran fine at the speed in my sig, so just to make sure what is stock volts for a 2140?


ps:cpu has been stable like that for about 1 month
 
You can download the Debugging Tools for Windows, which will help you identify the BSOD in question as you missed the info when it did restart. 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 if possible 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).

Also I would turn off the "Automatic Reboots" so you can identify problems from Blue Screens instead of just getting a reboot. You can disable this by right click on "My Computer" then click "Properties". Go into the "Advanced" tab and click the "Settings" button under "Startup and Recovery". About half way down the window that opens is a tick box that says "Automatic Reboots". Turn this off and click "OK". Now if you get another reboot caused from a system fault, you'll get information from a blue screen rather than nothing.

I would also consider maybe doing a Orthos 8 hour+ stability test if you have not already done it. Whilst your overclock is nothing massive, you have undervolted the CPU (although not by a huge amount) and it is worth testing that you have complete stability and you can rule out the CPU volts / overclock being the problem. You can download Orthos here if you don't have it already. It may not be the CPU though and you could be looking at the RAM. Is it set to the correct voltage? Also some RAM really doesn't like being overclocked much, and although you don't have a huge overclock on the RAM it just might not like it, especially if you have not adjusted the timings accordingly (what type of RAM do you have?).
 
ok not entirely sure what you need from this so ill give you it all :D
hope you see what it is

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8052bc10, The address that the exception occurred at
Arg3: 85c9b020, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
CI+cc10
8052bc10 108b550c528b adc byte ptr [ebx-74ADF3ABh],cl

TRAP_FRAME: 85c9b020 -- (.trap 0xffffffff85c9b020)
ErrCode = 00000002
eax=00000000 ebx=81c6fce0 ecx=00005a18 edx=00000000 esi=84a33870 edi=00000000
eip=8052bc10 esp=85c9b094 ebp=85c9b0e0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206
CI+0xcc10:
8052bc10 108b550c528b adc byte ptr [ebx-74ADF3ABh],cl ds:0023:0d190935=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

CURRENT_IRQL: 0

MISALIGNED_IP:
CI+cc10
8052bc10 108b550c528b adc byte ptr [ebx-74ADF3ABh],cl

LOCK_ADDRESS: 81d2e020 -- (!locks 81d2e020)

Resource @ nt!PiEngineLock (0x81d2e020) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x81d2e020
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805f0c08 to 8052bc10

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
85c9b0e0 805f0c08 85c9b1cc 85c9b1a0 84a33870 CI+0xcc10
85c9b158 805eabaf 00000000 85c9b1cc 00000001 CI+0xd1c08
85c9b178 805eb880 00000000 85c9b1cc 00000001 CI+0xcbbaf
85c9b1e4 81e51c7c 84a33840 895c0000 0003d000 CI+0xcc880
85c9b200 81dea7bd 84a33840 895c0000 0003d000 nt!SeValidateImageHeader+0x4d
85c9b26c 81dd8067 84a33840 84a29418 85f4c078 nt!MiValidateImageHeader+0x22e
85c9b38c 81dd7842 85c9b3e0 00000008 85c9b4f8 nt!MmCreateSection+0x76c
85c9b400 81c8c92a 85c9b528 00000008 85c9b4f8 nt!NtCreateSection+0x165
85c9b400 81c7e0d9 85c9b528 00000008 85c9b4f8 nt!KiFastCallEntry+0x12a
85c9b494 81ddda9d 85c9b528 00000008 85c9b4f8 nt!ZwCreateSection+0x11
85c9b554 81ddb6ae 80000048 81d11db0 82f71828 nt!MmCheckSystemImage+0x52
85c9b59c 81ddb820 85c9b684 80000048 85c9b5c0 nt!MiCreateSectionForDriver+0x95
85c9b5c4 81ddbabb 85c9b628 85c9b684 00000000 nt!MiObtainSectionForDriver+0x96
85c9b638 81ddd398 85c9b684 00000000 00000000 nt!MmLoadSystemImage+0x1bc
85c9b6b8 81ddbe13 88238000 85c9b728 00000000 nt!MiResolveImageReferences+0x237
85c9b730 81d86d33 85c9b8b8 00000000 00000000 nt!MmLoadSystemImage+0x514
85c9b924 81db5b76 00000000 85c9b900 85c9b954 nt!IopLoadDriver+0x360
85c9b968 81e37269 8786c550 00000001 8786c53c nt!PipCallDriverAddDeviceQueryRoutine+0x2f7
85c9b9a0 81e375f3 00000001 85c9ba98 81db587f nt!RtlpCallQueryRegistryRoutine+0x28e
85c9ba0c 81db5584 40000000 8000004c 85c9ba40 nt!RtlQueryRegistryValues+0x31b
85c9baf0 81db685a 00000000 85c9bd38 81d2d290 nt!PipCallDriverAddDevice+0x2ff
85c9bcec 81c07323 82f344d0 84a13650 85c9bd38 nt!PipProcessDevNodeTree+0x157
85c9bd44 81c78db8 00000000 00000000 82f71828 nt!PnpDeviceActionWorker+0x21b
85c9bd7c 81e25472 00000000 85c90680 00000000 nt!ExpWorkerThread+0xfd
85c9bdc0 81c9141e 81c78cbb 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CI+cc10
8052bc10 108b550c528b adc byte ptr [ebx-74ADF3ABh],cl

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: CI+cc10

FOLLOWUP_NAME: MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED_CI.dll

BUCKET_ID: IP_MISALIGNED_CI.dll

Followup: MachineOwner
---------
 
You must log in or register to reply here.
Back
Top Bottom