[FAQ] PC auto restart/Blue Screen (BSOD)

Lowyat.NET forums

Lowyat.NET Kopitiam Garage Sales

Lowyat.NET Rules and Regulations FAQ Help Search Members

Welcome Guest ( Log In | Register )

Lowyat.NET -> Technical Support

Bump Topic Add Reply RSS Feed

123 Pages « < 67 68 69 70 71 > » Bottom

Outline · [ Standard ] · Linear+

[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views

Allamz	Mar 9 2009, 11:44 PM Show posts by this member only \| Post #1361
New Member Newbie 1 posts Joined: Mar 2009	Hello There, i'm having the BSOD from KL1.sys below is my dump file, any help will be much appreciated. http://rapidshare.com/files/207189187/Mini030809-02.zip.html Attached File(s) Mini030809_02.zip ( 26.3k ) Number of downloads: 8
Card PM	Report Top Like Quote Reply

yanouchi	Mar 10 2009, 11:22 AM Show posts by this member only \| Post #1362
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	Elop there, i'm having BSOD from sysdata.xml. Here is my dump file, hope anyone will help me... Keep restart pc everytime i want to click like recyle bin, my computer n etc.... Heres my win debuggers result..kinda newbie in this thing, thanks... » Click to show Spoiler - click again to hide... « Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini031009-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRVc:\websymbolshttp://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Tue Mar 10 06:38:54.625 2009 (GMT+8) System Uptime: 0 days 0:03:28.359 Unable to load image ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ... Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 80550ae2, b6054944, 0} * Kernel symbols are WRONG. Please fix symbols to do analysis. * WARNING: Unable to verify timestamp for nv4_mini.sys * ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* Probably caused by : nv4_mini.sys ( nv4_mini+50fd00 ) Followup: MachineOwner --------- 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: 80550ae2, The address that the exception occurred at Arg3: b6054944, Trap Frame Arg4: 00000000 Debugging Details: ------------------ * Kernel symbols are WRONG. Please fix symbols to do analysis. ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ********************************************************************* * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 45eef5eb EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt+79ae2 80550ae2 893b mov dword ptr [ebx],edi TRAP_FRAME: b6054944 -- (.trap 0xffffffffb6054944) ErrCode = 00000002 eax=e114d6e8 ebx=00000000 ecx=000001ff edx=e114d6e8 esi=8ad5e0a0 edi=00000010 eip=80550ae2 esp=b60549b8 ebp=b60549f8 iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297 nt+0x79ae2: 80550ae2 893b mov dword ptr [ebx],edi ds:0023:00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from 80550ac7 to 80550ae2 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b60549f8 80550ac7 00000001 b6054b1c 8000000b nt+0x79ae2 b6054a38 805731be e1162008 00000000 00000000 nt+0x79ac7 b6054a5c 80572d55 00000000 00000000 00000000 nt+0x9c1be b6054b38 80573070 00000000 e1fbf190 b6054b90 nt+0x9bd55 b6054b64 805733f4 00000000 e112d520 b6054b90 nt+0x9c070 b6054b94 80573590 b6054bb8 00000000 e1160840 nt+0x9c3f4 b6054c7c 80582402 e1160840 b6054bb8 00000000 nt+0x9c590 b6054d30 80574f22 fffffffe 0000000c 00000001 nt+0xab402 b6054d4c 804dd98f fffffffe 0000000c 00000001 nt+0x9df22 b6054d64 7c90eb94 badb0d00 0420fe58 00000000 nt+0x698f b6054d68 badb0d00 0420fe58 00000000 00000000 0x7c90eb94 b6054d6c 0420fe58 00000000 00000000 00000000 nv4_mini+0x50fd00 b6054d70 00000000 00000000 00000000 00000000 0x420fe58 STACK_COMMAND: kb FOLLOWUP_IP: nv4_mini+50fd00 badb0d00 ?? ??? SYMBOL_STACK_INDEX: b SYMBOL_NAME: nv4_mini+50fd00 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_mini IMAGE_NAME: nv4_mini.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- This post has been edited by yanouchi: Mar 10 2009, 11:23 AM Attached File(s)** Minidump.zip ( 18.68k ) Number of downloads: 8
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 10 2009, 11:29 AM Show posts by this member only \| Post #1363
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	QUOTE(yanouchi @ Mar 10 2009, 11:22 AM) Elop there, i'm having BSOD from sysdata.xml. Here is my dump file, hope anyone will help me... Keep restart pc everytime i want to click like recyle bin, my computer n etc.... Heres my win debuggers result..kinda newbie in this thing, thanks... Hi there, You are having conflicts with your Nvidia driver. Please remove the current version of your driver from your system and download the latest version for your system. Please update the information and status after you install a new version of your Nvidia driver. Thanks and regards.
Card PM	Report Top Like Quote Reply

yanouchi	Mar 10 2009, 12:53 PM Show posts by this member only \| Post #1364
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(francischuahcw @ Mar 10 2009, 11:29 AM) Hi there, You are having conflicts with your Nvidia driver. Please remove the current version of your driver from your system and download the latest version for your system. Please update the information and status after you install a new version of your Nvidia driver. Thanks and regards. already update new driver...try to update information with WinDBG, its not working..status say Debugee not connected. After restart for new driver no more BSOD
Card PM	Report Top Like Quote Reply

Dickong	Mar 11 2009, 10:00 AM Show posts by this member only \| Post #1365
Regular Senior Member 1,689 posts Joined: Jan 2003	QUOTE(francischuahcw @ Mar 5 2009, 01:07 AM) You have missing registry file which results your window failed to operate correctly. Try to use a Window CD and do a system repair to recover the damage and corrupted registry and it will be fine. http://www.geekstogo.com/forum/How-to-repa...ws-XP-t138.html Thanks I reinstall the whole window but now it seem to me when booting up become quiet slow, but no more bsod, wonder how long it take to boot window, i mean 1min or more. tq
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 11 2009, 11:53 AM Show posts by this member only \| Post #1366
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	QUOTE(Dickong @ Mar 11 2009, 10:00 AM) I reinstall the whole window but now it seem to me when booting up become quiet slow, but no more bsod, wonder how long it take to boot window, i mean 1min or more. tq Run a ScanDisk for your HDD. Bad sector may be the cause for slow boot up.
Card PM	Report Top Like Quote Reply

yanouchi	Mar 12 2009, 08:53 PM Show posts by this member only \| Post #1367
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(yanouchi @ Mar 10 2009, 12:53 PM) already update new driver...try to update information with WinDBG, its not working..status say Debugee not connected. After restart for new driver no more BSOD today it got worst....BSOD..i try in safe mode, still BSOD... here the error: IRQL_NOT_LESS_OR_EQUAL after that i try in safe mode, it error like this: nv4_disp.dll i think something with updating the new driver... then after that i try to restart again here the error: PAGE_FAULT_IN_NONPAGE_AREA
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 12 2009, 09:56 PM Show posts by this member only \| Post #1368
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	Possible for you to upload your minidump file here for me to assist? I would suspect problem with your graphic cards. Looking for minidump file Go to My Computer and locate C:\Windows\Minidump or C:\Minidump. Once you have the minidump folder, please zipped the whole folder and upload it here (using add attachement function) or other web hosting page mentioned below. Please provide the link to download your file. RapidShare Putfile megaupload No minidump file available!!!How?? Do the following if you did not find your minidump file (Window XP) Right click at My Computer Go to Properties Look at Advanced tab then go for Startup and Recovery Look at Settings and untick Automatic Restart Make sure that write debugging information is Small Memory Dump (64kb) (Window Vista) Right click at My Computer Go to Properties Look at Advanced System Properties tab then go for Startup and Recovery Look at Settings and untick Automatic Restart Make sure that write debugging information is Small Memory Dump (64kb) The next time BSOD occurs, a minidump file will be created. Further tutorial are available at http://forum.lowyat.net/topic/346230
Card PM	Report Top Like Quote Reply

yanouchi	Mar 12 2009, 10:21 PM Show posts by this member only \| Post #1369
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	Okay heres the attachment minidump. Right now i'm uninstall the nvidia driver, But the problem still there. Please help...thanks Attached File(s) Minidump.zip ( 197.32k ) Number of downloads: 12
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 13 2009, 12:09 AM Show posts by this member only \| Post #1370
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	QUOTE(yanouchi @ Mar 12 2009, 10:21 PM) Okay heres the attachment minidump. Right now i'm uninstall the nvidia driver, But the problem still there. Please help...thanks A few thing to clarified with me here. Please let me know are you using a PC or a laptop. QUOTE STACK_COMMAND: kb FOLLOWUP_IP: nt!MiMakeSystemAddressValid+94 805fb93a cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiMakeSystemAddressValid+94 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4418c079 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x7a_c0000005_nt!MiMakeSystemAddressValid+94 BUCKET_ID: 0x7a_c0000005_nt!MiMakeSystemAddressValid+94 Followup: MachineOwner --------- QUOTE STACK_COMMAND: kb FOLLOWUP_IP: nv4_disp+ac7d1 bf0be7d1 0bbf6a0c8944 or edi,dword ptr [edi+44890C6Ah] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nv4_disp+ac7d1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_disp IMAGE_NAME: nv4_disp.dll BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner QUOTE STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+107 80550ae2 893b mov dword ptr [ebx],edi SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExDeferredFreePool+107 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+107 BUCKET_ID: 0x8E_nt!ExDeferredFreePool+107 Followup: Pool_corruption --------- QUOTE ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". BUGCHECK_STR: 0x7a_c0000005 CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO PROCESS_NAME: dwwin.exe Above stated is the result from some of your minidump file. From what i can observe here you are having problem on your hardware and it is not your graphic card driver. Instead i would have suspect you are having a faulty motherboard or a defect ram. Some of the minidump file show you have a memory corruption and pointed to the INTEL_CPU_MICROCODE_ZERO which is something related to the processor cache memory. Would suggest you to run memtest86+ to check your RAM for stability. Please do a few round of full test and let me know the outcome of your RAM test before we troubleshoot further. Regards.
Card PM	Report Top Like Quote Reply

yanouchi	Mar 13 2009, 09:59 PM Show posts by this member only \| Post #1371
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(francischuahcw @ Mar 13 2009, 12:09 AM) A few thing to clarified with me here. Please let me know are you using a PC or a laptop. Above stated is the result from some of your minidump file. From what i can observe here you are having problem on your hardware and it is not your graphic card driver. Instead i would have suspect you are having a faulty motherboard or a defect ram. Some of the minidump file show you have a memory corruption and pointed to the INTEL_CPU_MICROCODE_ZERO which is something related to the processor cache memory. Would suggest you to run memtest86+ to check your RAM for stability. Please do a few round of full test and let me know the outcome of your RAM test before we troubleshoot further. Regards. okay already run the memtest86+, each of ram tested and 4 pcs tested together (3GB), passed all the 8 test. no error. I'm using pc. i found some solution for problem like this such as clean the dust on gc card, use eraser to rub at metal parts ram but still have that serious error message This post has been edited by yanouchi: Mar 14 2009, 07:31 AM
Card PM	Report Top Like Quote Reply

naq_saviola	Mar 15 2009, 03:17 PM Show posts by this member only \| Post #1372
Casual Junior Member 394 posts Joined: Aug 2007 From: putrajaya	elo.. my pc keep restat with this error, IRQL_NOT_LESS_OR_EQUAL wat is problem?how to overcome?
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 15 2009, 04:08 PM Show posts by this member only \| Post #1373
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	QUOTE(yanouchi @ Mar 13 2009, 09:59 PM) okay already run the memtest86+, each of ram tested and 4 pcs tested together (3GB), passed all the 8 test. no error. I'm using pc. i found some solution for problem like this such as clean the dust on gc card, use eraser to rub at metal parts ram but still have that serious error message Most probably is motherboard failure or CPU failure. Else, did you monitor your system temperature? Is it normal?
Card PM	Report Top Like Quote Reply

francischuahcw	Mar 15 2009, 04:09 PM Show posts by this member only \| Post #1374
Retired. Do Not Disturb Senior Member 2,152 posts Joined: Feb 2006	QUOTE(naq_saviola @ Mar 15 2009, 03:17 PM) elo.. my pc keep restat with this error, IRQL_NOT_LESS_OR_EQUAL wat is problem?how to overcome? Please follow my instruction in post #1368. Regards
Card PM	Report Top Like Quote Reply

naq_saviola	Mar 16 2009, 11:22 AM Show posts by this member only \| Post #1375
Casual Junior Member 394 posts Joined: Aug 2007 From: putrajaya	here the minidump.. http://www.savefile.com/files/2042528 i hv change to my previous bios, seems better.. but can u check 1st, tq2
Card PM	Report Top Like Quote Reply

jon (",)	Mar 16 2009, 07:51 PM Show posts by this member only \| Post #1376
Getting Started Junior Member 78 posts Joined: Oct 2008	Hey i need some help about my BSOD. I've been getting this problem quite frequent hope you can help me with this problem. Thanks in advance Attached File(s) BSOD.txt ( 16.28k ) Number of downloads: 10
Card PM	Report Top Like Quote Reply

jon (",)	Mar 16 2009, 10:05 PM Show posts by this member only \| Post #1377
Getting Started Junior Member 78 posts Joined: Oct 2008	Sorry, if I've posted the wrong minidump cause I translate it to .txt file. Here is the original file Attached File(s) Mini031609_02.zip ( 34.25k ) Number of downloads: 7
Card PM	Report Top Like Quote Reply

Zax_imtiyaz	Mar 16 2009, 11:00 PM Show posts by this member only \| Post #1378
New Member Junior Member 47 posts Joined: Jun 2008 From: Putra World Trade Centre	Bro, could u help me bout my BSOD?? Here's the file...try to go to safemode also BSOD minidump.zip ( 284.57k ) Number of downloads: 7
Card PM	Report Top Like Quote Reply

alnk	Mar 18 2009, 07:42 PM Show posts by this member only \| Post #1379
New Member Newbie 1 posts Joined: Mar 2009	hi there i have a problem too upon installing a cracked version of Dawn of War II (this requierd me to update a certain version of direct X which i'm not sure of) then my computer began to remarkably slow down the specs are as of follows Core 2 Duo 3.0 ghtz 2gb RAM Runs on windows XP SP3 (version 2002 according to the cd) After installing the game, i managed to use the computer for 2 days (with it slowing down considerably) on the third day upon login the Window's BSoD popped up and i manage to catch a glimpse of NOT_ENOUGH_PHYSICAL_MEMORY however i have 2 gb of RAM. What is my problem? At first i had trouble logging on to safemode as the same BSoD popped up however in the end i managed and am now backing up my files and copied my dmp file on. Please help...best if you sent me an email =] Added on March 19, 2009, 7:01 pmi took it to techies and they said my HDD was damaged replaed and now works fine This post has been edited by alnk: Mar 19 2009, 07:01 PM Attached File(s) Mini031509_01.zip ( 11.9k ) Number of downloads: 7
Card PM	Report Top Like Quote Reply

Crazyfool	Mar 21 2009, 02:54 PM Show posts by this member only \| Post #1380
Getting Started Junior Member 148 posts Joined: Apr 2008 From: Sarawak	good post.. so helpful, finally solve my problem!
Card PM	Report Top Like Quote Reply

« Next Oldest · Technical Support · Next Newest »

123 Pages « < 67 68 69 70 71 > » Top

Add Reply Options

Change to:

0.0329sec

0.18

6 queries

GZIP Disabled
Time is now: 25th December 2025 - 01:40 AM

All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)

Removal Request

Powered by Invision Power Board © 2025 IPS, Inc.