InfiniteMac OSx86 - View Single Post

frisco2 · 06-27-2012, 05:03 PM

HI @ll

here a new problem!!!

The last days I modified my NVIDIA Grafik driver, I accept that an error is suffused to me. Now I receive a funny error message with start from LION

10.7.4! I investigated in the Internet and nothing found, which continues to help to repair. Perhaps does someone have an idea?

1. Problem “kernel: smb_treeconnect_internal: Malformed tree connect with A bath word COUNTs! wc= 2” see below --->
2. The annoying CPU panic message, which comes during the enterprise of LION applications and to start me again forces!
Can someone to me possibly explain which the individual messages for a meaning to have????

...............
NTFS Volumme name Mac Data, version 3.1

com.apple.launched 1 com.apple.correservices.applied.authentication 108 Exit timeout elapsed (20 seconds). Killing

smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2
smb_treeconnect_internal: Malformed tree connect with a bad word count! wc= 2

IN CASE READ THERE HAS BEEN A KERNEL PANIC. THERE IS NO ----ING SUPPORT FOR RUNNING LION ON AMD. SO YOU LL HAVE FIX THIS YOURSELF.

panic(cpu 0 caller 0X2cfddf): Kernel trap at 0x002f76e7, type 17=page fault, registers:
CRO: 0x80010033, CR2: 0x00000124, CR3: 0x00101000, CR4: 0x00000660
ERX: 0x21000000, EBX: 0x00000000, ECX: 0x00000100, EDX: 0x00000001
CR2: 0x00010124, EBP: 0x8344b808, ESI: 0x202e74a0, EDI: 0x00000000
EFL: 0x00010286, EIP: 0x002f76e7, CS: 0x00000004, DS: 0x0000000c
Error code: 0x00000000

Debugger called: (panic)
Backtrace (cpu 0), Frame : Return Adress (4 potential args on stack)
0x8344b6b8 : 0x2203ea (0x719156 0x8344b6d8 0x229fc0 0x0)
0x8344b6b8 : 0x2cfddf (0x6be9e4 0x2f76e7 0xe 0x6be98d)
0x8344b798 : 0x2c2c02 (0x8344b7b8 0x8344b7a8 0x8344b7b0 0x568812)
0x8344b7b0 : 0x2f8ff1 (0xe 0x48 0x70 0xc)
0x8344b808 : 0x2f8ff1 (0x15427e80 0x0 0x8344b848 0x329713)
0x8344b848 : 0x30d69e (0x202e74a0 0x0 0x0 0x0)
0x8344b898 : 0x30d1bf (0x15427df0 0x37634538 0x0 0x0)
0x8344b8d8 : 0x30f4d0 (0x1 0x0 0x4fe519bc 0x4fe519bc)
0x8344b938 : 0x4f9f39 (0x0 0x34 0x8344b980 0x202e56b0)
0x8344b9c8 : 0x5025b3 (0x16525804 0x202e1314 0x8344be60 0x8344bb00)
0x8344bb28 : 0x32dec1 (0x8344bb48 0x0 0x8344bb68 0x6a5ae8)
0x8344bb68 : 0x304927 (0x202e1314 0x8344bd4c 0x8344be60 0x160fd70c)
0x8344bbc8 : 0x303630 (0x8344bd30 0x0 0x15720800 0x400)
0x8344bc38 : 0x32317b (0x8344bd30 0x15cf2d8c 0x150e17f0 0x0)
0x8344bc98 : 0x31bb20 (0x8344bd30 0x8344bcf8 0x8344be90 0x160fd70c)
0x8344bd08 : 0x31c12d (0x160fd70c 0x8344bd30 0x0 0x8344be90)
0x8344bf88 : 0x5f36cb (0x15cd1828 0x160fd60c 0x160fd650 0xc)
0x8344bfc8 : 0x2c3137 (0x1601ad5c 0x0 0x4 0x246)

BSD process name corresponding to current thread: mdworker
Boot args: boot-uuid=034D684-4663-3CD9-856D-CBAE7B8CE287 rd=*uuid -legacy -force64 userkernelcache=no .v .f npci=0x2000

Mac OS version:
11E53

Kernel version:
Darwin Kernel Version 11.4.0: Sa 19 Mai 2012 08:08:44:CEST: bronzovka v3 rev B:xnu-1699.26.8/BUILD/obj/RELEASE_I386
Kernel UUID: 29B5CB24-2DD0-3E9C-8967-104037044578
System model: MacPro5,1

System uptime in nanoseconds: 641097053904

how does one turn the CPU off Panic error message in the long term? Possibly patch write one or adapt the DSDT???? Ask for urgent assistance

PS: the stupid sentence of bronzovka is naturally not new