Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Bsod


  • Please log in to reply
18 replies to this topic

#1 lordrohith

lordrohith

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 20 December 2007 - 07:15 PM

This started happening since I moved my computer upstairs. I tried system restore but to no avail. This only seems to happen when I play a game so I'm guessing something is wrong with my video card or its drivers. Maybe something fell out while I was moving the computer upstairs?

Error:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

*** STOP: 0x000000D1 (0x004FF358,0x00000002, 0x00000008, 0x004FF358)

PC STATS:

Windows: Windows XP5.1 (Build 2600) Service Pack 2
Internet Explorer: 7.0.5730.11
Memory (RAM): 448 MB
CPU: AMD Athlon™ 64 Processor 3400+
CPU Speed: 2405.7 MHz
Sound card: Realtek AC97 Audio
Display Adapters: SiS 760 | NetMeeting driver | RDPDD Chained DD
Screen Resolution: 1280 X 1024 - 32 bit
:
Network Adapters: SiS 900-Based PCI Fast Ethernet Adapter - Packet Scheduler Miniport
CD / DVD Drives: E: HP DVD Writer 640c | F: ASUS DVD-E616P3H | G: AC3093O GED576A
:
COM Ports: COM3 | COM1
LPT Ports: LPT1
Mouse: 3 Button Wheel Mouse Present
Hard Disks: C: 180.9GB | D: 5.4GB
Hard Disks - Free: C: 52.9GB | D: 726.6MB
USB Controllers: 4 host controllers.
Firewire (1394): 1 host controllers.
:
Manufacturer: Phoenix Technologies, LTD
Product Make: PW711AA-ABA SR1475CL NA520
:
AC Power Status: OnLine
BIOS Info: ATAT COMPATIBLE 011005 AWARD 42302e31
Time Zone: Central Standard Time
Battery: No Battery
Motherboard: ASUSTek Computer INC. Salmon
Modem: PCI Data Fax SoftModem with SmartCP


Really appreciate the help.

BC AdBot (Login to Remove)

 


m

#2 hamluis

hamluis

    Moderator


  • Moderator
  • 54,820 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:25 AM

Posted 20 December 2007 - 08:12 PM

http://support.microsoft.com/kb/810980

http://kadaitcha.cx/stop_err.html

Louis

#3 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 20 December 2007 - 09:26 PM

Thanks for the reply but none of those topics seem to apply to my situation. The BSOD only shows up when I'm playing a game, I've left my computer on overnight with utorrent running and it doesn't restart at all.

#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,571 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:25 AM

Posted 21 December 2007 - 05:28 AM

A corrupt device driver can cause 0x000000D1 errors. Try reinstalling your video driver.

How to update a Windows hardware driver
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 21 December 2007 - 02:19 PM

Thanks for the reply, I updated my video drivers but the restart still seems to occur. Really hope this won't require any new hardware.

#6 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,571 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:25 AM

Posted 21 December 2007 - 02:26 PM

Check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!" or "X" symbols.

You could also check your hard drive. Go Start > Run and type "chkdsk /r". It will probably ask for a reboot. This check can take many hours to complete.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#7 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 21 December 2007 - 02:33 PM

One of my network adapters named Hamachi Network Interface has an X next to it. Also a few days ago I had a device related to my webcam that had a ! next to it but since I don't use my webcam much I uninstalled it. I'll check my harddrive next.

#8 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 21 December 2007 - 02:55 PM

Hm, I tried the chdsk /r command and it said something about the drive being locked and that it can check only after a restart. So I restarted but I didn't see anything at all.

#9 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,571 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:25 AM

Posted 21 December 2007 - 03:29 PM

Try chkdsk again but use "chkdsk /p" this time.

0x000000D1 errors can also be caused by a damaged pagefile:

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a) and re-enter the settings that you wrote down in step cool.gif. Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.


The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#10 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 21 December 2007 - 05:07 PM

Followed all those steps and everything seemed to be working fine, but the BSODs haven't stopped yet.

#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:25 AM

Posted 21 December 2007 - 08:08 PM

The network device is a concern - try those drivers first.
Next, try updating your audio drivers (the second most common issue with games IME)
Next, try this free program to test your RAM: http://www.memtest86.com/
Next, try this procedure to reset your pagefile:

Use this technique to "reset" your pagefile:
a) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c) Reboot (this will remove the pagefile from your system)
d) Then go back in following the directions in step a) and re-enter the settings that you wrote down in step cool.gif. Follow the steps all the way through (and including) the reboot.
e) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.


If this doesn't fix it, then it's probably best to dig in and try and locate the .dmp file for the BSOD (search your hard drive for files ending in .dmp). Once you locate them, follow this procedure to perform an analysis of the memory dump: http://forums.majorgeeks.com/showthread.php?t=35246
Post back with the results of the memory dump and we'll take a look at to see if it reveals anything that will help.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#12 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 22 December 2007 - 12:34 PM

Followed all those steps, the results of the memtest86 are http://img140.imageshack.us/img140/3238/memtest86001wv0.jpg and http://img523.imageshack.us/img523/8913/memtest86002zf2.jpg

And these are the results for a few minidumps from yesterday:


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: eeff0000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e6a74, address which referenced memory

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




READ_ADDRESS: eeff0000

CURRENT_IRQL: 2

FAULTING_IP:
nt!CcSetVacbLargeOffset+76
804e6a74 8b38 mov edi,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: WINWORD.EXE

LAST_CONTROL_TRANSFER: from 804e6c1a to 804e6a74

STACK_TEXT:
b4acafa0 804e6c1a 84c0fe40 00000000 00000000 nt!CcSetVacbLargeOffset+0x76
b4acafb8 804e74fe 84c0fe40 00000000 00000000 nt!SetVacb+0x28
b4acb044 804e7844 84821468 00000000 00000000 nt!CcGetVacbMiss+0x1c0
b4acb07c 8055d7b8 00821468 00000000 00000000 nt!CcGetVirtualAddress+0x94
b4acb114 f72a9368 849736f8 b4acb1c8 000001ff nt!CcCopyRead+0x2b2
b4acb1f0 f72a9016 84b9cba0 849f5008 00000001 Ntfs!NtfsCommonRead+0xcc2
b4acb290 804edfe3 84c73020 849f5008 84ce9e20 Ntfs!NtfsFsdRead+0x22d
b4acb2a0 f734a459 b4acb2e8 804edfe3 84c743f8 nt!IopfCallDriver+0x31
b4acb2a8 804edfe3 84c743f8 849f5008 b55172b4 sr!SrPassThrough+0x31
b4acb2b8 b54d36b6 849f62b8 84c119e0 804edfe3 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
b4acb2e8 80570e16 849728b0 849f5008 849736f8 amon+0x46b6
b4acb390 8053ca28 00000e84 00000000 00000000 nt!NtReadFile+0x580
b4acb390 804fe29d 00000e84 00000000 00000000 nt!KiFastCallEntry+0xf8
b4acb42c b54d426c 00000e84 00000000 00000000 nt!ZwReadFile+0x11
b4acb468 b54d4c7e 00000e84 838f3028 000001ff amon+0x526c
b4acb48c b54d32c7 838f3008 00000000 80577301 amon+0x5c7e
b4acb4d8 804edfe3 849728b0 849f62a8 849f62a8 amon+0x42c7
b4acb4e8 80577672 84cebe18 84a81214 b4acb690 nt!IopfCallDriver+0x31
b4acb5c8 805b390a 84cebe30 00000000 84a81170 nt!IopParseDevice+0xa12
b4acb650 805afdeb 00000000 b4acb690 00000240 nt!ObpLookupObjectName+0x56a
b4acb6a4 8056a3b1 00000000 00000000 38a64c00 nt!ObOpenObjectByName+0xeb
b4acb720 8056ad28 b4acb868 001200a9 b4acb83c nt!IopCreateFile+0x407
b4acb77c bf8507ba b4acb868 001200a9 b4acb83c nt!IoCreateFile+0x8e
b4acba88 bf83a2ce e24ed398 b4acbaac 00000000 win32k!bCreateSection+0xe9
b4acbae0 bf83a1ad e24ea570 e2532928 e253292c win32k!EngMapFontFileFDInternal+0xc6
b4acbaf8 bf83a1d5 e24ea570 e2532928 e253292c win32k!EngMapFontFileFD+0x15
b4acbb0c bf85127f e2532918 00000000 bf85126d win32k!bttfdMapFontFileFD+0x23
b4acbb20 bf8b8248 00000000 e2532918 00000001 win32k!ttfdSemQueryFontTree+0x12
b4acbb48 bf8b143f 00000000 e2532918 00000001 win32k!PDEVOBJ::QueryFontTree+0x34
b4acbb84 bf8b2824 b4acbcec b4acbc98 84808c58 win32k!PFEOBJ::pfdg+0x6a
b4acbc20 bf808227 b4acbd0c b4acbca8 e1bd06b8 win32k!RFONTOBJ::bRealizeFont+0x1c
b4acbcb0 bf80828f e1bd0598 00000000 00000002 win32k!RFONTOBJ::bInit+0x29a
b4acbcc8 bf8eccb0 b4acbd0c 00000000 00000002 win32k!RFONTOBJ::vInit+0x16
b4acbce4 bf8ecc5f 00000000 4854414d 00000000 win32k!ulGetFontData2+0x17
b4acbd04 bf8ecc22 e39db660 4854414d 00000000 win32k!ulGetFontData+0x48
b4acbd48 8053ca28 87210f1c 4854414d 00000000 win32k!NtGdiGetFontData+0x26
b4acbd48 7c90eb94 87210f1c 4854414d 00000000 nt!KiFastCallEntry+0xf8
0609fd94 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
amon+46b6
b54d36b6 ?? ???

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: amon+46b6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: amon

IMAGE_NAME: amon.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46440bc2

FAILURE_BUCKET_ID: 0xA_amon+46b6

BUCKET_ID: 0xA_amon+46b6

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


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 004ff358, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 004ff358, address which referenced memory

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




READ_ADDRESS: 004ff358

CURRENT_IRQL: 2

FAULTING_IP:
+4ff358
004ff358 ?? ???

PROCESS_NAME: Idle

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f36a0b61 to 004ff358

FAILED_INSTRUCTION_ADDRESS:
+4ff358
004ff358 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80548ef8 f36a0b61 000000b5 8054901c 84b47418 0x4ff358
80549000 804ff517 80551d80 80551b20 ffdff000 0xf36a0b61
8054902c 80540f7d 80552180 00000000 0006b0b5 nt!KiTimerExpiration+0xaf
80549040 80551b20 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
80549050 80540ef6 00000000 0000000e 00000000 nt!KiIdleThread0
80549054 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+af
804ff517 5f pop edi

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiTimerExpiration+af

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTimerExpiration+af

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTimerExpiration+af

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


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 004f8e41, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 004f8e41, address which referenced memory

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




READ_ADDRESS: 004f8e41

CURRENT_IRQL: 2

FAULTING_IP:
+4f8e41
004f8e41 ?? ???

PROCESS_NAME: csrss.exe

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to 004f8e41

FAILED_INSTRUCTION_ADDRESS:
+4f8e41
004f8e41 ?? ???

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: fffffffff6d2ea98

STACK_COMMAND: dds F6D2EA98-0x20 ; kb

STACK_TEXT:
f6d2ea78 004f8e41
f6d2ea7c 00000008
f6d2ea80 00010206
f6d2ea84 00000010
f6d2ea88 e1da9198
f6d2ea8c 00000010
f6d2ea90 f6d2eaac
f6d2ea94 bf801713 win32k!SetWakeBit+0xb2
f6d2ea98 84ad5ae0
f6d2ea9c 00000002
f6d2eaa0 00000000
f6d2eaa4 e1d6b690
f6d2eaa8 7fffffff
f6d2eaac f6d2ead4
f6d2eab0 bf801232 win32k!TimersProc+0xeb
f6d2eab4 e1da9198
f6d2eab8 00000010
f6d2eabc 804fd968 nt!ZwDeviceIoControlFile
f6d2eac0 00000001
f6d2eac4 00000000
f6d2eac8 0000000d
f6d2eacc 00000000
f6d2ead0 00000001
f6d2ead4 f6d2ed30
f6d2ead8 bf88dba7 win32k!RawInputThread+0x634
f6d2eadc 00000022
f6d2eae0 006dfff4
f6d2eae4 bf801077 win32k!NtUserCallOneParam
f6d2eae8 00180016
f6d2eaec bf9901f4 win32k!`string'
f6d2eaf0 00000000
f6d2eaf4 84c668c8


FOLLOWUP_IP:
win32k!SetWakeBit+b2
bf801713 ebe2 jmp win32k!SetWakeBit+0xb2 (bf8016f7)

SYMBOL_NAME: win32k!SetWakeBit+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!SetWakeBit+b2

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!SetWakeBit+b2

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

Edited by lordrohith, 22 December 2007 - 12:35 PM.


#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:25 AM

Posted 22 December 2007 - 06:34 PM

Well, the memory test shows some errors - so that's something that has to be dealt with first. If the memory is bad, then attempts to access the bad areas can cause the BSOD with almost anything that's running on the system.

In order to determine which stick or which slot is causing this, you'll have to test all the sticks in one slot. If some come out good - then likely the slot is good. If all come out bad, then it may be that the slot is bad. In which case, try the other slots to see what results you get there.

As for the dump files - the first one references Microsoft Word and NOD32 - so they may be an issue. But we can't tell for sure until the memory is replaced. The second and third one's reference Windows system files - which is usually indicative of another, hardware related problem (although it can be an issue with Windows, but it's not as likely as a driver/hardware issue is).
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 lordrohith

lordrohith
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:25 AM

Posted 22 December 2007 - 09:28 PM

Thanks for the reply but regarding what you said about determining which slot/stick is causing the problem, how would I go about doing this? Would I have to open up my computer and check? Sorry, I am just a complete noob when it comes to computer hardware.

Edited by lordrohith, 22 December 2007 - 09:31 PM.


#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:25 AM

Posted 23 December 2007 - 10:22 AM

Presuming it's an HP, then here's a link to the mobo specs: http://h10025.www1.hp.com/ewfrf/wc/generic...57657&lc=en

Look at the link above and identify the the DDR memory slots in Figure 1 and Figure 2.
Shut down and unplug the system from the wall
Locate the DDR memory slots on your motherboard and determine if there's one or two sticks in the slots.

Let us know how many sticks are there.

If there's only one, you'll need to purchase a new stick of memory to replace that one (it will be a 512 mb chip in this case).

If there's 2 sticks - then you'll have to test each stick singly in each slot.
If a stick fails in both slots, it's likely that that stick is bad
If a stick fails in one slot only - then it's likely that that slot is bad

So, the combo's are:
Stick 1 in slot 1
Stick 1 in slot 2
Stick 2 in slot 1
Stick 2 in slot 2

Hopefully one of the sticks tests good in both slots - that'll mean that the slots are good (and you won't need a new motherboard)
Then the other stick should test bad in both slots - indicating that the stick is bad.

Once you determine which it is/what you need - we'll likely refer you to the memory configurator at Crucial to select new RAM ( http://www.crucial.com). What you'll be likely to need is DDR RAM (not DDR2) at speeds of PC2700 or PC3200.

For this system you'd:
Unplug the system from the wall
Open up the case
Ground yourself on the metal of the case frame with one hand
With the other hand remove one of the chips (there are clips at each end of the stick)
Let go of the ground (after putting the chip down on a non-conductive surface
Plug the computer back in (leave the side off and keep kids and pets away from it)
ReRun the memory tester
Then start this all over with the next stick.

If you only have 1 stick of RAM in the computer, then the problem is solved for you
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users