View Finder Error ID 1003

By siovale
Apr 25, 2010
Topic Status:
Not open for further replies.
  1. I have tried working on this problem for weeks to no avail and hope someone, here, can help me.

    I keep getting a view finder ID error: 1003


    The minidump file is attached.


    The exact message is as follows:

    Error code 1000000a,parameter1 00000004,parameter2 00000002,parameter3 0000000,parameter4 804e7f0d.

    My computer's configuration is as follows:
    Mobo: ASRock 775 Dual VSTA
    Chipset: VIA PT880 Pro
    Processor: Intel Core 2 Duo E6400@2133 MHz
    Physical Memory: 1024 MB (2 x 512 DDR - SDRAM)
    Video Card: NVIDIA GeForce 210
    HD: WD (Sata) 250 GB (2 HDs)
    Network card: VT82C570 MV IDE Controller VT6102 Rhine II Fast Ethernet Adapter
    OS: MS Windows XP Pro 5.01.2600 Service Pack 3


    Any help with this is very much appreciated by this newbie to the forum. :))

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Your error is 0xA and faulty hardware is one way that they are created. In your case the file specifically cited memory corruption as your issue. Therefore run Memtest on your memory.

    See the link below and follow the instructions. There is a newer version than what is listed but either one should work. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

    Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


    Link: http://www.techspot.com/vb/topic62524.html


    * Get back to us with the results.
  3. siovale

    siovale Newcomer, in training Topic Starter

    Thank you Route44. Very kind of you to help me.

    I will do exactly as you say and will post back. :grinthumb
  4. siovale

    siovale Newcomer, in training Topic Starter

    Ran Memtest on each memory stick and no errors were found.

    Computer crashed again this morning and I got the same 1003 message.

    Decided to run Hot CPU Tester Pro and got the following log:

    000000| 0000 00000628 Apr, 26 - 01:43:37 | Startig Hot CPU Tester Pro 4.3

    000001| 1012 00000628 Apr, 26 - 01:43:37 | Initializing DefectTrack Engine version 2.2.0

    000002| 1010 00000628 Apr, 26 - 01:43:37 | Loading options...

    000003| 1011 00000628 Apr, 26 - 01:43:37 | Reading system info...

    000004| 0000 00000628 Apr, 26 - 01:43:39 | CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz

    000005| 0000 00000628 Apr, 26 - 01:43:39 | Speed: 2135MHz

    000006| 0005 00000628 Apr, 26 - 01:43:39 | -1

    000007| 0005 00000628 Apr, 26 - 01:43:39 | 32

    000008| 0005 00000628 Apr, 26 - 01:43:39 | 32

    000009| 0000 00000628 Apr, 26 - 01:43:39 | L1 Cache Size: 64KB

    000010| 0000 00000628 Apr, 26 - 01:43:39 | L2 Cache Size: 2048KB

    000011| 0000 00000628 Apr, 26 - 01:43:39 | L3 Cache Size: -1KB

    000012| 0000 00000628 Apr, 26 - 01:43:39 | Hyper-Threading: FALSE

    000013| 0000 00000628 Apr, 26 - 01:43:39 | SMP: TRUE

    000014| 0000 00000628 Apr, 26 - 01:43:39 | Scanning SMBIOS...

    000015| 0000 00000628 Apr, 26 - 01:43:39 | BIOS Vendor: American Megatrends Inc.

    000016| 0000 00000628 Apr, 26 - 01:43:39 | Manufacturer ID:

    000017| 0000 00000628 Apr, 26 - 01:43:39 | Produce Name: 775Dual-VSTA

    000018| 0000 00000628 Apr, 26 - 01:43:39 | Motherboard: 775Dual-VSTA

    000019| 0000 00000628 Apr, 26 - 01:43:39 | Total Physical Memory: 1072934912 bytes

    000020| 0000 00000628 Apr, 26 - 01:43:39 | Availabe Physical Memory: 398688256 bytes

    000021| 0000 00000628 Apr, 26 - 01:43:39 | Total Virtual Memory: 2147352576 bytes

    000022| 0000 00000628 Apr, 26 - 01:43:39 | Availabe Virtual Memory: 2101661696 bytes

    000023| 0000 00000628 Apr, 26 - 01:43:39 | Operating System: Windows XP Professional Service Pack 3

    000024| 0156 00000628 Apr, 26 - 01:43:40 | Setting Process Priority...

    000025| 1111 00000628 Apr, 26 - 01:43:51 | Diagnostic has started

    000026| 1112 00000628 Apr, 26 - 01:43:51 | Test Duration: 06:00:00

    000027| 1113 00000628 Apr, 26 - 01:43:51 | Diagnostic Method: Sequential

    000028| 1114 00000628 Apr, 26 - 01:43:51 | Error Handling: Ignore and Continue

    000029| 1115 00000628 Apr, 26 - 01:43:51 | Hyper-Threading: Disabled

    000030| 0010 00000628 Apr, 26 - 01:43:51 | -Complex Matrix : Enabled

    000031| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000032| 0011 00000628 Apr, 26 - 01:43:51 | --Matrix Size: 3,000x3,000

    000033| 0011 00000628 Apr, 26 - 01:43:51 | --Matrix Data Type: Double

    000034| 0010 00000628 Apr, 26 - 01:43:51 | -Calculating Pi : Enabled

    000035| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000036| 0011 00000628 Apr, 26 - 01:43:51 | --Pi Iterations: 10,000

    000037| 0010 00000628 Apr, 26 - 01:43:51 | -Sorting Algorithms : Enabled

    000038| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000039| 0011 00000628 Apr, 26 - 01:43:51 | --Insertion Sort: Enabled

    000040| 0011 00000628 Apr, 26 - 01:43:51 | --Shell Sort: Enabled

    000041| 0011 00000628 Apr, 26 - 01:43:51 | --Merge Sort: Enabled

    000042| 0011 00000628 Apr, 26 - 01:43:51 | --Heap Sort: Enabled

    000043| 0011 00000628 Apr, 26 - 01:43:51 | --Quick Sort: Enabled

    000044| 0011 00000628 Apr, 26 - 01:43:51 | --CArray Quick Sort: Enabled

    000045| 0011 00000628 Apr, 26 - 01:43:51 | Sorting Array Size: 100,000

    000046| 0010 00000628 Apr, 26 - 01:43:51 | -Prime Test : Enabled

    000047| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000048| 0011 00000628 Apr, 26 - 01:43:51 | --Iterations: 100,000

    000049| 0010 00000628 Apr, 26 - 01:43:51 | -Fast Fourier Transforms : Enabled

    000050| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000051| 0010 00000628 Apr, 26 - 01:43:51 | -Chipset : Enabled

    000052| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000053| 0010 00000628 Apr, 26 - 01:43:51 | -L1 Cache : Enabled

    000054| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000055| 0010 00000628 Apr, 26 - 01:43:51 | -L2 Cache : Enabled

    000056| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000057| 0010 00000628 Apr, 26 - 01:43:51 | -Memory : Enabled

    000058| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000059| 0010 00000628 Apr, 26 - 01:43:51 | -HD : Enabled

    000060| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000061| 0010 00000628 Apr, 26 - 01:43:51 | -MMX : Enabled

    000062| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000063| 0010 00000628 Apr, 26 - 01:43:51 | -SSE : Enabled

    000064| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000065| 0010 00000628 Apr, 26 - 01:43:51 | -SSE2/SSE3 : Enabled

    000066| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000067| 0010 00000628 Apr, 26 - 01:43:51 | -3DNow! : Disabled

    000068| 0011 00000628 Apr, 26 - 01:43:51 | --Thread Priority: THREAD_PRIORITY_NORMAL

    000070| 1026 00000ab8 Apr, 26 - 01:43:52 | Starting Calculating Pi Module on CPU 0

    000071| 1028 00000afc Apr, 26 - 01:43:52 | Starting Sorting Algorithms Module on CPU 0

    000082| 1024 00000bd4 Apr, 26 - 01:43:52 | Starting Complex Matrix Module on CPU 1

    000083| 1026 00000bdc Apr, 26 - 01:43:52 | Starting Calculating Pi Module on CPU 1

    000073| 1032 00000bcc Apr, 26 - 01:43:52 | Starting Chipset Module on CPU 0

    000076| 1036 00000c24 Apr, 26 - 01:43:52 | Starting L2 Cache Module on CPU 0

    000079| 1042 00000ae4 Apr, 26 - 01:43:52 | Starting MMX Module on CPU 0

    000072| 1030 00000abc Apr, 26 - 01:43:52 | Starting Prime Test Module on CPU 0

    000078| 1040 00000bd8 Apr, 26 - 01:43:52 | Starting HD Module on CPU 0

    000075| 1034 00000af8 Apr, 26 - 01:43:52 | Starting L1 Cache Module on CPU 0

    000080| 1046 00000a80 Apr, 26 - 01:43:52 | Starting SSE2/SSE3 Module on CPU 0

    000085| 1030 00000b00 Apr, 26 - 01:43:52 | Starting Prime Test Module on CPU 1

    000081| 1044 00000ab0 Apr, 26 - 01:43:52 | Starting SSE Module on CPU 0

    000084| 1028 00000b08 Apr, 26 - 01:43:52 | Starting Sorting Algorithms Module on CPU 1

    000069| 1024 00000984 Apr, 26 - 01:43:52 | Starting Complex Matrix Module on CPU 0

    000074| 1052 00000bd0 Apr, 26 - 01:43:52 | Starting Fast Fourier Transforms Module on CPU 0

    000077| 1038 00000bec Apr, 26 - 01:43:52 | Starting Memory Mdoule on CPU 0

    000089| 1036 00000a3c Apr, 26 - 01:43:52 | Starting L2 Cache Module on CPU 1

    000086| 1052 00000c5c Apr, 26 - 01:43:52 | Starting Fast Fourier Transforms Module on CPU 1

    000087| 1032 00000a24 Apr, 26 - 01:43:52 | Starting Chipset Module on CPU 1

    000088| 1034 00000a34 Apr, 26 - 01:43:52 | Starting L1 Cache Module on CPU 1

    000091| 1040 00000c58 Apr, 26 - 01:43:52 | Starting HD Module on CPU 1

    000093| 1044 00000c44 Apr, 26 - 01:43:52 | Starting SSE Module on CPU 1

    000094| 1046 00000bc4 Apr, 26 - 01:43:52 | Starting SSE2/SSE3 Module on CPU 1

    000092| 1042 00000c48 Apr, 26 - 01:43:52 | Starting MMX Module on CPU 1

    000090| 1038 00000c64 Apr, 26 - 01:43:52 | Starting Memory Mdoule on CPU 1

    000095| 9999 00000bcc Apr, 26 - 01:49:42 | Error:CPU 0: Memory cells do not match; cMem1[2206943] = 55, cMem2[2206943] = 56

    000096| 0000 00000bcc Apr, 26 - 01:49:43 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-014942.dmp

    000097| 9999 00000a24 Apr, 26 - 01:49:46 | Error:CPU 1: Memory cells do not match; cMem1[2980831] = -80, cMem2[2980831] = -79

    000098| 0000 00000a24 Apr, 26 - 01:49:46 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-014946.dmp

    000099| 9999 00000bd4 Apr, 26 - 01:53:42 | Error:CPU 1: Checksums do not match; Matrix1 = -28115503932.883739, Matrix2 = 9795150339124250800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000.000000

    000100| 0000 00000bd4 Apr, 26 - 01:53:43 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-015342.dmp

    000101| 9999 00000984 Apr, 26 - 01:53:52 | Error:CPU 0: Checksums do not match; Matrix1 = -28115503933.211456, Matrix2 = -28115503932.818485

    000102| 0000 00000984 Apr, 26 - 01:53:52 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-015352.dmp

    000103| 9999 00000b08 Apr, 26 - 01:54:04 | Error:CPU 1: MFC QuickSort: Checksums do not match; a[13] = 0, a[13] = 1

    000104| 0000 00000b08 Apr, 26 - 01:54:04 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-015404.dmp

    000105| 9999 00000afc Apr, 26 - 01:54:07 | Error:CPU 0: MFC QuickSort: Checksums do not match; a[13] = 0, a[13] = 1

    000106| 0000 00000afc Apr, 26 - 01:54:07 | Minidump file saved at C:\Program Files\Hot CPU Tester Pro 4\\HCTApr26-015407.dmp

    000107| 1045 00000c44 Apr, 26 - 07:43:55 | Ending SSE Module on CPU 1

    000109| 1031 00000bc4 Apr, 26 - 07:43:55 | Ending Prime Test Module on CPU 1

    000111| 1039 00000c64 Apr, 26 - 07:43:55 | Ending Memory Module on CPU 1

    000110| 1027 00000bdc Apr, 26 - 07:43:55 | Ending Calculating Pi Module

    000112| 1041 00000c58 Apr, 26 - 07:43:55 | Ending HD Module on CPU 1

    000113| 1037 00000a3c Apr, 26 - 07:43:55 | Ending L2 Cache Module on CPU 1

    000108| 1043 00000c48 Apr, 26 - 07:43:55 | Ending MMX Module on CPU 1

    000114| 1035 00000a34 Apr, 26 - 07:43:55 | Ending L1 Cache Module on CPU 1

    000115| 1053 00000c5c Apr, 26 - 07:43:55 | Ending Fast Fourier Transforms Module on CPU 1

    000116| 1031 00000b00 Apr, 26 - 07:43:55 | Ending Prime Test Module on CPU 1

    000117| 1043 00000ae4 Apr, 26 - 07:43:55 | Ending MMX Module on CPU 0

    000118| 1045 00000ab0 Apr, 26 - 07:43:55 | Ending SSE Module on CPU 0

    000119| 1031 00000a80 Apr, 26 - 07:43:55 | Ending Prime Test Module on CPU 0

    000120| 1037 00000c24 Apr, 26 - 07:43:55 | Ending L2 Cache Module on CPU 0

    000123| 1035 00000af8 Apr, 26 - 07:43:55 | Ending L1 Cache Module on CPU 0

    000122| 1031 00000abc Apr, 26 - 07:43:55 | Ending Prime Test Module on CPU 0

    000121| 1039 00000bec Apr, 26 - 07:43:55 | Ending Memory Module on CPU 0

    000124| 1053 00000bd0 Apr, 26 - 07:43:55 | Ending Fast Fourier Transforms Module on CPU 0

    000125| 1027 00000ab8 Apr, 26 - 07:43:55 | Ending Calculating Pi Module

    000126| 1041 00000bd8 Apr, 26 - 07:43:55 | Ending HD Module on CPU 0

    Unfortunately the minidump files disappeared. If you need them, I could run the test again tonight.

    Hope you can help with this latest development. :)
  5. dividebyzero

    dividebyzero trainee n00b Posts: 4,783   +639

    The Hot CPU test seems to be showing that the CPU failed in it's mathematical test (Complex Matrix)- from what I can gather the program sets identical matrices for each core and applies the same mathematical function to both of them. In this instance two different answers show up.
    A question:
    What is the temp of the CPU cores at idle and under load ?
    Overheating of one or both cores could cause the ALU (arithmetic and Logic Unit) or FPU (Floating Point processing unit) to fail. If your temps are within Intel's specification then it would seem that the CPU is failing- although I stress that I am not familiar with the software you used (Hot CPU Tester Pro) or the exact terminology/error reporting of the program. I presume that when you purchased the software you were given a means of submitting the minidump files for analysis. Is this correct or do the company not provide tech support for their product?

    ****EDIT: Have just located the Hot CPU Tester Pro site ( no updates since 2007 !). On the third link at the top of the page (Documents) it supposedly leads to a LiveSupport link which seems dead as is most of the sites links.
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Thanks for looking in DBZ.
  7. siovale

    siovale Newcomer, in training Topic Starter

    CPU Temps et al.

    Thank you, DBZ and Route 44 for continuing to help me.

    I tried contacting Hot CPU but to no avail.

    Are there other diagnostic tools that you are both familiar with that I could run, in order to help pinpoint the problem in more detail?

    In the meantime, CPU temp idle: 49 C
    Core #1 59 C
    Core #2 59 C

    CPU temp load: 52 C
    Core #1 at 100% load : 65 C
    Core #2 at 100% load : 65 C

    GFX temp: 38 C

    I've heard that CPU failure is very rare. Is this true?

    Very kind of you both. :)
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Yes, cpu failure is not a common issue. It does happen but cpus also tend to be one of the most stable components quality wise that you can purchase and run.

    The next step would be to compare those temperature to Intel's specification as per DBZ's advice.
  9. dividebyzero

    dividebyzero trainee n00b Posts: 4,783   +639

    The idle tempreture indicates that you are using the Intel stock cooler (or something similar), but if this is the case then the 100% load tempretures are way too low. A difference (or delta) of 6ºC between 0% and 100% usage is not possible under the same cooling method.

    Have you tried removing the reapplying the thermal interface material (TIM, thermal grease) ?
    If not, then run the system to warm up the CPU heatspreader/CPU cooler -this will soften the TIM and make the cooler removal easier.
    Power down, switch off the power at the wall and power supply (but leave the power cord connected to both so that it continues to be grounded), then dissipate any static electricity you may have by touching the power supply or any unpainted surface of your computer case.
    Unplug the fan plug from the motherboard header (or power supply cable) and note it's location for reattaching later.
    Remove the CPU cooler (if it's the stock Intel cooler this requires only rotating the four latches on the mounting "legs" of the cooler ( link here showing the procedure, and also Intel's site (figures 20, 21)).
    Carefully clean the TIM off both the CPU heatspreader and the bottom of the cooler using a soft lint-free cloth/electronic wipes and isopropyl alcohol (very cheap at pharmacies) or the same stuff in a fancy package.
    Once clean you can either re-apply some new TIM (i.e. this or similar) shown here, or you can inspect the CPU socket and CPU contact pads for damage at this point before reapplying the TIM and cooler assembly.
    If your CPU has been functioning well previous to this episode then I wouldn't bother with this step unless the system has had some kind of physical shock/impact (i.e. rough handling),- then it may be beneficial to check the CPU seating and whether the load plate (the CPU securing plate) is still securely latched,
    Once reassembled re-test and note temps.
  10. siovale

    siovale Newcomer, in training Topic Starter

    Will do...

    These CPU errors are not entirely new. I never paid much attention, I think, because it is only recently that my computer started crashing and I kept getting the 1003 ID. (Still got it today and the event viewer returned:

    System error.
    Category 102
    Error event ID 1003
    Error code 1000000a, parameter1 00000ff97, parameter2 0000001c, parameter3 00000000, parameter4 80500175)

    Will do as you suggest, DBZ, re. removing and re-applying thermal paste. Will also re-test and get back to you and R44 with the results. I do hope this will do it, because I just can't figure out what is causing these crashes or the 1003 error. *sigh*.

    Anyway greetings and many thanks to you both from Canada. :)
  11. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Go ahead and attach that minidump from your latest crash. 0xA errors are caused by either hardware or drivers attempting to address a higher IRQ Level than they should.
     
  12. siovale

    siovale Newcomer, in training Topic Starter

    I keep losing the minidump files, but if it happens again, once I re-seat the CPU and re-test (which I hope to do either today or tomorrow), I'll save them on another drive and post them here. I hope the re-seating will do it, though.

    Route 44, what is an IRQ level? If drivers are involved, then could it be that it is software that is causing these crashes? (It's obvious, though, that I also have a CPU problem).

    Thanks again. :)
  13. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Here is a brief and definitely not complete definition of IRQ Level:

    Computers have many things within them that can interrupt a processor. These include timers, I/O devices, other processors, internal processor performance counters, etc. All processors have an instruction for disabling interrupts, somehow, but that instruction (cli in x64 processors) isn’t selective about which interrupts it disables.

    The people who built DEC’s VMS operating system also helped design the processors that DEC used, and many of them came to Microsoft and designed Windows NT, which was the basis for modern versions of Windows, including Windows XP and Windows 7. These guys wanted a way to disable (very quickly) just some of the interrupts in the system. They considered it useful to hold off interrupts from some sources while servicing interrupts from other sources.

    They also realized that, just as you must acquire locks in the same order everywhere in your code to avoid deadlocks, you must also service interrupts with the same relative priority every time. It doesn’t work if the clock interrupts are sometimes more important than the IDE controller’s interrupts and sometimes they aren’t.

    Interrupts are frequently called “Interrupt ReQuests” and the priority of a specific IRQ is its Level. These letters, all run together, are IRQL.

    So if you lay out all the interrupt sources in the system and create a priority for each one, or sometimes a priority for each group, you can start to do interesting things.


    It is when a driver attempting to address a higher IRQL than it is designed for occurs the system crashes.


    * Right now we have nothing to tell us if it is indeed a driver but it appears that you do have a cpu problem from what we can tell.
  14. siovale

    siovale Newcomer, in training Topic Starter

    Thank you so much, Route 44, for the info. and for keeping an eye on my ongoing problem. :)

    I hope to get around to re-seating the CPU tomorrow and running the test, since I will be unable to get around to it today. It will generate another log, of course. In the meantime, if the system crashes again, I'll retrieve and post the minidump files and hope you will be able to shed more light (as I'm sure you will) on these problems I've been having.

    Just as I finished writing this, my computer crashed again (with the ubiquitous 1003 error). Here is the minidump files of this latest crash.

    Attached Files:

  15. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Both dumps give only OS drivers and one error is another 0xA the other is 0x19: BAD_POOL_HEADER

    A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers.

    Run harddrive diagnostics on your harddrive. Find the make, go to the manufacture's website and download their free utility. Run both short and long tests.

    * Look forward to what the reseating does.
  16. siovale

    siovale Newcomer, in training Topic Starter

    Well... I finally got around to re-seating the CPU (spent 3 hours just putting the heatsink back on #@%^&) and ran the Hot CPU test. It came back with an error again, but seemingly a different one. During this test, the computer crashed (see attached Hot CPU log file).

    I'm also attaching the minidump file that was produced by the crash.

    I appreciate you taking another look and letting me know what you think. I just can't get to the bottom of this at all. *sigh*

    Attached Files:

  17. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Your error is 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

    Cited issue: Memory corruption. I notoiced dividebyzero is here and hopefully he can get to reading your log. Does this test also stress the memory? If so that could be the reason for your crash.
  18. siovale

    siovale Newcomer, in training Topic Starter

    Thanks R44. :)

    Yes, this Hot CPU seems to test the memory also. Looking at the log, it would seem that the memory is enabled and the thread priority is normal. It doesn't look as though it returned a memory error, at least in the HCPU log.

    It's strange because just the other day, as per Dividebyzero's instructions, I did 8 runs of Memtest on each of my memory sticks (one at a time) and they seemed to be error free.

    When I started having the crashes, I even reformatted the HD and reinstalled Windows with sound card and video card drivers, etc. That obviously didn't solve the problem, since it's still crashing. In fact, it crashed again today, as I said, in the middle of the HCPU test. Again, the error returned was 1003 with the following parameters:

    Error code 10000050, parameter 1 b8dab210, parameter 2 00000001, parameter 3 8056dcc2, parameter 4 00000002.

    What do you suggest I do? Replace any hardware? Is the ASRock mobo any good? Is any hardware on it even worth replacing? Should I be looking at a new setup?

    Thank you both for your patience and for not giving up on me. :D
     
  19. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    Naa, we never give up anybody :) except those who a) don't listen to advice (and even then we are patient -- to a degree) :mad: or b) they get testy. :blackeye:

    We understand the frustration felt with computer issues because we have computers of our own. The biggest difficulties are the distances, the hours in difference which at times is clear around the other side of the globe, and the inability to see the system with our own eyes.


    Anyway, if this system is doing everything you need it to (minus the issues) I say keep it. The reason I asked you if the test put a stress on your memory is because stress can cause errors but under normal circumstances, even gaming, it can remain stable.

    Re-read dividebyzero's advice/respones. He has a much greater working knowledge than I have. Hopefully he'll respond.
  20. dividebyzero

    dividebyzero trainee n00b Posts: 4,783   +639

    I'd say the problem still lies within the CPU.
    I would suggest downloading Prime95 (here) and selest a custom test to stress the CPU only, pretty much leaving the RAM out of the equation.
    I'd run the program with only one DIMM (RAM stick). If the test fails then swap RAM sticks and repeat the test. Pretty laborious but unfortunately that's the essence of troubleshooting hardware.
    Once you start the program:
    select "Options" > "Torture Test" > "small FFTs" or "Custom" radio button.
    Small FFT will test very little of the RAM, while the custom settings will test virtually none.
    Either will provide the answer we're looking for.
    If you are checking the "Custom" radio button" then
    Min FFT size (in K) ....set this to 8
    Max FFT size (in K)....set this to 8
    Make sure "Run FFT's in place is checked" and this will ensure that the test doesn't cycle through your RAM.

    Leave everything else at defaults and then start the test ("OK" button)- keep an eye on CPU/core temps.

    I would leave the test to run a minimum of an hour (run longer if you can), although if the test fails it's likely to do so within a few minutes. If this happens then you'll likely have an error message along the lines of a "Fatal error: rounding....." and "hardware failure..."
    This test is primarily to check the condition of your CPU's L2 cache. If your CPU core temps stay within Intel's thermal specification then a failure, if it occurs (or if the system crashes/hangs), points to a failing CPU. At this point troubleshooting becomes a little more problematic. Basically to be sure where the fault lies you would need access to another LGA775 motherboard and RAM (or at least a board that can use your present RAM) to see if the test result can be replicated in a different enviroment.

    ***Remember to disable AV software and any backround programs before running any testing***

    Also, could you tell us whether these crashes happen in usual deskop activities (2D, word processing, surfing etc) and the make/model/age/spec's of your power supply (especially if the crashes are more prevalent during gaming or intensive computation (i.e.video/graphical work). Older and/or underpowered ( PSU's lose a percentage of their rated output over time) can cause excessive ripple in the current which will often lead to failures in CPU's, as well as motherboards northbridge (memory controller/chipset) and virtually every other component in the system.
  21. siovale

    siovale Newcomer, in training Topic Starter

    Thank you, Route 44, and Dividebyzero for helping me. It is very much appreciated.

    Okay... So, after re-seating the heatsink, I don't seem to be crashing anymore.

    I also disabled and disconnected a floppy drive I'd installed before I started crashing. That might have been the reason. Haven't had a crash, and hence a 1003 error since.

    I ran the HotCPU test again and it returned only one error, but a different one from before. I've attached the log.

    It used to crash when I was playing music through Mediaplayer. I have a feeling the CPU would not be able to pass an intensive stress test, but, like I've said, in normal desktop operations, the computer doesn't seem to be crashing anymore. (I don't play games :) ).

    As to the PSU, it's an Antec ATX 430.

    Thanks again.

    Attached Files:

Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.