New
#11
its not under warranty..it behaves crazily..around 75 t0 80 c gpu temp,it will crash
its not under warranty..it behaves crazily..around 75 t0 80 c gpu temp,it will crash
its not under warranty.i use msi afterburner & speedfan to monitor temp..around 70 to 80 c gpu temp the display will crash
That is a high heat. You may go for a cooling pad for laptops.
I have informed it to a dell personnel, I hope he will visit your thread shortly.
thanks for the info.i m using cooling pad
Hi imnsu,
As referred by “Arc”, I have gone through the entire thread and I would suggest you to follow the below mentioned steps:
Check whether the BIOS version is updated or not? If not then kindly update the current BIOS version for this computer. To update the BIOS of your computer, follow the below mentioned steps:
·Go to http://www.dell.com/support/drivers/us/en/19/DriversHome/NeedProductSelection?fkey=Drivers_PS
·Put in the system’s Service Tag and choose the Operating System.
·Select the BIOS and download the latest Version of BIOS.
·Flash the BIOS and check if the system is working fine.
If the issue still persists then I would recommend running Dell Diagnostics. In order to run Dell Diagnostics from Hard Drive, follow the mentioned steps: Restart your computer. When the DELL™ logo appears, tap <F12> immediately. In the boot device list, highlight Boot to Utility Partition and press <Enter>. Under Dell Diagnostics Main Menu (see Dell Diagnostics Main Menu), select the extended test. If you get any error code, make a note of the error code.
If Dell Diagnostics passes, then try booting your system in” Safe Mode”. Start your computer and start tapping F8 continuously. Highlight "Safe Mode" from Windows Advance Options and press enter. See if your Dell computer works fine in Safe Mode.
Please reply with results.
i have the latest bios version of a12 as given in dell site.is there any latest version to that?
i have run the diagnostics & it gave battery as error
at the same time i wanna tell u that i need a proper driver for my wifi..since i have changed my motherboard i am not getting the proper driver from dell website
someone pl help me..i have attached the zip file
Hi,
I want to confirm whether you received an error code “PSA 1000-0213” as CMOS battery failure or was it simply battery failure?
An out of date BIOS can cause any of these CMOS battery failure error codes. In this case try reinstalling BIOS by clicking on the URL mentioned: http://www.dell.com/support/drivers/us/en/19/DriverDetails/DriverFileFormats?DriverId=R301434&FileId=2731117857
After reinstalling BIOS, try to run the Diagnostics again and if you still get the same error code then I would suggest you to check if the motherboard purchased was compatible or not. Else replace the system CMOS battery for this specific symptom.
To search for the Wi-Fi driver, can you please tell me the type of Wi-Fi card you are using on this new motherboard?
Hi.
Please uninstall:
If you are overclocking, please restore back to factory clocks and uninstall:Code:Start Menu\Programs\TuneUp Utilities 2012\All functions Public:Start Menu\Programs\TuneUp Utilities 2012\All functions Public Start Menu\Programs\TuneUp Utilities 2012 Public:Start Menu\Programs\TuneUp Utilities 2012 Public Start Menu\Programs\AVG PC Tuneup 2011 Public:Start Menu\Programs\AVG PC Tuneup 2011 Public Start Menu\Programs\AVG PC Tuneup 2011\Utilities Public:Start Menu\Programs\AVG PC Tuneup 2011\Utilities Public
Please download and install MSE Microsoft Security Essentials - Free Antivirus for Windows & run a full scan and remove anything that it finds.Code:Start Menu\Programs\MSI Afterburner NSU-LAPTOP\NSU:Start Menu\Programs\MSI Afterburner NSU-LAPTOP\NSU
BSOD Anaylze
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA BSOD Index
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
To make sure that hard drive is good run disk check following the tutorials below:Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Yusra\Downloads\imnsu\imnsu\091212-23712-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03062670 Debug session time: Wed Sep 12 15:07:00.463 2012 (UTC + 6:00) System Uptime: 1 days 4:28:22.993 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ........................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {2d10050, 1, 7feef98f5db, 8} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45ea5 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 0000000002d10050, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: 000007feef98f5db, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000008, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cc100 0000000002d10050 FAULTING_IP: +3261613139356131 000007fe`ef98f5db ?? ??? MM_INTERNAL_CODE: 8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002e2d7bb to fffff80002e9d1c0 STACK_TEXT: fffff880`066a2ab8 fffff800`02e2d7bb : 00000000`00000050 00000000`02d10050 00000000`00000001 fffff880`066a2c20 : nt!KeBugCheckEx fffff880`066a2ac0 fffff800`02e9b2ee : 00000000`00000001 00000000`02d10050 00000000`00000001 00000000`112f35d0 : nt! ?? ::FNODOBFM::`string'+0x45ea5 fffff880`066a2c20 000007fe`ef98f5db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`01f5e170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ef98f5db STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+45ea5 fffff800`02e2d7bb cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+45ea5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3 FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+45ea5 BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+45ea5 Followup: MachineOwner ---------
- Disk Check by Brink
- Hard drive scan usings SeaTools SeaTools | Seagate both long and short tests.
You should run memtest86+ on each stick for 8 passes preferably overnight.
Let us know your results