Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.



  • Please log in to reply
3 replies to this topic

#1 DrKailey


  • Members
  • 2 posts
  • Local time:09:45 AM

Posted 05 March 2016 - 10:50 PM

First post, thanks for any and all help.


Running Mach3 CNC software on on old Dell box to power a lathe conversion.


Keeps randomly crashing with BSOD, not a good thing when you're trying to machine some parts.


XP Professional installed from licenced CD, upgraded to SP2.  P4 @ 3.2 GHz, 40G HD, 4 G RAM.


Tried a repair install from the CD, nada.





Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini030216-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Mar  2 18:13:35.421 2016 (UTC - 8:00)
System Uptime: 0 days 3:08:07.953
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {a36848, 2, 1, 80524ef2}
Probably caused by : memory_corruption ( nt!MiInsertPageInList+37 )
Followup: MachineOwner
kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 00a36848, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80524ef2, address which referenced memory
Debugging Details:
WRITE_ADDRESS:  00a36848 
80524ef2 8914f8          mov     dword ptr [eax+edi*8],edx
LAST_CONTROL_TRANSFER:  from 804e8470 to 80524ef2
f789e818 804e8470 00000000 00008000 00000000 nt!MiInsertPageInList+0x37
f789e844 8069ee75 8a5b2788 00000000 00000044 nt!MmZeroPageThread+0xda
f789edac 8057dfed 80088000 00000000 00000000 nt!Phase1Initialization+0x1144
f789eddc 804fa477 806a033e 80088000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
80524ef2 8914f8          mov     dword ptr [eax+edi*8],edx
SYMBOL_NAME:  nt!MiInsertPageInList+37
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInList+37
BUCKET_ID:  0xA_nt!MiInsertPageInList+37
Followup: MachineOwner

Edited by hamluis, 06 March 2016 - 10:27 AM.
Moved from XP to BSODs/Crashes - Hamluis.

BC AdBot (Login to Remove)


#2 ranchhand_


  • Members
  • 1,710 posts
  • Gender:Male
  • Location:Midwest
  • Local time:08:45 AM

Posted 06 March 2016 - 11:28 PM

I have no knowledge of the program that you are running, evidently it is a dedicated machining control program. However, if the problem is hardware in the computer there are a couple of thing we can try.

I will assume that this computer/software was running fine for years with no problems. Correct me if i am wrong.

I will also assume that there were no recent power outages or spikes that shut the computer down.

So lets test a couple of things that commonly can cause these random crashes as follows:


Please post a Speccy log that will give me an idea of what you are running as follows:


Please go Here and download Speccy system analyzer (free) and save to your problem computer's desktop. Install it.

Allow your computer to run for a few minutes, using it as usual.

Open Speccy. Give it a few seconds to scan your system.

Click File \Publish Snapshot.

In the next screen, click yes.

In the next screen, click Copy To Clipboard.

In your next post, paste that link in the post.


>  When is the last time that you completely cleaned the inside of the case? Especially if it is in a shop environment, it can get clogged with dust and overheat which will cause crashes. In addition, sometimes older circulation fans stop working, check that they are all spinning up to speed. If the case is filthy, open the side and take a hand-vac with air flow reversed (blowing, not intake) with a crevice tool and blow out the case, paying special attention to the CPU heatsink and fan. I suggest you do this outside, a really dirty case can produce clouds of dust.


> Test the memory: if you have multiple sticks, remove and test one at a time using the #1 slot as follows:


>  Download the (free) zip file (2nd from the top) ISO of Memtest86+ and burn to a CD.

>  Make sure your BIOS is set to CD = 1st Boot Device, HDD = 2nd Boot Device.

Reboot with the CD in your drive. Allow it to run until you get a message at the bottom of the screen that testing is complete (about 20 minutes). Any red posts at the bottom of the screen means that memory stick is bad.

If you have multiple sticks, test only one (1) stick at a time

If Memtest will not run or you get error messages, let me know.

If you have any questions on how to do the above, post back.


If the memory tests as good, next test the hard drive (HDD) as follows:


Go here and download Seatools For DOS (free)

Accept the EULA and download the ISO file.
When download is complete burn the ISO to a CD or DVD.
Make sure your BIOS is set to:   1st Boot Device = CD drive, 2nd Boot Device = Hard Drive.

Boot the computer with the CD in the drive.
When the program opens, click the upper left corner for the Long Test.
> Note: if you get a pop-up window telling you that SMART has tripped and asking if you want to continue, choose Yes. Be sure to post that in your next reply along with the result of the test.
At the end of the test, you will get either a Pass or Fail notice. Post the result in your next reply.
Be sure to have your hard drive directly installed internally to the motherboard, not in an external case.

That will get you started; post back with results.

Edited by ranchhand_, 06 March 2016 - 11:32 PM.

Help Requests: If there is no reply after 3 days I remove the thread from my answer list. For further help PM me.

#3 DrKailey

  • Topic Starter

  • Members
  • 2 posts
  • Local time:09:45 AM

Posted 07 March 2016 - 09:45 AM

Thanks for the reply!


This is an old Dell Workstation 360 that was stored for years then brought out to run a machine.  I cleaned it thoroughly so it's not overheating.


The MS Windows debugger points to the memory so I've checked each of the four sticks with Memtest86, all check OK.  I have a buddy in IT that said these machines were notorious for bad caps, they had to replace dozens of them at his work.  I looked for bulging/leaking caps but couldn't see any.


He has an old Optiplex 745 for me so I think I'm going to retire this 'ol gal, she sure doesn't owe my anything.


Thanks again for you help!

#4 ranchhand_


  • Members
  • 1,710 posts
  • Gender:Male
  • Location:Midwest
  • Local time:08:45 AM

Posted 08 March 2016 - 08:35 AM

Welcome! :cowboy:

Help Requests: If there is no reply after 3 days I remove the thread from my answer list. For further help PM me.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users