[rshaffer61]

Grrrrr
Graphics card.
Let me find the entry and see what we can do about it.

[Advertisements]

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.

[rshaffer61]

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.

[Meskis]

I don't know how many RAM stick there is, because I haven't seen it fromm inside, because it's laptop :/

P.S. I read a lot of forums, that have problem with this driver, in one forum I found, saying, that I should find earliar drivers, because there's no igxpdx32.dll

P.S.S.

The problem that everyone is having is in the igxpdx32.dll itself . When intel wrote the new driver it has a glich in the driver it's self . There nothing wrong with your hardware or anything dealing with the bios like I said it is the driver it's self any driver writtin from 2007 to now .

Can it be true?

Edited by Meskis, 12 August 2011 - 07:02 PM.

[rshaffer61]

No problem with finding the memory if you go ahead and run the test. That will tell us if we have a memory issue at least.

As far as the statement a older driver may fix the issue but i would rather save that as a last resort.

[Meskis]

Ok, I'll inform you tommorow.

[Meskis]

What should I post after that?

[rshaffer61]

Did it show any errors and how many passes did it make?

[Meskis]

Didn't tested it yet, because hadn't had a chance, tommorow I'll buy CD and try it.

[rshaffer61]

OK no problem I will be here.

[Meskis]

So, the results are:

Edited by Meskis, 15 August 2011 - 05:51 AM.

[rshaffer61]

Not a memory issue then.

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

[Meskis]

When I enter sfc /scannow to Run, it just opens black box which dissapears in few milisecnds, my windows is XP, so I couldn't upload that folder.

[rshaffer61]

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.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[Meskis]

Checking file system on C:

The type of the file system is NTFS.



A disk check has been scheduled.

Windows will now check the disk.                         

Cleaning up minor inconsistencies on the drive.

Cleaning up 426 unused index entries from index $SII of file 0x9.

Cleaning up 426 unused index entries from index $SDH of file 0x9.

Cleaning up 426 unused security descriptors.

CHKDSK is verifying file data (stage 4 of 5)...

File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

Free space verification is complete.

CHKDSK discovered free space marked as allocated in the

master file table (MFT) bitmap.

Windows has made corrections to the file system.



  81923432 KB total disk space.

  77819352 KB in 151087 files.

     51984 KB in 12163 indexes.

         0 KB in bad sectors.

    253956 KB in use by the system.

     65536 KB occupied by the log file.

   3798140 KB available on disk.



      4096 bytes in each allocation unit.

  20480858 total allocation units on disk.

    949535 allocation units available on disk.



Internal Info:

80 c9 02 00 bc 7d 02 00 f8 81 03 00 00 00 00 00  .....}..........

28 03 00 00 02 00 00 00 ad 05 00 00 00 00 00 00  (...............

24 b1 02 05 00 00 00 00 fc 09 37 68 00 00 00 00  $.........7h....

20 24 48 0a 00 00 00 00 ea 20 76 32 06 00 00 00   $H...... v2....

64 3f 56 3d 00 00 00 00 9c 74 7c ee 06 00 00 00  d?V=.....t|.....

99 9e 36 00 00 00 00 00 a8 39 07 00 2f 4e 02 00  ..6......9../N..

00 00 00 00 00 60 b7 8d 12 00 00 00 83 2f 00 00  .....`......./..



Windows has finished checking your disk.

Please wait while your computer restarts.





For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[rshaffer61]

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

Interesting... It found issues with the File System which indicates maybe this was or is part of the issue. Anymore BSOD's since Friday?