system error

Status
Not open for further replies.

boykov

Posts: 67   +0
hi there

after an upgrade (2x256mb dual ch. to 2x512mb and a sata hdd) my pc started to crash periodically.... changed the DDR modules for diferent ones , but the problem continues ... 3-4 days and ... this is what i get: :unch:

source: system error
category: (102)
event ID: 1003

error code 0000000a, parameter1 00000016, parameter2 00000002, parameter3 00000000, parameter4 804dbda3.

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 31 36 2c 20 000016,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 64 00, 804d
0050: 62 64 61 33 bda3

with some variations but generally the same.... (category and event)

my system is : athlon XP 2500+ (barton)
2x512MB dual ch. ddr400 (noname brand , tried kingston not compatible!!!)
ASUS FX 5600 128MB
motherboard : MSI K7N2 delta ILSR

if anyone has any ideas please HELP...
all latest drives installed and bios...

thanks

a few things i forgot to mention ... when i tried kingston modules there were no problems runnin single channel ... problems only begin in dual channel.. i´ve ran memtest for over 24hrs and nothing no errors ... blue screen only seems to appear when i´m on the net...
and my minidumps if more info is needed , do tell....

thanks
 
Hi,

Your windows are crashes randomly with any pattern. It is symptom of faulty hardware and the bugcheck 0A, 50, 8E and D1 are all related to faulty memory. One minidump is crashed with instructon alignment error. Base upon all of the above symptoms, I believe that it is faulty memory.

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

If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram


Mini090705-01.dmp BugCheck 10000050, {d3e8c033, 0, 8056b8f7, 0}
Mini090705-01.dmp Probably caused by : hardware ( nt!CmpFindValueByNameFromCache+c5 )

Mini090705-02.dmp BugCheck 1000008E, {c0000005, 804ea4b6, ec683c44, 0}
Mini090705-02.dmp Probably caused by : ntoskrnl.exe ( nt!ObReferenceObjectSafe+d )

Mini090705-03.dmp BugCheck 1000000A, {86fc6890, 2, 1, 804ea01e}
Mini090705-03.dmp Probably caused by : ntoskrnl.exe ( nt!KiAttachProcess+9 )

Mini102105-01.dmp BugCheck 1000007E, {c0000005, f74cfedd, ecb3baa4, ecb3b7a0}
Mini102105-01.dmp Probably caused by : ks.sys ( ks!KsDispatchIrp+b )

Mini110405-01.dmp BugCheck D1, {0, 2, 1, f7b19e20}
Mini110405-01.dmp Probably caused by : usbohci.sys ( usbohci!OHCI_SubmitTransfer+14 )

Mini112005-01.dmp BugCheck 1000007E, {c0000005, ed40e96b, eb089a20, eb08971c}
Mini112005-01.dmp Probably caused by : portcls.sys ( portcls!CIrpStream::TransferKsIrp+88 )

Mini112305-01.dmp BugCheck 1000007E, {c0000005, ecfa396b, b92e9a20, b92e971c}
Mini112305-01.dmp Probably caused by : portcls.sys ( portcls!CIrpStream::TransferKsIrp+88 )

Mini112505-01.dmp BugCheck A, {16, 2, 0, 804dbda3}
Mini112505-01.dmp Probably caused by : ntoskrnl.exe ( nt!KiWaitTest+30 )
 
thanks for the reply

i just downclocked the timings for the ram... so far so good ... i guess i´ll have to wait and see...

thanks again

P.S: this is the first time i´m changing memory timings.
 
Hi,

since downclocking my ram i´ve had no problems with blue screens , so far.

thanks again :)
 
Status
Not open for further replies.
Back