PC troubleshoot...need ugernt help..plz help!! :(

napster007

napster007

Padawan
Hi guys,

i'm having a problem in my PC since a long time and i really need ur help this time to figure this thing out. about 6 months ago i bought my new PC

CPU: Amd phenomII x4 955
MOBO: ASUS 785td-evo
ram: 4GB DDR3 1333
grphics: nvidia gt220

after running my PC for a while it started to give problems like physical memory dump every now and then when i was playing games and all. and one fine day my pc did not even start. My mobo was not powering up. so i replaced it with a new one MSI 890GXM-G65 and now i am facing these problems:

1.> When i tried to install windows 7, it during the first phase of installation when it copies files, the process suddenly stopped and said :"windows has detected a problem and has aborted installation to prevent damage to your computer"

2.> after many trials i managed to get it installed... and now many a times at the time of boot up, there's a physical memory dump and the PC keeps restarting.

3.> sometimes, the mobo is powered on, but with no display nor any boot up sound from the board.

can u guys please tell me what the problem is..... this is so frustrating... :-(
 
G

gk2k

gkbhat.blogspot.com
One reason for the problem might be a heating problem. Try removing your graphics card and then check.
 
coderunknown

coderunknown

Retired Forum Mod
another possibility is HDD getting lot of bad sectors. if you have a 2nd HDD, connect it parallel & than check for bad sectors from the other HDD.
 
desiibond

desiibond

Bond, Desi Bond!
when there is a memory dump or BSOD, did you get a chance to see what is causing it? the file name or error code etc should help.
 
OP
napster007

napster007

Padawan
my mobo is now booting fine.... and the windows 7 starts to install but, during installation everytime that i tried(>10) the process is stopped in between when windows is expanding files....

and a blue screen appears saying that a problem has occured and the installation has stopped to prevent damage to your computer.... i have already formatted my HDD

this is so frustrating......!!!!!! i kept my PC straight (as in it was lying down b4 as i was installin with my sade case open) and now it installed perfectly.... this is so bizzare!! what if the problem occurs again or gets worse?? any diagnosis??
 
Last edited:
asingh

asingh

Aspiring Novelist
For some reason only one of your memory dumps is running through..this is what I picked up...

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


Loading Dump File [C:\Users\ANIL SINGH\Desktop\memory_dumps_tdf\121310-17144-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8224b000 PsLoadedModuleList = 0x82393810
Debug session time: Mon Dec 13 03:01:17.034 2010 (GMT+6)
System Uptime: 0 days 0:00:08.096
Loading Kernel Symbols
...................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 824aa7da, 80786210, 0}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+109 )

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

0: 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: c000001d, The exception code that was not handled
Arg2: 824aa7da, The address that the exception occurred at
Arg3: 80786210, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!FsRtlAllocateExtraCreateParameterList+31
824aa7da 85c0 test eax,eax

TRAP_FRAME: 80786210 -- (.trap 0xffffffff80786210)
ErrCode = 00000000
eax=8bbffb10 ebx=00000000 ecx=00000003 edx=00000004 esi=00000004 edi=807862fc
eip=824aa7da esp=80786284 ebp=8078628c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210282
nt!FsRtlAllocateExtraCreateParameterList+0x31:
824aa7da 85c0 test eax,eax
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8ab86130 to 824aa7da

FAILED_INSTRUCTION_ADDRESS:
nt!FsRtlAllocateExtraCreateParameterList+31
824aa7da 85c0 test eax,eax

STACK_TEXT:
8078628c 8ab86130 00000000 807862fc 80786308 nt!FsRtlAllocateExtraCreateParameterList+0x31
807862ac 8ab836a8 80786310 01000000 84889008 fltmgr!TargetedIOCtrlGenerateECP+0x1c
80786314 8ab83abd 8587e6d8 8587e6d8 80786350 fltmgr!FltpNormalizeNameComponent+0x76
80786324 8ab83eb6 8587e6d8 00000000 8587e6d8 fltmgr!FltpCallNormalizeNameComponentHandler+0x7f
80786350 8ab84df4 0187e6d8 00000000 8587e6d8 fltmgr!FltpExpandShortNames+0x138
8078636c 8ab85505 85870000 00000000 85878efc fltmgr!FltpGetNormalizedFileNameWorker+0xae
80786384 8ab82765 8587e6d8 00000000 8587e6d8 fltmgr!FltpGetNormalizedFileName+0x19
8078639c 8ab6cb21 8587e6d8 00000000 00000000 fltmgr!FltpCreateFileNameInformation+0x81
807863cc 8ab6cfa3 8594e0ec 00000000 80786464 fltmgr!FltpGetFileNameInformation+0x321
807863f4 8ab9fc87 00736570 00000401 80786428 fltmgr!FltGetFileNameInformation+0x12b
80786444 8ab9fedd 85736570 80786464 00000020 fileinfo!FIStreamGetInfo+0x109
80786480 8ab66324 85736570 807864a4 17614ed7 fileinfo!FIPostCreateCallback+0x171
807864e8 8ab69512 00736510 85736510 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
807864fc 8ab69b46 85736510 8576c860 8078653c fltmgr!FltpProcessIoCompletion+0x10
8078650c 8ab6a29c 85736778 8576c860 85736510 fltmgr!FltpPassThroughCompletion+0x98
8078653c 8ab7d8c9 8078655c 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
80786588 822874bc 85736778 85772378 8587f084 fltmgr!FltpCreate+0x2db
807865a0 8248b62d b3cd52f3 80786748 00000000 nt!IofCallDriver+0x63
80786678 8246c1d7 856cb030 848bb870 85872488 nt!IopParseDevice+0xed7
807866f4 8249224d 00000000 80786748 00000240 nt!ObpLookupObjectName+0x4fa
80786754 8248a5ab 807868d4 848bb870 00000000 nt!ObOpenObjectByName+0x159
807867d0 824c55ee 807868fc 00000020 807868d4 nt!IopCreateFile+0x673
80786818 8228e42a 807868fc 00000020 807868d4 nt!NtOpenFile+0x2a
80786818 8228c7a1 807868fc 00000020 807868d4 nt!KiFastCallEntry+0x12a
807868a8 8240f5f7 807868fc 00000020 807868d4 nt!ZwOpenFile+0x11
80786904 8240f411 80786b30 00000000 80786928 nt!MiCreateSectionForDriver+0x7f
8078692c 8240ede6 80786998 80786b30 00000000 nt!MiObtainSectionForDriver+0x96
807869a8 823ee2c0 80786b30 00000000 00000000 nt!MmLoadSystemImage+0x1db
80786b9c 825fc853 00000001 00000000 80786bd4 nt!IopLoadDriver+0x386
80786be8 825f887b 8080fb78 8080a840 00000000 nt!IopInitializeSystemDrivers+0x163
80786c6c 825fde6f 0080a840 848239f0 84823680 nt!IoInitSystem+0x6de
80786d48 823d647c 80786d90 8245966d 8080a840 nt!Phase1InitializationDiscard+0xce4
80786d50 8245966d 8080a840 b3cd591b 00000000 nt!Phase1Initialization+0xd
80786d90 8230b0d9 823d646f 8080a840 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
fileinfo!FIStreamGetInfo+109
8ab9fc87 85c0 test eax,eax

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: fileinfo!FIStreamGetInfo+109

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME: fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18f

FAILURE_BUCKET_ID: 0x8E_BAD_IP_fileinfo!FIStreamGetInfo+109

BUCKET_ID: 0x8E_BAD_IP_fileinfo!FIStreamGetInfo+109

Followup: MachineOwner
---------
Click to expand...

It seems to be pointing towards bad memory. Can you run the system with just one RAM stick. Alternate the two if the problem persists.

Will try to run more dump file analysis tonight if I can manage. Do post back what happens.

EDIT:
Also, reset the CMOS once, so we baseline the system.
 
You must log in or register to reply here.
Top Bottom