[srfdriver22]

Sometimes when I turn my monitor on (I don't let my HD or monitor sleep) when I wake up, I get a KP. It's not every time, but every once in a while. Here's the panic.log clipping:

panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000833B8 0x0008389C 0x0001ED8C 0x000908C0 0x00093B8C
Proceeding back via exception chain:
Exception state (sv=0x1FC38A00)
PC=0x0028702C; MSR=0x00009030; DAR=0x00000001; DSISR=0x42000000; LR=0x1FD472E0; R1=0x1205BC90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00246AB0 0x0024C1C8 0x0024C7A8 0x0024BDD4 0x0023F104 0x0023F0C8
Exception state (sv=0x1FB1EA00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

[Chuckit]

Do you have any third-party RAM?

[srfdriver22]

Yes, 1 256 stick. I've done multiple HW tests on it and it always comes up fine. Is that what it looks like?

[Chuckit]

Originally posted by srfdriver22:
Yes, 1 256 stick. I've done multiple HW tests on it and it always comes up fine. Is that what it looks like?

Well, the log says it's a data access error. That strongly suggests bad memory to me. I'm not a 31337 hax0r or anything, so you might want a second opinion. But bad memory is what it looks like to me.

[someone_else]

This could be bad RAM, but it could also be a bug. The DAR is very close to NULL (0) and any access to NULL will cause a kp.

This could also be some kind of other hardware problem. If you look at the backtrace, you will see that a registry plane (for hardware) is being iterated. It may be that your hardware is not responding correctly to power events, and is causing an empty list (NULL) to be returned to the kernel.

There's no way to know for sure what is going on. You'll have to do some troubleshooting. Trying removing the extra RAM. Try a different monitor, try different video card. (The last two may not be possible for you though.)

Here is the backtrace leading up to the kp (assuming you are running 10.3.2):

0x28702c <OSArray::getNextObjectForIterator(void*, OSObject**) const+56>: stw r0,0(r5)
0x246ab0 <IORegistryEntry::getChildIterator(IORegistryPla ne const*) const+168>: mr r3,r30
0x24c1c8 <IOService::actionWillTerminate(IOService*, unsigned long, OSArray*)+188>: lwz r2,0(r27)
0x24c7a8 <IOService::terminateWorker(unsigned long)+512>: lwz r2,0(r23)
0x24bdd4 <IOService::terminateThread(void*)+56>: lwz r0,22180(r30)
0x23f104 <IOLibInit+280>: lwz r0,88(r1)

HTH.

[srfdriver22]

Originally posted by someone_else:
This could be bad RAM, but it could also be a bug. The DAR is very close to NULL (0) and any access to NULL will cause a kp.

This could also be some kind of other hardware problem. If you look at the backtrace, you will see that a registry plane (for hardware) is being iterated. It may be that your hardware is not responding correctly to power events, and is causing an empty list (NULL) to be returned to the kernel.

There's no way to know for sure what is going on. You'll have to do some troubleshooting. Trying removing the extra RAM. Try a different monitor, try different video card. (The last two may not be possible for you though.)

Here is the backtrace leading up to the kp (assuming you are running 10.3.2):

0x28702c <OSArray::getNextObjectForIterator(void*, OSObject**) const+56>: stw r0,0(r5)
0x246ab0 <IORegistryEntry::getChildIterator(IORegistryPla ne const*) const+168>: mr r3,r30
0x24c1c8 <IOService::actionWillTerminate(IOService*, unsigned long, OSArray*)+188>: lwz r2,0(r27)
0x24c7a8 <IOService::terminateWorker(unsigned long)+512>: lwz r2,0(r23)
0x24bdd4 <IOService::terminateThread(void*)+56>: lwz r0,22180(r30)
0x23f104 <IOLibInit+280>: lwz r0,88(r1)

HTH.

Interesting. I'll try troubleshooting the RAM again, though I've had KP's before and tried it and the KP's just stopped. No rhyme or reason to it.

Unfortunately, I can't try a different monitor or graphics card. Though, how did you come to the conclusion that those two may be a problem?

[someone_else]

Originally posted by srfdriver22:
Though, how did you come to the conclusion that those two may be a problem?

Well, you originally_said the problem happens when your monitor wakes up, and then I said:

This could also be some kind of other hardware problem. If you look at the backtrace, you will see that a registry plane (for hardware) is being iterated. It may be that your hardware is not responding correctly to power events, and is causing an empty list (NULL) to be returned to the kernel.

The hardware I was speaking of was your monitor/graphics card.

HTH.