Whoiskeel - several errors in XP

I've just started getting this same problem about a week ago, BSOD every few hours or so, often while it is idling. I just re-formatted and it is still doing it.

abit kx7-333r
athlon 1800
512 kingston
radeon 8500le

I've installed no new hardware or software, it just started doing it one day. i ran memtest86 overnight, and no errors.

at first it was giving me win32k.sys errors. then once it said hptpro.sys, my raid driver...so i took the hd off of the raid ide, and put it on the normal one, reformatted, and no success.

when i run chkdsk i get this message:
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

so i run chkdsk/f, reboot, and doesn't help. i also tried disabling my virtual memory, reboot, then enable to no avail...i'm convinced it's hardware, but what hardware? page fault...it could be memory or virtual memory no? or something else acting up?

HELP!

Confus-Ed replied

Welcome to Windrivers whoisKeel :)

The chckdsk errors you are getting look to be symptomatic of whatever is making the BSOD's !!! so try running scandisk in safe mode whilst logged in as machine administator (the account that comes 'built-in') we need NO errors in the MFT (Master File table - a bit like a File allocation table under FAT only for NTFS) - without this 'good' windoze has no flipping chance whatsoever of working correctly, as every time it tries to access a file it'll get pointed to the wrong one ! (that's what the MFT is, kind of like an index in a book) .

BTW 'Chkdsk /f' can NOT be run sucessfully from within windows (chkdsk on its own will run but the '/f' bit can't), its a command line util & only really wants to be run at boot before windoze takes ownership of all the files - ticking the little checkboxes on the Scandisk options 'Automatically fix file system errors' & 'Scan for & attempt recovery of bad sectors' will do what 'chkdsk/f' can at the next boot. (Folks get confus-ed with its usage in 9x {which is glorified DOS};)).



Whoiskeel replied

Yes, i understand that...but i said chkdsk /f didn't fix the problem even after running during boot.

I was unaware that there was scandisk in winxp...i can't find it and windows help tells me it is no longer available. how can i access scandisk? it isn't under WINDOWS/ OR WINDOWS/SYSTEM OR WINDOWS/SYSTEM32 and it isn't listed under system tools, and i tried typing scandisk at the run prompt and no help there either.

also, is there are log file for chkdsk somewhere?

Confus-Ed replied:

Quote:

---

Originally Posted by whoisKeel

Yes, i understand that...but i said chkdsk /f didn't fix the problem even after running during boot.

I was unaware that there was scandisk in winxp...i can't find it and windows help tells me it is no longer available. how can i access scandisk? it isn't under WINDOWS/ OR WINDOWS/SYSTEM OR WINDOWS/SYSTEM32 and it isn't listed under system tools, and i tried typing scandisk at the run prompt and no help there either.

also, is there are log file for chkdsk somewhere?

---

No you are quite right & I was having an 'idiot moment' :knife: no bloody scandisk in your xp - (I use fat for speed & I put scandisk back in as the link from my computer {via the reg} as it works better for fat with large sector sizes - then I ran chkdsk seperately & was clicking the boxes to see what wording the check boxes came up with but put scandisk as that's what it says on 'my' box but no one elses when I click in tools :rolleyes: ) but the bit about running at boot is the important bit - sorry for the confus-ed-ness :rolleyes: ..

I can see why you think your problem is maybe hardware, win32k.sys is very often IRQ &/or memory range type errors - so sharing & the like or lack of 'good' - you have of course installed the VIA hyperion chipset patches ? As the board is VIA KT333 ..

Do you have any other devices than those mentioned & more to the point what's sharing IRQ's or memory that might be at issue ? (you can view that in device manager, view resources by connection) - sometimes if drivers get updated this can cause problems where none existed before & you might have to do a 'slot shuffle' of your pci cards as the assignments available to each slot can change as one driver gobbles anothers resources - this was happening staright after a re-install ? - but why the hell any of this stops chckdsk from running puzzles me ..

So you can start normally after this each time ? Can you see chkdsk trying to run ? or does it just let you tick the box & then 'error' at boot .. & the same in safe mode ?

I can answer the bit about chkdsk logs - you can find a sort of summary by looking at 'winlogon' in event viewer .. you ought to find something like this if it ran

Quote:

---

The event should look something like this.

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 2/29/2004
Time: 11:44:36 PM
User: N/A
Computer: ******
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is WinXPSP2.


A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 127 unused index entries from index $SII of file 0x9.
Cleaning up 127 unused index entries from index $SDH of file 0x9.
Cleaning up 127 unused security descriptors.

10265503 KB total disk space.
4754412 KB in 32877 files.
10060 KB in 1211 indexes.
0 KB in bad sectors.
89135 KB in use by the system.
53376 KB occupied by the log file.
5411896 KB available on disk.

4096 bytes in each allocation unit.
2566375 total allocation units on disk.
1352974 allocation units available on disk.

Internal Info:
60 88 00 00 33 85 00 00 62 be 00 00 00 00 00 00 `...3...b.......
45 00 00 00 00 00 00 00 9c 01 00 00 00 00 00 00 E...............
ae a6 8f 02 00 00 00 00 62 5a b1 0f 00 00 00 00 ........bZ......
34 b5 ff 02 00 00 00 00 00 00 00 00 00 00 00 00 4...............
00 00 00 00 00 00 00 00 f6 51 14 1c 00 00 00 00 .........Q......
90 12 07 ce 00 00 00 00 90 12 07 ce 00 00 00 00 ................
6d 80 00 00 00 00 00 00 00 b0 2f 22 01 00 00 00 m........./"....

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.

---

Bookmarkmns said:

Late read but a simple trick may help. Remove all your PCI cards, make sure thay are in different slots and try again. Where the cards go can be crucial and could account for some of the issues.

To which I replied:

I agree with that advice BUT IN 2K AND XP you must uninstall each card in device manager first. You can uninstall them altogether and shut down and remove them. Both XP and 2k don't like having hardware shifted around without warning - nics are exceptionally difficult.

To which Bookmarkmns said:
Sorry sloppy thinking from me, Noo-Noo, that is the route to take. UNINSTALL first and then try the cards in a different order.

Whoiskeel said:

ok...back to me :)

i ran powermax for maxtor drives, did the tests, and passed...so i did a low level format, which said it passed 'certified error free'.

then i tried to install windows AGAIN...and while formatting at about 30% it would try to reboot, but would hang...the disc was trying to read and the hard drive light was on. i couldn't reset or turn the power off.

i tried this 3 times and thought maybe it was power supply? so i unhooked one of my cd drives (burner) and got through the installation fine. i have installed ZERO drivers at this point and my pc runs like crap without the via drivers and ati drivers...gonna see if it crashes without any drivers.

here's my error list previously:
0x50 PAGE_FAULT_IN_NONPAGED_AREA
problem caused by win32k.sys

0x8E
0x0A
0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
problem casued by usbuhci.sys
0x24

that's FIVE freaking BSOD errors. i'm gonna run without drivers for awhile and see if that causes problems. when i run chkdsk within windows i still get:
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

i'm not even gonna bother with chkdsk/f or /r again cause it does absolutely nothing.

wmicro offered this general advice:

To user: Qerr, Mad Dad and whoisKeel
Here is what you need to fix your problem, which we all hope, sees these articles.

When you install Microsoft Windows XP, you may receive a STOP error message similar to one of the following during Setup:
STOP 0x0000008e or STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA sees this
http://support.microsoft.com/default.aspx?kbid=315335


834450 - "Stop 0x0000008E" error message in Win32k.sys when you use the keyboard to access a program menu in Windows XP Fixes an issue in Windows XP where, if you use the keyboard to access a program menu, you may receive a Stop error message. Requires that you install Windows XP Service Pack 1 and a hotfix to resolve the problem.
http://search.microsoft.com/search/....sys+windows+xp
==
Qerr 04-06-2004, 08:40 AM
0x0000008E win32k.sys Page_fault_in_nonpaged_area 0x00000050 navex15.sys

======
whoisKeel Yesterday, 05:46 PM 5-4-04
0x50 PAGE_FAULT_IN_NONPAGED_AREA problem caused by win32k.sys
===================
Mad Dad 04-26-2004, 06:04 AM
Memory Address 0xE8000000-0xE9FFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561 Memory Address 0xE8000000-0xE9FFFFFF NVIDIA GeForce FX 5600SE

oh wow, my own thread :)

ok, here's my update. i've been running for almost 24 hours now with no bsod. 1 of my cd-roms is detached. i've installed the newest via drivers, sp1, and the newest catalyst drivers. i have restore points in-between each one. i'm gonna wait a few days to install my creative drivers (sb live!). then wait a few more to start installing usb devices. i'm thinking that's when the errors will probably surface again.

question tho: how come i couldn't get through the install process w/o taking out a cd-rom drive? if all these problems were a result of a faulty power supply, i wouldn't get a BSOD would i? it would just cut off or reboot right?

on a side note, i've been running this machine for over 2 years now...last driver update/hardware added was my kodak camera drivers in december (xmas)...i don't understand how it could be a driver issue when nothing has changed at all...i'm confused :)

oh yeah, and i have looked at those microsoft links...i have run 2 different memory tests overnight (7 or 9 hours a piece). Doc Memory 2.0 and newest memtest86...no errors.

OK CDroms are ide devices. If they break down then they can cause all kinds of wierd errors. It could be the cable was bad or not connected right, the jumper was not on the right place or the logic board was simply having a fit. Add to that possible bios setting problems such as udma on a a device that works in pio mode and you can see there is a fair amount to test as to what went wrong.