Several errors in XP

for some reason I have goten several errors on my PC, here is some of them

Error code 1000008e, parameter1 c0000005, parameter2 bf8a2c76, parameter3 b9d1fbe4, parameter4 00000000.


Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

Error code 00000050, parameter1 88b64688, parameter2 00000001, parameter3 8052ec54, parameter4 00000000.

thise are not all, I have also goten

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

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.

Quote:

---

Originally Posted by NooNoo

.. 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..

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?

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.

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

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).

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

well reinstalling xp didnt work, so far I have had

Page_fault_in_nonpaged_area
0x00000050
navex15.sys

Memory_management
0x0000001A

and

0x0000008E
win32k.sys

and that is since yesterday evening :\ about 5 pm here now.

[QUOTE=Qerr]well reinstalling xp didnt work, so far I have had

Page_fault_in_nonpaged_area
0x00000050
navex15.sys

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...

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+ ^_^;;

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

Where to start?

I also have had this problem since assembling my first machine a few weeks ago....

XP Pro Service pack 1
Intel 2.5 Ghz
Soyo 845pe Lite motherboard
1 512 stick of RAM and 1 256
Western Digital Caviar 80GB HDD
425 Watt power supply
Nvidia GeForce FX 5600 (AGP)
Sony DVD RW
wacom tablet (my only usb device)
and also a cable modem running through a belkin router

...and when it runs, it runs great. Problem is (seemingly) random reboots. I've been researching my problem using the error codes and dumpchk data and the only thing I've found is small comfort that I'm not alone with this problem. Many threads citing the same errors, curiously most of them seem to be about 1-2 years old. This is the most recent thread I've found, so I registered and am posting.

Let me take a moment to say that I don't have as many "ComputerSmart Points" as others that I see posting, but I'm capable enough, and am always eager to learn whatever I need to to solve a problem.

In all the threads I've read, no one has come to a definitive solution.

This is the best thread I've read so far
http://forums.viaarena.com/messagevi...rc&STARTPAGE=1

A lot of people talk about RAM, but when it's changed the problems persist. I've run it with either and both of my sticks and still gotten the BSODS. Haven't run a memtest yet, though. Other people talk about IRQ assignments, and I think that's a possibility. ONly this morning have I started looking into reassigning my IRQs (my USB and VidCard share IRQ 16. IRQ 11 is empty, see this thread: http://www.annoyances.org/exec/forum/winxp/1005541276)

I've checked my voltages, flashed the bios, upgraded to SP1 (the first time it rebooted during the install, -curses!- and I had to reinstall from scratch). I've messed around in BIOS some, but not every corner.

At post I get a message flash by that tells me "no 80 pin conductor cable installed"...which is strange because I'm able to read/write to the HDD no problem (until BSOD, which happens if the machine is idle or busy). Replaced the cable, replugged it, everything, so I'm just going to ignore that problem, because if the cable isn't installed then how could it be working with the HDD, right? I know the diff. between a 40 pin and 80 pin, so I'm sure I've got the right cable installed.

Here's one thing that evryone seems to have in common, a GeForce card. Not everyone, but almost everyone. Mobo, chipset, processor, everything else seems to change (even W2K running instead of XP, but most commonly XP). Through an AGP slo, not PCI.

So, there's some more avenues I want to explore. Questions:
What can you tell me about this, from my Sys. Info screen-

I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

I/O Port 0x000003C0-0x000003DF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce FX 5600SE

Memory Address 0xE8000000-0xE9FFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xE8000000-0xE9FFFFFF NVIDIA GeForce FX 5600SE

IRQ 16 NVIDIA GeForce FX 5600SE
IRQ 16 Intel(R) 82801DB/DBM USB Universal Host Controller - 24C2

Memory Address 0xD0000000-0xDFFFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xD0000000-0xDFFFFFFF NVIDIA GeForce FX 5600SE

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce FX 5600SE

I/O Port 0x000003B0-0x000003BB Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce FX 5600SE

The error codes I'm getting are mainly the ones listed elsewhere in this thread, 1000007f, x050, x08e, IRQ not less or equal, and some pagefile faults....

Anybody have any ideas, is this thread still alive?

Thanks for anything.

Well, to over generalize....its either a faulty driver, faulty ram, or a faulty service
http://www.microsoft.com/resources/d...d_stp_ccgm.asp

Have you installed the Intel INF Update Utility?

Well, I ran memtest and guess what, my 512 stick came up with all kinds of errors. Why couldn't it have been the 256? Oh well, I'll send it back...

I hope that was the source of my BSODs.

DsLTech, I checked your link. It was the stop code I was getting the least, about paging, and I think it was a result of the bad RAM, a symptom, rather than a cause. Thanks.

hudsonsmith, yes I've installed the INF update, too.

Waiting for another BSOD, fearing it. But you know how it can be sometimes, once you actually verbalize the problem, the solution makes itself apparent. I wonder how many people figure out thier problems because they've posted them in a forum and actually written them out, made them literal and tangible, rather than a jumble of suspiscions and guesses shuffling around in thier head.

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!

Quote:

---

Originally Posted by Mad Dad

.. But you know how it can be sometimes, once you actually verbalize the problem, the solution makes itself apparent. I wonder how many people figure out thier problems because they've posted them in a forum and actually written them out, made them literal and tangible, rather than a jumble of suspiscions and guesses shuffling around in thier head.

---

:thumbs: That's the one ! So glad your issue is sorted or at least explained ;) now onto the next one ...

So .. 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};)).

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?

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.

---

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.

Quote:

---

Originally Posted by bookmarkmns

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.

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

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.

Quote:

---

Originally Posted by Qerr

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

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/d...l=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

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.

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)

Geesh this thread is getting confus-ed https://forums.windrivers.com/images.../2005/03/1.gif. I had to look back to see who started it and what the original problem was. https://forums.windrivers.com/images.../2005/03/1.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.https://forums.windrivers.com/images.../2006/04/1.gif

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.

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 !

The PC Boot Process - Windows XP.

http://dotnetjunkies.com/WebLog/unkn...les/12284.aspx

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?

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?

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.

Wow! Nothing, delete away, it will recreate...

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/unkn...les/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



http://www.i.u-tokyo.ac.jp/ss/lectur...32K/Win32K.pdf
http://support.microsoft.com/default...&Product=WinXP

Quote:

---

Originally Posted by wmicro

To Qerr
I apologize if you took any posting wrong.
Also the key is win32k.sys this is the root of the problem like I stayed it is a timing problem, see more on the PC Boot Process - Windows XP. At http://dotnetjunkies.com/WebLog/unk...cles/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.

http://www.i.u-tokyo.ac.jp/ss/lectur...32K/Win32K.pdf
http://support.microsoft.com/default...&Product=WinXP
http://www.anixis.com/products/ppe/techdoc/td00026.htm

---

Why, wmicro, are you apologizing for anything? For what -ed said? Well, you shouldn't, alright? Geesh that was nothing!! We are ALL about diagnosing pc's. Some of us just need to editorialize: me, others, and especially confus-ed. He is THE Geezer, and has been around longer than most, after all. So, let him go off on his occasional techno rants. After all, it is often the ones who have been here the longest who do just that And. there really is a reason for it. (well, most of the time...you see sometimes, we just 'play' with each other) and quite often we ALL can learn something from it. So, being you are here to help, take it from someone who hasn't always gotten "along" with the old timers: be patient and don't fight back: but DO contribute...because we can always use expertise. Alright?
Anywho, yeah, now that we know the hdd is alright we can pursue other possibilities. And, yeah, the video card is a possiblility. So: step by step we will help! Trust me: don 't fight, just get along. Your knowledge and expertise will become obvioius: to some sooner, to others later.https://forums.windrivers.com/images.../2006/04/1.gif

Quote:

---

Originally Posted by Qerr

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 - 'ed's summary -

Quote:

---

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 !)..

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?