PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) where win32k.sys was indetefied. I have also goten 0x0000004e, 0x000000BE, 0x0000001A
I thought it was that I had to small a powersupply but the I disconnected a HDD my CD-burner.
system is this:
Operating System
Windows XP Professional Service Pack 1 (build 2600)
2.07 gigahertz AMD Athlon XP (2600+)
NEC DVD_RW ND-1300A
WDC WD1800JB
764mb ddr memory( cant remember what brand atm)
msi gf4 ti4200 64mb
k7n2 delta-L motherboard
300w powersupply
That is what I have in now, I have aslo a 120gb hdd and a cd-burner but they arnt connected atm.
I have run a memtest 86 that havent found any errors with my ram.
I also get errors when I use programs thise seems to be random aswell :\
For some reason when I install driver updates for my gf4 ti4200 I get a msg that it hasnt past the xp test, is this normal or?
If anyone need any more info just ask and I will try to get it
NooNoo
April 2nd, 2004, 09:20 AM
Welcome to Windrivers Qerr
Run a check on your hard drive, scandisk with surface test option selected.
As for not passing the XP compatability, no big deal, just means they didn't send that version to ms for validation. You can get other versions that have been from Nvidia.
confus-ed
April 2nd, 2004, 09:37 AM
.. just means they didn't send that version to ms for validation. You can get other versions that have been from Nvidia.
Just for now .. maybe go get one that did/does !?! (at least it eliminates it) .. these all look like IRQ 'issues' when its misbehaving on a share ! ;) , IRQ for VGA should 'almost always' want be allocated in bios & not be sharing with anything else at all..
LaSERCHiPs
April 2nd, 2004, 01:01 PM
Have you update all XP files and drivers?
Make sure the Bus Mastering drivers are up to date before installing the video drivers...
Did this just suddenly occur or is this off a fresh install?
Qerr
April 5th, 2004, 10:18 AM
NooNoo: I ran a chckdisk if thats what you mean by scandisk( I couldn't find any scandisk options)
and as for the driver I dl it with the msi live update program.
I cant quiet remember when it startet but I think it started after I put in my new motherboard(hope it isnt the motherboard again, had a problem with it earlyer had to send it in and get a new one) and cpu.
LaSERCHiPs
April 5th, 2004, 11:56 AM
So you have XP errors everywhere after replacing the mobo...
If you haven't done so you'll need to update/replace the HAL for the new mobo...you will continue to get these errors unless the mobo was the same model and brand name or you reinstall XP
Qerr
April 5th, 2004, 06:11 PM
HAL what is that -_-;?
but any way I got pissed at my pc so I formated c and reinstalled xp, will let you know how it goes(if that was the problem).
LaSERCHiPs
April 5th, 2004, 06:42 PM
HAL = Hardware Abstraction Layer
Definition: A windows XP service that provide basic input/output services such as timers, interrupt, and mutliprocessor management for computer hardware.
The HAL is a device driver for the motherboard circuitry that allows different families of computers to be treated the same by Windows XP Operating System
Hal.dll is file needed to be updated...
This maybe the cause of your problem....Re-installing should fix your problem
Can you give me the model # of the mobo old and new
Qerr
April 6th, 2004, 11:40 AM
well reinstalling xp didnt work, so far I have had
Norton Anti Virus .... Well I would first dump this program....I hate Norton...
Memory_management
0x0000001A
and
0x0000008E
win32k.sys
Well I did some research and there are tonnes of people receiving this error...
The majority of the problems appear to RAM related...
I know you probably don't want to do this but...Try it anywaze
Lower the speed of the RAM down in the BIOS...Perhaps the RAM isn't as fast as stamped
Other people have had to switch brand names of RAM...Use the recommended type posted by the manufacture of the mobo.
Next solution is...
in the BIOS change the RAM timing from "Optimal" to "Sync" ... if you have the option
And finally use 44.03 Detonator Driver if this is compativle with your Video Card...I think it is...People say that this has help out....
Hope this helps...
Qerr
April 6th, 2004, 01:13 PM
I could ditch norton but then I would need another anti virus and firewall program.
as for the memory tips I'll try them out.
I did run a memtest86 that didnt find anything.
I got another error now ^_^
Irql_not_less_or_equal
0x0000000A
I wish that it could be just one or two errors instead of 10+ ^_^;;
RaMoNeIrO
April 12th, 2004, 09:23 AM
Hello guys!
I came across this forum looking to solve a problem I'm having, but looks like I might help you out.
The errors you described are most likely RAM related. I noticed you have a 768 Mb RAM, what means you have two sticks (512 + 256). Make sure they are the same brand, or, at least, the same clock. Try taking one out and runnig memtest. If no errors are found, that could do it.
Anyway, one of the erros is driver related. Some service that XP could not load, and thats exactly the error I'm getting. If you have any USB devices, like broadband modems or wireless interface throgh USB, make sure its has the latest drivers installed. At least, that seems to be what is causing my 1000007f, 00000008, 80042000 error.
Sorry about the English, but I'm from Brazil, and sometimes I can do some real stupid mistypes.
Hope I coul help!
See ya
bookmarkmns
April 30th, 2004, 06:30 PM
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.
NooNoo
May 1st, 2004, 08:54 AM
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.
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.
bookmarkmns
May 1st, 2004, 04:53 PM
Sorry sloppy thinking from me, Noo-Noo, that is the route to take. UNINSTALL first and then try the cards in a different order.
Qerr
May 1st, 2004, 09:32 PM
sorry for this long delay from me, but I have just tested my memory with memtest86 and I found no errors, so It isnt the memory in my pc. :\
I'm wondering if it is possible that a hdd can be the cause of the error.
It makes this odd, sort of hacking sound (not much tho, its only about 2-3 of this anomalitis in the sound, and I'm not sure if it is the hdd or another device) when it is almost done booting up.
I will see if I'm able to install windows on a nother hdd and see of it goes.
TripleRLtd
May 1st, 2004, 10:45 PM
sorry for this long delay from me, but I have just tested my memory with memtest86 and I found no errors, so It isnt the memory in my pc. :\
I'm wondering if it is possible that a hdd can be the cause of the error.
It makes this odd, sort of hacking sound (not much tho, its only about 2-3 of this anomalitis in the sound, and I'm not sure if it is the hdd or another device) when it is almost done booting up.
I will see if I'm able to install windows on a nother hdd and see of it goes. If you are hearing sounds from the hdd then almost "anything" is possible. Download the hard drive diag from your hard disk manufacturer and run the test before continuing problem solving. Listen: if the hard drive is going bad, you will lose everything if you continue unless you back up NOW!!!
So, try this first:
http://support.wdc.com/download/index.asp#dlgtools
wmicro
May 3rd, 2004, 04:46 AM
Here what to try is to remove all cards disconnect all drive except your floppy, hard drive and your video card and start your computer and see what and what code you received by Windows XP.
Also see this links on Windows XP Knowledge Base Articles on stop Error Messages Checklist at http://dynamicmember.us/wmtbb/index.php?showforum=23
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details. at
http://www.msicomputer.com/product/detail_spec/product_detail.asp?model=K7N2_Delta-L
SLOTS
One AGP (Accelerated Graphics Port) 1.5V 4x/8x slot
Five 32-bit PCI bus slots (support 3.3v/5v PCI bus interface)
One ACR (Advanced Communication Riser) slot
Qerr
May 3rd, 2004, 01:24 PM
What will happen if I have two xp installed simutanuasly on two different hdds
(both are in the same pc tho)
Can I choose from which to boot from?
Need to make sure that it isnt the hdd that is bad and to see if it is possible to solve the problem by just formating the whole hdd.
To wmicro: where in bios can I change voltage etc to the memory? Can check it out aswell, but I'm pretty sure it isnt the memory.
confus-ed
May 3rd, 2004, 01:37 PM
Re memory timings - experience tells me if they are 'bad' then setup spits the dummy & won't complete, I'd be off running some disk diagnostics like RRR mentions ..
& that seems much better & less bother than doing a tandem install (btw if you do another then 'pre-windows' it should give you a choice of which to run)
TripleRLtd
May 3rd, 2004, 01:45 PM
Geesh this thread is getting confus-ed http://forums.windrivers.com/images/smilies/wink.gif. I had to look back to see who started it and what the original problem was. http://forums.windrivers.com/images/smilies/rolleyes.gif
Qerr, go back to the WD link for the diag. You seem to want to do this the hard way. The download will fit on one floppy and take 90 seconds to test the drive. Remember, if you're drive is going bad, the more you play with it, the less chance you get at recovering data. So, let's be sure about the hdd first.http://forums.windrivers.com/images/smilies/thumbs.gif
wmicro
May 3rd, 2004, 02:58 PM
To start the ball rolling we must conclude on diagnosing the machine.
Windows NT, 2000, XP, XP professional and Windows 2003 and one of the secrets of the software is the reason behind the delay on starts up these Windows versions have a built in diagnostic sequence which every time window starts up going through the diagnostic sequence which you can’t see this is the reason of the long start up time. In the Linux OS version when you install the Linux you will see the diagnostic sequence live which you see everything testes accept for Windows in something fails in the diagnostic sequence you will get the error codes like these.
User confus-ed is on the right track “Re memory timings - experience tells me if they are 'bad' then setup spits the dummy & won't complete, I'd be off running some disk diagnostics like RRR mentions ..” and also so user TripleRLtd is on the right track also “go back to the WD link for the diag. You seem to want to do this the hard way. The download will fit on one floppy and take 90 seconds to test the drive. Remember, if you're drive is going bad, the more you play with it, the less chance you get at recovering data. So, let's be sure about the hdd first”.
These error codes, this sounds like more of a hardware problem then software and you tested the hard drive and test OK! I would disconnect that hard drive and install your Windows XP on another drive and see if this cure the problem if not I would incline it would be the motherboard and the reason behind this I have seen this, 4 times in my experience dealing with Windows 2000 and XP as confus-ed states it is timing’s problem.
The rule of thumb any type diagnosing from TVs to automobile computers you must diagnose using knowing good parts.
Also your Bios should be set to auto unless you changed it.
You can see better explanation in your user manual on voltage setup.
confus-ed
May 3rd, 2004, 03:05 PM
Just a note for both RRR & wmicro - folks here always want to do things the hardway ! :D - strangely even when several folks say the same thing many times the poster will 'have their own agenda' & want to do things their own way regardless, of whats already been said to them .. you'll have to grin & bear it ;), they don't know who knows what they are talking about, if they did they probably wouldn't be asking !
OK, I ran the diagnostics utility, both quick and extended testing and it found no errors.
How can I find out if the motherboard is the cause for the "random" reboot?
NooNoo
May 3rd, 2004, 05:44 PM
Qerr is your machine set to automatically restart on error? If so, please uncheck it. (Right click my computer, properties, advanced, startup and recovery button).
Then you can get the full bsod in all its glory and you can post exactly what these errors are.
What does event viewer have to say just after one of these reboots?
Qerr
May 3rd, 2004, 06:28 PM
What will happen if I delete the memory.dmp file? Will windows make a new one because atm it is 767mb in size and I'm unable to open it.
NooNoo
May 3rd, 2004, 06:29 PM
Wow! Nothing, delete away, it will recreate...
wmicro
May 3rd, 2004, 10:14 PM
To Qerr
The key is win32k.sys this is the root of the problem like I stated it is a timing problem, see more on the PC Boot Process - Windows XP. At http://dotnetjunkies.com/WebLog/unknownreference/articles/12284.aspx
On the file or driver call win32k.sys so to make it quite sample it sounds like a graphic card is your problem. See these links for better understanding.
See this one for understanding Windows program cannot predict that this will happen because there is no standard location for storing the GINA DLL chain at
http://www.anixis.com/products/ppe/techdoc/td00026.htm
What will happen if I delete the memory.dmp file? Will windows make a new one because atm it is 767mb in size and I'm unable to open it.
You need to enable 'small memory dump' .. goes searching on how .. Overview of memory dump file options for Windows 2000, for Windows XP, and for Windows Server 2003 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;254649) - 'ed's summary - Click Start, point to Settings, and then click Control Panel.
Double-click System.
On the Advanced tab, click Startup and Recovery
I'm coming to the conclusion that this is all just IRQ & resource issues for sure, as I said about two pages ago (less 'certainly' ;)).. this thread now is sooooooo complicated, due to having answered about three other peoples problems on the way .. that's its pretty difficult to find out just what is happening - if Qerr can manage a summary at this point of just where he might be 'at' :) - I think it'll certainly help (if it just helps me !)..
Qerr
May 4th, 2004, 08:15 AM
I have now enabled small dumps.
Well atm it looks like it is either some thing wrong with the motherboard, gfx card or IRQ and resourse problem as you think it is.
How can I got about checking thise 3 things?
Qerr
May 4th, 2004, 08:42 AM
Ok, just had a couple of BSoDs, and I need to know which program to use to open them
confus-ed
May 4th, 2004, 08:53 AM
Ok, just had a couple of BSoDs, and I need to know which program to use to open them
If you unchecked the 'restart automatically' bit as Noo says above, when you get a 'fatal' one it should get 'stuck' & the only way out is reset or on/off (you can get 'BSODs' that aren't fatal), the simplest answer is to write it all down !
& I'll answer your earlier questions while I'm at it as well ..
The only practical way (without specialist equipment), to check any PC part is to try it in conjunction with known working good ones (I think someone says earlier?) - not much help if you just have one pc !
As for IRQ conflicts the best way with that is to start with absolutely the minimum kit installed you can, get it working like that & then add back any additional cards that might be responsible for all this 'madness' .. (so just memory vga & hd, any 'onboard whatever' wants disabling in bios if you can work it out - this is also the time to try ACPI on or off, if you still can't get it going)
Qerr
May 4th, 2004, 09:12 AM
Its over a month since I made it so that the pc becomes a blue screen with the serius errors instead of just rebooting, but isnt there a way to read the logs?( I'm some what lazy when it comes to writing down all the stuff it sais. :)
As for the resolving if it as an IRQ problem, isnt there an easier way? :)
Because if I Have to install every thing again then I would have to wait intill this weekend :\
NooNoo
May 4th, 2004, 09:30 AM
Qerr, the bsod information is vital. Please write it down.
confus-ed
May 4th, 2004, 10:05 AM
..As for the resolving if it as an IRQ problem, isnt there an easier way? :) ..
No (well if there is, somebody please tell me ! then maybe I won't think the pay for this is so 'mean' ..) - this is one of the many things I do for a living - testing various pc part combos for 'assembly' manufacturers (folks who put a motherboard made by 'someone' with a video card by 'somebody else' with a NIC by 'yet another guy' etc) - they send me a big pile of parts & I test all the combos & drivers they come with & then they decide what they might want to ship (not always taking notice of what they paid me to do I might add, grrr.. - pressumably another tester somewhere can get it to work, maybe with other drivers ? or maybe I'm more picky or just thick ..) - if you can get hold of all the correct documentation it gets easier (aforementioned available resources by slot), but nobody seems to do that any more !
Often any BSOD gives pointers after a bit of googling ;)
Qerr
May 4th, 2004, 01:05 PM
Here is what the eventviewer sais about one of the BSoDs: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000bbd0, 0x00000002, 0x00000000, 0xf0ba9733).
Here is from the techical data of a BSoD, I suppose that is the info you want.
kmixer.sys - adress F035E683 base at F0350000, datestamp 3d6ddc1c
If you just need the info from the eventviewer then I got lots more :\
NooNoo
May 4th, 2004, 02:35 PM
Qerr do you have sp1 installed?
Is the video card or cpu overclocked?
Are all the event id entries for kmixer.sys?
confus-ed
May 4th, 2004, 03:20 PM
If all or at least many of the errors all relate to kmixer.sys that'll be coming from your onboard sound drivers (Realtek ALC650 Audio ?) either being corrupted or for whatever reason something else that's sharing whatever IRQ it has..
Try disabling all your onboard sound devices for a bit & see if it persists .. oh & at any point in this gloriously confus-ed thread is there any mention of you applying the appropriate Nvidia Nforce2 SPP chipset patch ? If you haven't do so as well, that'll have a big impact on IRQs etc going 'screwey' .. (this ties in with the earlier win32k.sys errors somebody remarked upon higher up the thread)
Qerr
May 4th, 2004, 05:49 PM
Yes, sp1 is installend, no neither the cpu or any thing else is ovcerclocked.
No the Kmixer is rearly in the error atlest realativly rear. :)
What patch? Where can I get it?
And the onboard sound card is the only sound card I have in the pc atm.
TripleRLtd
May 4th, 2004, 05:57 PM
Yes, sp1 is installend, no neither the cpu or any thing else is ovcerclocked.
No the Kmixer is rearly in the error atlest realativly rear. :)
What patch? Where can I get it?
And the onboard sound card is the only sound card I have in the pc atm. The point to disabling it in Bios setup is to see if any of your problems are solved. But, your stating that it rarely is the error, well....
Listen, you've got mucho problems seemingly. Have you tried a repair install, or better yet. saving any vital data and formatting? A squeeky clean install with problems will tell us a lot. Is this still under warranty?
Qerr
May 4th, 2004, 06:05 PM
Yes tried repair install, didnt help, I will try to do a clean install this weekend, but first I need to ereas, about 10-20gb of files :\
btw if I do the clean install will it solve any IRQ problems?
wmicro
May 5th, 2004, 12:22 AM
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/results.aspx?view=en-us&st=b&na=82&qu=win32k.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
NooNoo
May 5th, 2004, 05:18 AM
http://www.bev.me.uk/wd/edited10a.gif
Now, where were we?
Qerr
May 5th, 2004, 07:01 AM
I was going to try the Nvidia Nforce2 SPP chipset patch, but I need to know where I can get it.
this is for 2k, but xp is the same (http://support.microsoft.com/default.aspx?scid=KB;en-us;291806) something has been very very screwed over.
Qerr
May 5th, 2004, 04:08 PM
I have run checks on the memory and hdd(they where fine), so I'm wondering are there utilitys that can check the mother board and the gfx card?
ps. that microsoft link didnt tell me much :\
NooNoo
May 5th, 2004, 04:52 PM
Qerr you have formatted and reinstalled... you got these errors. There is nothing for it now but to test stuff by putting it in another machine. This could be as simple as a bad ide cable.... ram timings not set right, video card ram going bye bye.
You can no longer afford to be lazy about this.
Qerr
May 5th, 2004, 05:13 PM
I can test the video card tomorrow by pulling it out and put in my old one, if I can find it. but mother board? that migth be harder :\ I will see if I can find a way to test it. btw do I still need to check the hdd and memory in this way?
NooNoo
May 5th, 2004, 05:16 PM
hdd - change the cables for known good ones. ram you have already run memtest86 - how long for?
Qerr
May 5th, 2004, 06:44 PM
Passed 4 tests, that would be altest 1 hour on the 256mb, 1,5hours on the 512mb and when both was in it was about 2-3 hours I think.
NooNoo
May 6th, 2004, 03:36 AM
There are 7 tests in total - suggest you run it till all 7 are complete.
Qerr
May 6th, 2004, 08:50 AM
Is it ok to have both of the memsticks in at the same time or do I need to do one and then the other?
NooNoo
May 6th, 2004, 09:12 AM
You will need to do one, then the other and then BOTH together, yes 3 times. This is to ensure one stick is not mismatching with the other and causing your problems.
wmicro
May 6th, 2004, 09:47 PM
TO: Qerr
When NooNoo comes online and see if he agrees normally I don't updated the bios and unless there is a problem, however in your case you have many issues at hand.
With today’s new procedures of BIOS life updates online it is relevantly easy.
Caution: Anywhere in the update procedures you don’t understand, this reply back to this board, do not make a choice on your own and write down any error code if any.
• Online update BIOS/Driver/Firmware/Utility.
• Live Monitor auto-detects and suggests the latest BIOS/Driver/Utilities information.
• AP Version: 3.58 (2004/04/08) File size 3.295MB
DOWNLOAD THIS AND INSTALL IT
http://us-download.msi.com.tw/support/swr_exe/LiveUpdate358B1.exe
This ver (5.7) will fix all the below:
1. This is Award BIOS release.
2. This BIOS fixes the following problems of the previous version:
- Adds for Support Write ROMSIP use 4K in 2M/16,8,8,32 ROM.
- Adds for Support Write ROMSIP use 4K in 4M/64K ROM.
- Reduces much time to update ROMSIP with 4M flash bios.
- Verifies flash data after romsip update and will update data again if flash data error occurs
======
ver 5.6 11/13/2003
2. This BIOS fixes the following problems of the previous version:
- Supports Nvidia System Utility.
==========
ver 5.2 6/6/2003
2. This BIOS fixes the following problems of the previous version:
- Shows current systems memory channel information
- Updates DDR400 timing settings
- Removes "Reset Configuration Data" intem in the BIOS setup as chipset does not support it
Note: This BIOS cannot be used on K7N2 Delta-ILSR(MS-6570-030).
Nvidia standard driver for MSI VGA cards.
Nvidia Driver 45.32 for Win2000/XP/Server2003
http://us-download.msi.com.tw/support/dvr_exe/45.32_XP.exe
TripleRLtd
May 6th, 2004, 11:14 PM
Yes indeedy, Querr has a multitude of problems. And, if the Bios has not been updated as of yet, then YES, do it! Then remove everything but the video card and ONE module of ram. And run it for awhile.
Geesh, this one has been going on for too long, and has caused arguments amongst nomally civil "tech helpers" . Sometimes a motherboard IS just bad!!! So, since the Bios update has seemingly not been tried, and since this seems to be where ALL the problems have been found to be (after all the testing of the hdd and ram), maybe, just maybe: that is the problem!!!
So, how about a complete update as to what you have done so far, what you have tested: sort of a summary Querr!
Let's get to the bottom of this. And no, if there were a hardware or software all encompassing test for motherboards, that would make all of our jobs sooo much easier: but there ISN"T! It is all a system of troubleshooting steps right now, and the one who invents such a truly reliable device will be rich, indeed.
PS
wmicro: NooNoo is a woman, and our forum moderator.http://forums.windrivers.com/images/smilies/thumbs.gif
Qerr
May 7th, 2004, 02:20 AM
Well it looks like it might be the ram after all :\
Just ran the memtest on the 512mb stick and it came up with one error, here it is:
My pc also reboots without me telling it to do so (still have it to give me a blue screen when an error accours).
Qerr
May 8th, 2004, 08:14 AM
Just had a nother BSoD
stop: 0x0000008E (0xC0000005, 0xBF849C48, 0xF6D810C4, 0x00000000)
win32k.sys - address BF849C48 base at BF800000
Just had this one aswell.
DRIVER_IRQL_NOT_LESS_OR EQUAL
stop: 0x000000D1 (0x00000014, 0x00000002, 0x00000000, 0xF97C5253)
usbport.sys - address F97C5253 base at F97AB000, datestamp 3f04cf17
NooNoo
May 8th, 2004, 08:52 AM
try reapplying service pack1 (http://support.microsoft.com/?kbid=317326) for the usbport.sys error.
Otherwise you are looking at a driver conflict or irq conflct.
here is how to start troubleshooting the 0xD1 messages (http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_ottj.asp)
the 0x8E message is also sp1 related (http://support.microsoft.com/?kbid=325154)
NooNoo
May 8th, 2004, 08:54 AM
this registry fix needs to be checked for the 0x000000B8 (http://www.jsiinc.com/SUBL/tip5700/rh5782.htm) - yes I know it says 2000, but check the registry anyway.
Qerr
May 8th, 2004, 09:01 AM
In this HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Clusnet\Start
I'm only able to com to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\
I'm unable to find clusnet there.
How do I reinstall sp1?
NooNoo
May 8th, 2004, 09:02 AM
download it and double click it.
TripleRLtd
May 8th, 2004, 09:11 AM
download it and double click it.http://forums.windrivers.com/images/smilies/biggrin.gif (http://forums.windrivers.com/misc.php?do=getsmilies#)
Geesh, I just read this whole thing again, and we are back to reapplying service packs???? We've formated and reinstalled, tested ram and removed a seemingly bad modul. No cards in pc except for video? And STILL all these problems?
Let's go back a couple of days:
Qerr you have formatted and reinstalled... you got these errors. There is nothing for it now but to test stuff by putting it in another machine. This could be as simple as a bad ide cable.... ram timings not set right, video card ram going bye bye.
You can no longer afford to be lazy about this. Yes indeedy, Querr has a multitude of problems. And, if the Bios has not been updated as of yet, then YES, do it! Then remove everything but the video card and ONE module of ram. And run it for awhile.
Geesh, this one has been going on for too long, and has caused arguments amongst nomally civil "tech helpers" . Sometimes a motherboard IS just bad!!! So, since the Bios update has seemingly not been tried, and since this seems to be where ALL the problems have been found to be (after all the testing of the hdd and ram), maybe, just maybe: that is the problem!!!
So, how about a complete update as to what you have done so far, what you have tested: sort of a summary Querr!
Qerr
May 8th, 2004, 10:35 AM
When I first got thise BSoDs I first did a repair install of winxp, didnt work.
I then did a clean install, didnt work, I then did some research and I eventualy found this board. Since I got here I have tested the HDD, no errors, then the ram, where there was an error and the bad ram stick have been removed.
Still got the error. Some where in this time period I removed the sound card and the ethernett card I had in my pc.
I also got another BSoD.
PAGE_FOULT_IN_NONPAGED_AREA
STOP: 0x00000050 (0x89518CE4, 0x00000001, 0xF98C7503, 0x00000000)
NTFS.SYS - address F98C7503 base at F98A4000
well here is another update from me. last weekend I reinstalled windows, since so many of you said it was faulty driver or somthing like that. Now that didnt work, I could have upto 5 BSoDS during one hours, so I decided to change the gfx card, now I use an old ati radeon 7500. I installed it thursday night, and since then I have only had 2-3 BSoDs, but now I got some other problems.
The first problem is that the pc reboots with out be telling it( I have changed it so that is should show blue screen when there is a serius errror)
The secon is after the sceen has been turned off/gone to saving modus. When I then turn the screen back on it is black, I have tryed to turn of the back on the screen but that doesnt work and pushing the power button (for a very short time that is) in just turns the pc off. I have been told that the last problem is becouse the bios/windows is sett to turn the hdds of after a while but none of thise settings are on.
NooNoo
May 15th, 2004, 11:48 AM
Have you replaced the powersupply unit in the case?
Qerr
May 15th, 2004, 06:35 PM
No I have not
chingchooee
June 2nd, 2004, 01:09 AM
As the rest of the people in this thread, I've been getting the 0x8E errors. I deleted the partition currently on the HDD and formatted + installed XP integrated with SP1. For some reason, which I find odd because it has never done this before, XP automatically detects everything and installs drivers for everything. I'm sure it may be the drivers and I have no clue why it is installing everything to begin with. Some of the errors I get are 0x0000008E(0xC0000005, 0xBF87BDC6, 0xF3708BF0F, 0x00000000). Like I said, its a FRESH installed copy of XP and when I try to do something, I get this error. Anyone help?
LJP
June 18th, 2004, 06:26 AM
Ok... This only applies to people who have Norton Antivirus installed.
Your link comes up dead... can you describe the navigation or provide the document number?
I found it in that lovely link they provided you with...
Here is the much shorter printable version http://service1.symantec.com/SUPPORT/nav.nsf/pfdocs/2002120614533906?Open
LJP
June 18th, 2004, 06:33 AM
Thanks hehe... i was trying to be smart and parse the url with my own description.
Try it now, so much for the fancy stuff.
LJ
NooNoo
June 18th, 2004, 06:36 AM
As the rest of the people in this thread, I've been getting the 0x8E errors. I deleted the partition currently on the HDD and formatted + installed XP integrated with SP1. For some reason, which I find odd because it has never done this before, XP automatically detects everything and installs drivers for everything. I'm sure it may be the drivers and I have no clue why it is installing everything to begin with. Some of the errors I get are 0x0000008E(0xC0000005, 0xBF87BDC6, 0xF3708BF0F, 0x00000000). Like I said, its a FRESH installed copy of XP and when I try to do something, I get this error. Anyone help?Welcome to Windrivers chingghooee
If you have norton antivirus, refer to the post above.
Otherwise we need ALOT more information about your machine.
If this happened during setup then read here (http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315335)
If not, test your ram extensively anyway (http://www.memtest86.com/)
Other known suspects are network cards - UNINSTALL from Device Mangler FIRST!! the remove the card or if onboard disable and see if that improves things
windrivers.com
Copyright WebMediaBrands Inc., All Rights Reserved.