Blue screen and mem dump

Hi override_y2k,
    Backup all your data and Reinstall

Bye
---
Harish

override_y2k,
    That might happen if you upgraded

Do you install Zone Alarm?

Take a look at the following web page,

http://aumha.org/win5/kbestop.htm

which is presented using frames.  Click on the error code (0A) in the left pane of the page, which is a link to the following quotation:

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
“Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Partial List of Driver Error Codes That the Driver Verifier Tool Uses to Report Problems {KB 315252} Win XP
Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
“Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)

You should go to the actual page in order to read the links given in the quotation above.

If i upgraded to what?

I installed a new NEC dvd burner about a month ago. I never had any problems with my PC until last week or so. The only recent software i remember installing is a BETA of MSN Messenger. Ive tried a system restore to see if that helps. Will keep this updated.

Attach the 3 to 4 minidumps at any webspace and I will examine the dump. You can find the minidumps at the folder \windows\minidump

Well if you give me an email address i'll mail you the dump files. Unfortunately i dont have any webspace for hosting the files.

You can find my email address at my profile.

If you want to have more evidence, provide more minidumps

OK, i will award you the points anyway.

I'll mail you some more of the dumps.

Thx Martin.

I hate to say that this is hardware problem but in fact it is. Two minidumps have memory corruption. The third dump crashes because windows write to non-exist address which is prohibited. As you know, the hardware occurs random, if it fails at clock level interrupt routine or tcpip.sys. We know they are stable routine which is unlikely to fail unless hardware error. Then it is easy to identify this is hardware problem. However if the hardware occurs at the device driver and XP does not have their symbolic map because the device drivers are owned by hardware manufacturers.  Windbg cannot report memory corruption for non-Microsoft software.

Mini030105-01.dmp
BugCheck 1000000A, {0, 1c, 1, 804dcb98}
Probably caused by : memory_corruption
FAULTING_IP: nt!KiReadyThread+11 804dcb98 aa               stosb  <-- this instruction is changed due to hardware problem
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    804dcb98 - nt!KiReadyThread+11
      [ 8a:aa ]
1 error : !nt (804dcb98)
MODULE_NAME:  memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
STACK_COMMAND:  kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Mini022805-02.dmp
BugCheck 100000D1, {3, 2, 1, f6f73be6}
Probably caused by : memory_corruption
CHKIMG_EXTENSION: !chkimg -lo 50 -d !USBPORT
    f6f73bd8 - USBPORT!USBPORT_QueuePendingTransferIrp+84
      [ 60:64 ]
1 error : !USBPORT (f6f73bd8)
MODULE_NAME:  memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
STACK_COMMAND:  kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption

Which hardware component is faulty? Your feedback will help us to resolve similar problem.

I have had similar issue

blue screens on boot

driver_corrupted_mmpool 0xdo alternating with
crql_not_less_or_equal 0xa

and then sometimes it boots OK and stays up

anyway it failed the windows memory test quite convincingly - Bad RAM