Definitely spoke too soon.

[onthat]

Turned off my MBP last night and when I started it today, I got a loading screen covered in multicolored vertical lines...then it says restart the computer. Please tell me this can be fixed without sending it back. Only had it for a few days now.

 

[SkyBell]

Might be a kernel panic, might be something worse. I can't offer advice, as I don't own a MBP, but I do have an iBook, and when that happened to me, it was a kernel panic (Along with a dying logic board, but that's a manufacturing defect common in iBook G3's, I don't think that's your problem.)

 

[Britanium]

Turned off my MBP last night and when I started it today, I got a loading screen covered in multicolored vertical lines...then it says restart the computer. Please tell me this can be fixed without sending it back. Only had it for a few days now.

Call AppleCare

 

[onthat]

I reset the pram about 3 times, then it started up fine...so I put the OSX install disk in and tried to run hardware check. Now it's screwed again and I get a kernel panic every time I start up.

 

[onthat]

alright, I got hardware test to load up and am gone see what it tells me.

 

[heatmiser]

Apple Quality Control Strikes Again!
Seriously, that's a bummer. Try taking it into a store, or calling AC for help. It sounds like a hardware problem (ie, something you can't fix).

 

[onthat]

passed the quick test... moving on to extended test.

 

[QCassidy352]

Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420.1 (KHTML, like Gecko) Version/3.0 Mobile/3B48b Safari/419.3)

sounds like either a video card or a logic board problem. :-/ I do not think you'll be able to resolve this without service

 

[Naimfan]

Seriously, that's a bummer. Try taking it into a store, or calling AC for help. It sounds like a hardware problem (ie, something you can't fix).

Exactly correct. Even if hardware test doesn't turn anything up, get it to an Apple store and have them (or Applecare) exchange it.

 

[onthat]

Mon Dec 10 01:09:37 2007
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x014b2000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x3d240e40, ECX: 0x00000000, EDX: 0x04832004
CR2: 0x00000000, EBP: 0x2592b508, ESI: 0x041f1800, EDI: 0x2412b004
EFL: 0x00010246, EIP: 0x3d02e0f2, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2592b2f8 : 0x128d08 (0x3cc0ec 0x2592b31c 0x131de5 0x0)
0x2592b338 : 0x1a4a55 (0x3d2524 0x1 0xe 0x3d1d48)
0x2592b448 : 0x19aeb4 (0x2592b460 0x1 0xdb96203 0x0)
0x2592b508 : 0x3d03d18b (0x2412b004 0xb 0x0 0x3d02cf0a)
0x2592b538 : 0x3d03b600 (0x2412b004 0x2592b570 0x0 0x1a37c0)
0x2592b818 : 0x3d02f81a (0x0 0x600d600d 0x7022 0x2592b848)
0x2592b8d8 : 0x3d1bfb33 (0x24137564 0x4d2 0x3d1e69dc 0x6e766461)
0x2592b9c8 : 0x3d02a402 (0x24137000 0x0 0x2592bad2 0x80)
0x2592ba28 : 0x3bc62133 (0x422ec00 0x0 0x2592bad2 0x80)
0x2592bb58 : 0x3bc63813 (0x422ec00 0x3bc66cac 0x2592bbfc 0x4)
0x2592bc18 : 0x35d91875 (0x422ec00 0x1 0x0 0x2592bdd4)
0x2592bc78 : 0x35d8b06b (0x422ec00 0x0 0x0 0x422ec00)
0x2592bc98 : 0x38c421 (0x422ec00 0x4009370 0x4009370 0x0)
0x2592bce8 : 0x3b2886 (0x422ec00 0x4009370 0x4009370 0x0)
0x2592bd48 : 0x18d4d2 (0x422ec00 0x4009370 0x0 0x0)
0x2592bdb8 : 0x12b4c3 (0x4868780 0x427c298 0x2592bdf8 0x11e042) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.0.6)@0x3d029000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35b7e000
dependency: com.apple.iokit.IONDRVSupport(1.4.7)@0x3bc5b000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.7)@0x35d83000
com.apple.iokit.IONDRVSupport(1.4.7)@0x3bc5b000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35b7e000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.7)@0x35d83000
com.apple.iokit.IOGraphicsFamily(1.4.7)@0x35d83000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35b7e000

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386

verified permissions and verified disk
Extended hardware test shows no problems
posting this from affected computer