[rshaffer61]

OK now lets run some diagnostics as you originally wanted to do.
First let's check the hd integrity by doing the following.

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this finds and fixes any problems

[Advertisements]

I have run the Chkdsk /r.

It says the volume is clean.

Thanks

[jds2207]

I have run the Chkdsk /r.

It says the volume is clean.

Thanks

[jds2207]

Unfortunately, I am still getting BSOD! Same STOP codes as before.

[rshaffer61]

OK lets move on to the next step:

Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions



Revised and Simplified:


Do you have a valid XP CD?

If so, place it in your CD ROM drive and follow the instructions below:

• Click on Start and select Run... type sfc /scannow (note the space) (Let this run undisturbed until the window with the blue progress bar goes away)

SFC - Which stands for System File Checker,
retrieves the correct version of the file from %Systemroot%\System32\Dllcache or the Windows installation source files, and then replaces the incorrect file.
If you want to see what was replaced, right-click My Computer and click on Manage. In the new window that appears, expand the Event Viewer (by clicking on the + symbol next to it) and then click on System.

[jds2207]

I have run "sfc /scannow" and there were no errors found.

Thanks.

[rshaffer61]

Ok going off post 10 lets check your system services to see if it is causing the BSOD.

Lets see what you have in your startup services area

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

[jds2207]

I have tried this. I made it through one startup but received a BSOD while in windows. The code was:

STOP: 0x00000050 (0xBA570000, 0x00000001, 0x804F4BBE, 0x00000000)

On the next bootup I received BSOD with code:

STOP: 0x0000007E (0xC0000005, 0x8AA361C4, 0xBA56FB04, 0xBA56F800)


One thing I did notice. Firefox is not loading. However, when I went through post #21, I was able to get firefox to load before receiving the first BSOD.

Thanks

[rshaffer61]

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

What I'm looking at is the highlighted part first so lets check that as it is the most likely to cause a lot of errors and BSOD's..


If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[jds2207]

I have run memtest86+-2.11.iso with 5 passes. I do have errors. Through 5 passes, I have 13 errors. Here is the information I have on screen

Top left:
Intel Core 2 2394 MHz
L1 Cache: 32K 33250 MB/s
L2 Cache: 4096K 15960 MB/s
L3 Cache: None
Memory: 2006M 2823 MB/s
Chipset: Intel GM965/GL960 (ECC: Disabled) - FSB: 199 MHz - Type: DDR-II
Settings: RAM: 332 MHz (DDR665) / CAS: 5-5-5-15 / Dual Channel


Also, below the first line I have the following:

Tst Pass Failing Address Good Bad Err-Bits Count Chan
3 0 0004f378c78 - 1267.5MB 40404040 40c04040 00800000 1



Does this mean it is a RAM issue? I think I am finally happy to see an error because the problem is starting to come to light!!

Thanks.

[rshaffer61]

I have run memtest86+-2.11.iso with 5 passes. I do have errors. Through 5 passes, I have 13 errors. Here is the information I have on screen

Bad memory.
If you have more then one memory module you may want to test them individually to see if they both or just one is bad.
If only one module i think we may have actually found the root to your issue. Bad memory can cause all your issues and with a little repair work after it is replaced you should be as good as new.

[jds2207]

OK great! This will sound very naive but how do I go about determining if I have more than 1 memory module.

If I have two, do I take one out and run memtest and then switch the memory modules and run memtest a second time to see if one of them has no errors?

Also, what would be your recommendation for RAM. I am using Windows XP.

Thanks again.

[rshaffer61]

On the bottom of the laptop you will find a latch marked as Ram or Memory.
Take the screw out and the latch will come off. You will then be able to see the module or modules at that point.
Let me know.
Crucial shows the memory for that system HERE

[jds2207]

I have installed new RAM. I ordered from Crucial and it came very quickly and the installation went well. Unfortunately, I still have a BSOD!!!

This time, the code is:

STOP: 0x0000007E (0xC0000005, 0x8AB771C4, 0xBA56FB04, 0xBA56F800)

[rshaffer61]

Is this happening on bootup or after starting windows?
The explanation of this error is as follows:

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

Can you get a new Event Viewer log please so i can see the exact reason.

[jds2207]

Hi,

The BSOD seems to be happening very sporadically. Sometimes it happens on bootup. Sometimes I can log in to windows and then the BSOD comes in Windows. The stop codes vary as well. The ones I have received thus far are:

0x0000007E

0x0000007B

0x00000050

I will try to get the Event Viewer log for you. I am having issues getting into Windows at the moment. Even starting in safe mode isn't always working.


I am beginning to get a bit overwhelmed. If I brought the laptop into a shop, what actions would they even be able to do at this point beyond what I can do via your directions?