• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

bsod during winxp install

ok during winxp installation after the partition when it installs i get a bsod during installation called page_fault_in_nonpaged_area. Idk what could be wrong. I did transfer the pc from my friends house and his dad INSISTED it be in the trunk instead of me holding it.

amd 3500
nforce4
6600gt

btw i dont have a floppy drive


thanks
 
Originally posted by: thursday22dp
it was 2 threads and 2 problems....how would i run memtest exactly?

edit: does memtest just detect problems or fix them as well?

It detects problems, typically hardware problems.

Download the memtest86 cd iso, burn it, boot it, run it.

It's also THE SAME ERROR IN ALL 3 THREADS. :|
 
Originally posted by: thursday22dp
and if i dont have a cd burner?

Return your computer to the computer literate person you took it from.
Buy one.
Borrow one.
Dumpster dive for one.
Ask a friend to burn it for you.
Get a really small pin and "burn" it manually.
Get new RAM to test it out (although this isn't as conclusive as memtest86).
 
anyways, i ran a checkdisk which came out fine. Now i keep getting a slew of random bsods, most recent was ntfs.sys and that was pretty much all it said.
if i ran memtest and it found problems id still have to return my ram correct since it doesnt fix probs?

any other ideas? i was considering bringing it into comp usa
 
Originally posted by: thursday22dp
memtest has been running for 11 hours and 0 errors..any other ideas?or would errors show up later in the test?

Typically within the first pass or too..

It can sometimes happen if timings are too tight as well.

I had 3000 errors in 1:00 exactly..

slowed the timings WAY down and still had 4 errors after about 20 min.
 
i reset the bios before so everything is default so i doubt that would be a problem.

i was thinkin maybe the pieces are touching something so i might take most of it apart and rebuild it, any imput?
 
its the only other install disk i have

ok it got much farther this time and got close to the end of installation and then blue screened to irql not less or equal to(not sure on exact wording)

EDIT😱k just got ntfs.sys bsod
 
my psu is fine, the pc iself is only 25 months old. I use a sata HD btw. Im not sure on this but IDE cables count as ATA then ill swap the cd drive ones. I have 1 sata hd and 1 ide cd rom
 
oh yeah in he recovery console for xp disk i did a chkdks but all i can do is /p and /r how can i do a /f or is /f and /r basically the same?
 
U:\>chkdsk /?
Checks a disk and displays a status report.


CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/i] [/C] [/L[:size]]


volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentation
.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).

/L:size NTFS only: Changes the log file size to the specified number
of kilobytes. If size is not specified, displays current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index entries.
/C NTFS only: Skips checking of cycles within the folder
structure.

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.
 
What is your entire hardware setup? One solution you might try IF you're using 2 sticks of RAM is to take one out. I know with my motherboard, I had a problem using dual channel during XP installation. It would BSOD with the same error and I had to install with 1 RAM stick. Solved the problem, and then popped the RAM back in and all was well.
 
Back
Top