-Memtest: Not sure. Just the test that is automatically run when booting to the latest memtest iso.
I will run the hdd tests from a boot cd.
Main Topics
Browse All TopicsGetting between 1 and 5 BSOD / day. No apparent correlation between what (if anything) I am doing and the crashes.
No particularly new hardware, though I did install an Intel 2200BG wireless miniPCI card a few months ago.
In my troubleshooting, I have formatted and reinstalled the system with a SP2 slipstreamed disc, but this had no apparent effect on the BSOD's.
I have switched the memory modules with each other. Memtest ran 7 or 8 full passess with no errors. The BSOD's seem random. Sometimes naming a file sometimes not. Among other files named on the BSOD's have been atapi.sys, and win32k.sys. Sometimes it gives me an error like 'IRQ not less or equal', sometimes not. There's no apparent consistency.
I have also been running Western Digital diagnostics for Windows. It always says the drive is fine if it gets through, even on the 'extended test'. But, it doesn't always get through. About a third of the time it crashes in the middle of the test.
Any ideas??
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.
When Windows crashes with blue screen, it writes a system event 1001 and a minidump to the folder \windows\minidump. Check system event 1001 and it has the content of the blue screen
Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001. Copy the content and paste it back here
Zip 5 to 6 minidumps and attach the zip files at any webspace. I will study the dump and find out the culprit.
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8028aa, 0xf0171c30, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000060, 0x0000000d, 0x00000000, 0xf778b875). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x000059b0, 0x0000000d, 0x00000000, 0xf778bc85). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x804f0181, 0xefb8698c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8054ae2d, 0xf073b288, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8054ae34, 0xefff9844, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8028aa, 0xf00f9c30, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8056332f, 0xf0168658, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini07
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000028, 0x00000002, 0x00000000, 0x8050257b). A dump was saved in: C:\WINDOWS\Minidump\Mini07
Minidumps uploaded to http://gra.midco.net/mrnat
Three minidumps are inaccessible by windbg and it is symptom of bad ram. Two minidumps crashed with IRQL x'0d' which is the device driver. It is unlikely the IRQL x'0d' crash due to software error. All the symptoms prove that it is a bad RAM. What do you mean swap memory module? If you have two memory stick, take out a memory stick. If your Windows does not crash, the memory stick which is not in-use is faulty.
A minidump crashed with bugcheck code 0A. From the disassemble code, register eax only if bad ram.
80502574 8b04b580e95580 mov eax,[nt!MmPagingFile (8055e980)+esi*4] ?? why eax =0
8050257b 8b7828 mov edi,[eax+0x28]
Mini072405-01.dmp 0a (0x00000028, 0x00000002, 0x00000000, 0x8050257b) nt!MiReleaseConfirmedPageF
Mini072505-01.dmp 8e (0xc0000005, 0x8056332f, 0xf0168658, 0x00000000) win32k!xxxRealInternalGetM
Mini072505-02.dmp 8e (0xc0000005, 0xbf8028aa, 0xf00f9c30, 0x00000000) nt!ObGetObjectSecurity+53 -> nt!ExAllocatePoolWithTag+6
Mini072505-03.dmp 8e (0xc0000005, 0x8054ae34, 0xefff9844, 0x00000000) nt!ObGetObjectSecurity+53 -> nt!ExFreePoolWithTag+673
IA Mini072505-04.dmp 8e (0xc0000005, 0x8054ae2d, 0xf073b288, 0x00000000) nt!ExFreePoolWithTag+66c
IA Mini072505-05.dmp 8e (0xc0000005, 0x804f0181, 0xefb8698c, 0x00000000) nt!IoCompleteRequest+ab
Mini072505-06.dmp d1 (0x000059b0, 0x0000000d, 0x00000000, 0xf778bc85) atapi!IdeGetSrbData+f
Mini072605-01.dmp d1 (0x00000060, 0x0000000d, 0x00000000, 0xf778b875) atapi!IdeGetInterruptState
IA Mini072605-02.dmp 7f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
Mini072605-03.dmp 8e (0xc0000005, 0xbf8028aa, 0xf0171c30, 0x00000000) win32k!xxxRealInternalGetM
When I said I swapped the memory modules I meant that there are two SODIMMs and I put the one from slot 1 into slot 2, and then one from slot 2 into slot 1. Maybe that was pointless but I saw it recommended elsewhere. Hey! at least they got reseated.
Regarding the earlier post that memtest may be running the basic test rather than full/extended test: I looked through all the options in memtest, and it appears that there is no explicit option like BASIC vs. FULL. There are 10 tests (0-9) and when you just boot to the CD it runs all of them sequentially and then repeats.
Is it possible that the problem could be faulty RAM and yet memtest does not show any errors after 7 full passes (about 12 hours) ?
McKnife: You are evidently referring to a version of Memtest other than their latest. v.3.2.
On this version you press 'c' to get to the configuration menu where you have:
(1) Test Selection
(2) Address Range
(3) Memory Sizing
(4) Error Summary
(5) Error Report Mode
(6) ECC Mode
(7) Restart
(8) Refresh Screen
(9) Adv. Options
(0) Continue
If you choose 'Test Selection' then you get:
(1) Default Tests (which observation indicates means tests #1 - #8)
(2) Skip Current Test
(3) Select Test
(4) Select Bit Fade Test (which observation indicates is test #9)
(0) Continue
I have been running tests 1-8 without errors. Although if I attempt to change options (2) or (3) from the main menu the program quits responding. For example, I have tried (2) Address Range -> (3) Test All Memory. Or (3) Memory Sizing -> (2) BIOS - All; and (3) Memory Sizing -> (2) Probe.
Any of those choices causes the program to stop responding.
Anyhow, after taking out one of the mem chips and running the computer for a while, I have had no crashes, so now I have taken that one out and put in what may be the 'BAD' one, and am waiting to see if the computer crashes with it.
Don't waste time to run memtest as some faulty ram can pass memtest. As you want to fix the problem, take out a memory stick and your windows does not crash. This is the solution. As memtest have to run a long time, if it does not report any problem and your windows still crash. Your problem is still unresolved,
cpc2004: You were right. With one of the sticks out it ran a burn-in app for almost 24 hours without problem. With the other one in it crashes usually within an hour.
All this time I've trusted memtest to uncover any problems with RAM.
Now I know that you can have a piece of RAM that is consistently bad, and yet consistently passes memtest.
Thanks for the advice.
Business Accounts
Answer for Membership
by: McKnifePosted on 2005-07-26 at 13:01:27ID: 14530953
-Memtest: Full passes of the normal or extended tests?
Don't run your hd tests under windows, create a boot diskette or boot cd and try again.
I'd say, random bsods that frequently would be RAM, power supply, or hdd mostly.