also you could remove your network card if it is onboard disable it in the bios to see if this helps.
Main Topics
Browse All TopicsI've got a Windows XP computer that has started crashing at apparently random times.
I suspect faulty memory, but I have run the MS memory test utility (boots from CD) and no errors were reported. Of course, these mem test utilities are not always 100% in detecting a memory problem.
I have rar'd 8 mindumps and a text with the corresponding 1001 events. If anyone wants to do a diagnosis on them I'd appreciate it. I know that "cpc2004" does this kind of thing.
The minidumps are at the URL below.
http://gra.midco.net/mrnat
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Well, there were two RAM sticks in the PC, a 512MB and a 256MB.
I took out the 256MB for a little while, and the system crashed again. So I put the 256 back in and took the 512 out and it ran OK.
But, to make sure it wasn't the slot, I put the 512 back in, but I put it in the slot where the 256 had been, and took the 256 out.
So far, so good.
Incidentally, the period where I had the 256 only in the computer and no crashes was very short so it doesn't prove much on its own.
As for the suggestions you made CPC2004:
1. The CPU fan appears to be working, I don't have any convenient way to test the CPU temp. E.g., no motherboard temp monitor utility.
2. Did that.
3. Both are standard clocked.
4. Did that
5. It is compatible.
6. SPD is on, timing is the same.
7. There is nothing new added to the system to consume more power USB or other. If problems continue I will try swapping in a bigger and better PSU.
8. Did that.
9. Haven't done that.
10. Did that
Thanks for the tips. I'll let you know what happens.
Business Accounts
Answer for Membership
by: cpc2004Posted on 2006-01-09 at 17:49:10ID: 15656378
4 system crashes are caused by code corruption and the culprit is faulty ram.
essage+0x2 64 3f6 ads+0x6a 0x23
:
0
cher+1a )
73 )
f )
You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor
If it still crashes, diagnostic which memory stick is faulty
Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
Mini010606-02.dmp
BugCheck 1000008E, {c000001d, bf83f284, f6db091c, 0}
Probably caused by : memory_corruption
STACK_TEXT:
f6db09f0 bf83f4e8 03651988 00000000 00000001 win32k!xxxCallHook2+0x177
f6db0a0c bf801b2c 00000000 00000001 00000002 win32k!xxxCallHook+0x26
f6db0a54 bf884812 f6db0aa4 000025ff 00000000 win32k!xxxRealInternalGetM
f6db0d30 bf86d10a bf9a9620 00000001 f6db0d54 win32k!xxxDesktopThread+0x
f6db0d40 bf8010ca bf9a9620 f6db0d64 0071fff4 win32k!xxxCreateSystemThre
f6db0d54 804de7ec 00000000 00000022 00000000 win32k!NtUserCallOneParam+
f6db0d54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0071ffe0 00000000 00000000 00000000 00000000 0x7c90eb94
FAILED_INSTRUCTION_ADDRESS
win32k!xxxCallHook2+177
bf83f284 0fff ???
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
!chkimg -lo 50 -db !win32k
14 errors : !win32k (bf83f285-bf83f2fd)
bf83f280 47 04 85 db 0f *ff ed 00 00 00 8b 4f 24 *ff f9 ff G..........O$...
bf83f290 74 14 8b 46 2c *ff d2 42 d3 e2 85 90 a4 00 00 00 t..F,..B........
bf83f2a0 0f 84 e5 01 00 *05 8b 46 40 8b 40 0c 0b *ff 98 00 .......F@.@.....
bf83f2b0 00 00 f6 c4 04 *ff 85 07 fe ff ff 8b 07 *ff 0d e4 ................
bf83f2c0 90 9a bf 25 ff ff 00 00 8d 04 40 f6 44 *00 09 01 ...%......@.D...
bf83f2d0 0f 85 c3 01 00 *05 8b 46 28 8d 8e 9c 00 *ff 00 8b .......F(.......
bf83f2e0 19 85 db 89 45 *ff 8d 45 e8 89 46 28 89 *ff ec 0f ....E..E..F(....
bf83f2f0 85 26 fe ff ff *00 d7 e8 5c 26 fc ff 8b *00 44 85 .&......\&....D.
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: .trap fffffffff6db091c ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Mini010606-01.dmp BugCheck 1000007E, {c000001d, 806ee320, f007acac, f007a9a8}
Probably caused by : hardware ( rdbss!RxWorkerThreadDispat
Mini010606-02.dmp BugCheck 1000008E, {c000001d, bf83f284, f6db091c, 0}
DEFAULT_BUCKET_ID: CODE_CORRUPTION <-- faulty ram
Probably caused by : memory_corruption
Mini010606-03.dmp BugCheck 1000008E, {c0000005, bf80c374, f4d4d584, 0}
Mini010606-03.dmp DEFAULT_BUCKET_ID: CODE_CORRUPTION
Probably caused by : memory_corruption
Mini010706-01.dmp BugCheck 1000008E, {c0000005, 8054ae34, b875b9c8, 0}
Probably caused by : ntoskrnl.exe ( nt!ExAllocatePoolWithTag+6
Mini010806-01.dmp BugCheck 1000000A, {80080a4, 2, 0, 804ee3c5}
Probably caused by : naiavf5x.sys ( naiavf5x+1e9e )
Mini010906-01.dmp BugCheck 1000008E, {c0000005, bf81036c, ed80e414, 0}
DEFAULT_BUCKET_ID: CODE_CORRUPTION
Probably caused by : memory_corruption
Mini010906-02.dmp BugCheck 10000050, {f3875107, 1, bf806785, 0}
Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+e
Mini010906-03.dmp BugCheck 1000008E, {c0000005, bf8f4f34, b4db87a0, 0}
DEFAULT_BUCKET_ID: CODE_CORRUPTION
Probably caused by : memory_corruption