No Start up

[Bushy]

Hi all,

I purchased a new system about 6 weeks ago, since having this i have had numerous blue screen shutdowns, i put it down to win7 recently being released and bugs that would be fixed in updates. Over the last week i had what a lot of people have been experiencing which is the windows logo coming up then a blank screen. I don't have a cursor in screen though. I do a hard restart and then it loads up again sometimes no problem sometimes to the blank screen again.

Yestersay i turn on the machine and get nothing. All lights up, fans all run but nothing on the display. Not even the pre diagnostic screen which tells me what graphics card i'm running. No beep. The fans run at high speed until i have to hard restart and hope it comes on.

If it comes on the graphics info pops up after about 20 seconds then it sends me into startup repair, which then asks me if i would like to system restore. I said no first time then screen went blank. Second time i said yes, system restore did not kick in and the screen went blank again with the fans running at high speed.

Now it won't even start just high speed fans.

I haven't been able to get into the machine to get minidump files to attach.

I'm not too clever with computers but can easily follow instructions.

Please help somebody as i have call of duty to play!!! lol

 

[theog]

Hi

As PC is NEW take back to Retailer.

 

[Bushy]

its what i thought i'd have to do, its from a mail order company (overclockers) and i thought if i could find out what was up with it i.e a faulty component i could then get a new one sent out and then return the faulty component.

If i remove the graphics card and then start up will the onboard graphics take over? That way i could eliminate the graphics card.

 

[nickle]

Try running memtest86 from a bootable cd and a hard drive diagnostic from the manufacturer's web site before going through the hassle of sending the PC back.

Disable the graphics card driver in device manager and reboot the PC.

 

[Bushy]

it wouldn't do anything when i put memtest in either.

I have since spoken to overclockers support, they advised me to remove the graphics card, i have done this and everything seems fine.

So it was the graphics card.

Thanks all who helped.

 

[Bushy]

hi all just switched on this morning and the bugger did another BSOD, with the on board graphics.

Could someone please analyse the minidump attached?

It looks like total gibberish to me!

Thanks

 

[nickle]

The only definitive thing that I can find in the dump is that a memory managemnet error occured and it happened in a kernel thread while wmpnscfg.exe( Windows Media Player network sharing configuration) was running. Although wmpnscfg.exe may or may not be the victim of bad data being sourced from somewhere else in your system (misbehaving driver or whatever).

Run the memory test that I suggested previously and update bios and drivers found in device manager (network,video,motherboard,etc.).

If you are overclocking return the pc to the default settings for purposes of this debugging session.

It is your call whether you want to return the pc or not.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\nickle\AppData\Local\Temp\Rar$DI00.709\123009-16021-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Wed Dec 30 05:06:14.704 2009 (GMT-5)
System Uptime: 0 days 0:00:47.514
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, fffff7063fbef001, 12b25, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff7063fbef001
Arg3: 0000000000012b25
Arg4: fffff70001080000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41284
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnscfg.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002ad5a63 to fffff80002a7ef00
STACK_TEXT:  
fffff880`0790c7f8 fffff800`02ad5a63 : 00000000`0000001a 00000000`00041284 fffff706`3fbef001 00000000`00012b25 : nt!KeBugCheckEx
fffff880`0790c800 fffff800`02ab1b49 : fffffa80`07407ec8 fffff6fb`831fdf78 00000000`00000012 00000000`00000012 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`0790c840 fffff800`02ab24d4 : fffffa80`003822f0 00000000`00000003 fffff6fb`831fdf78 fffff706`3fbef000 : nt!MiTerminateWsle+0x29
fffff880`0790c880 fffff800`02ab222b : 00000000`00000003 00000000`00000012 80000000`12b65863 00000000`0000001c : nt!MiDeleteValidSystemPte+0x1a4
fffff880`0790c980 fffff800`02a52c74 : fffffa80`07407ec8 00000000`00000001 00000000`00000000 fffffa80`0000001c : nt!MiDeletePteRange+0x291
fffff880`0790ca00 fffff800`02a51efa : 00000000`00000001 fffffa80`07407b30 fffffa80`07407b30 00000000`00000001 : nt!MiDeleteAllHashMappings+0xe4
fffff880`0790ca40 fffff800`02d617af : fffff8a0`02a13550 00000000`00000001 00000000`00000000 fffffa80`0525a380 : nt!MmCleanProcessAddressSpace+0xa2
fffff880`0790ca90 fffff800`02d3acb8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x47f
fffff880`0790cb60 fffff800`02a7e153 : fffffa80`07407b30 000007fe`00000000 fffffa80`0525a380 fffffa80`0538c620 : nt!NtTerminateProcess+0x138
fffff880`0790cbe0 00000000`771d017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018f818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771d017a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`02ad5a63 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
Followup: MachineOwner
---------

 

[Bushy]

cheers pal, i have run the memtest and one of my sticks of ram has errors on it.

I'll return this to the supplier and get a return.

The machine was overclocked but i have reset it to optimized settings in the bios.

Obviously the ram was bad from the start,

thanks for your help.

 

[TGSoldier]

After your reset it to default, did you run the memtest? The errors could just be from unstable overclock..

 

[Bushy]

Yes memtest was run after overclock was reset.