Crash on waking

Question

Level 1

30 points

Crash on waking

I have a new mid-2012 MBP 13 - 2.9GHz/8GB with a 256GB SSD, running OS 10.7.4. When I started off with the supplied version of the OS (10.7.2 or 3?), I could close the cover on the computer to sleep -- or use any other method -- and the computer would wake as expected. Then I updated the software, which rolled me to OS 10.7.4 plus a variety of other updates. Now, I my MBP 13 cannot sleep and wake without crashing. My screen freezes with a spinning pinwheel. My mouse can move that pinwheel, but all other inputs are not recognized. I searched the support discussions, but found no solutions that work for me. The most promising solution was to do a clean reload of the OS with a Time Machine backup. This is how I know that this behavior is related to the updated software. Any ideas?

MacBook Pro (13-inch, Mid 2012), Mac OS X (10.7.4)

Posted on Jul 11, 2012 11:44 AM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Jul 11, 2012 3:34 PM in response to tomfrenock

If you have more than one user account, these instructions must be carried out as an administrator.

If you have an optical drive, make sure there is no disc in it.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ If you’re running OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

Step 1

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.

Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged during the time something abnormal was happening. That time might be before or after the boot.

For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. If the problem is a system crash or shutdown failure, post the messages from before the boot time, when the system was about to crash or was failing to shut down. In either case, please include the BOOT_TIME message at the beginning or the end of the log extract.

Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Step 2

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Pleasedon’t post shutdownStall or hang logs — they're very long and not helpful.

Reply

Answer 2

tomfrenock Author

Level 1

30 points

Jul 12, 2012 8:02 AM in response to Linc Davis

Linc – Thanks for the suggested actions. I entered the BOOT_TIME command, but no messages were displayed. I have the following text for the period of this event. I checked for messages in the system diagnostic reports, but it was completely empty. Hope that this helps.

--------------------------------------------------------------------------

7/12/12 6:45:30.605 AM talagent: CGSConnectionRelinquishWindowRights(cid, newWindowNumber, reservedRights): CGError 1001 on line 619

7/12/12 6:45:33.309 AM FileSyncAgent: PROPFIND /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:C74E6657-75D7-42E2-B768-EAD2639F6AD6, auto-retries=0, manual-retries=0

7/12/12 6:45:33.427 AM FileSyncAgent: MKCOL /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:B77B4145-8E39-4DDE-B988-2B553E45B870, auto-retries=0, manual-retries=0

7/12/12 6:45:33.531 AM FileSyncAgent: LOCK /.FileSync (FAILED), httpStatusCode:503, errorType:100 (domain=DAVErrorDomain, code=30), transactionState:5, txnId:B4425BF2-E6DD-4003-B5D6-59D4B9C78701, auto-retries=1, manual-retries=0

7/12/12 6:46:19.219 AM com.parallels.vm.prl_pcproxy: QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory

7/12/12 6:46:19.219 AM com.parallels.vm.prl_pcproxy: QFileSystemWatcher: failed to add paths: /Library/Managed Preferences

7/12/12 6:47:18.936 AM com.apple.launchd.peruser.501: ([0x0-0x14014].com.apple.AppleSpell[320]) Exited: Killed: 9

7/12/12 6:47:18.936 AM com.apple.launchd.peruser.501: ([0x0-0x17017].com.apple.iTunesHelper[344]) Exited: Killed: 9

7/12/12 6:47:18.938 AM com.apple.launchd.peruser.501: (com.apple.talagent[263]) Exited: Killed: 9

7/12/12 6:47:19.226 AM iStatLocal: Checking for updates

7/12/12 6:48:26.202 AM com.apple.launchd.peruser.501: (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

7/12/12 6:48:26.205 AM com.apple.launchctl.Aqua: load: option requires an argument -- D

7/12/12 6:48:26.205 AM com.apple.launchctl.Aqua: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...

7/12/12 6:48:26.324 AM com.apple.launchd.peruser.501: (com.apple.launchctl.Aqua[239]) Exited with code: 1

7/12/12 6:48:27.252 AM SystemUIServer: MenuCracker 2.2 (/Library/Application Support/iStat local/extras/MenuCracker.menu)

See http://sourceforge.net/projects/menucracker

MenuCracker is now loaded. Ready to accept new menu extras.

7/12/12 6:48:27.253 AM SystemUIServer: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)

7/12/12 6:48:27.283 AM SystemUIServer: MenuCracker: Allowing "iStatMenusBattery".

7/12/12 6:48:27.295 AM SystemUIServer: MenuCracker: Allowing "iStatMenusCPU".

7/12/12 6:48:27.309 AM SystemUIServer: MenuCracker: Allowing "iStatMenusNetwork".

7/12/12 6:48:27.321 AM SystemUIServer: MenuCracker: Allowing "iStatMenusTemps".

7/12/12 6:48:27.336 AM SystemUIServer: Could not load menu extra NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded) for Class (null)

7/12/12 6:48:27.598 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 6:48:27.600 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 6:48:27.601 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 6:48:27.603 AM com.apple.Finder: Thu Jul 12 06:48:27 2012 Finder[250] (FileSync.framework) _SFSendMessage: gServerMessagePortName = 'com.apple.FileSyncAgent.iDisk'

7/12/12 6:48:27.605 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 6:48:27.734 AM SystemUIServer: iStat Menus loading extra - battery

7/12/12 6:48:27.822 AM FileSyncAgent: GET /internetservices/issupport/2_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:103 (domain=AYNetDBErrorDomain, code=8), transactionState:5, txnId:220930FC-A726-4E94-9B90-CF381ACA9AE7, auto-retries=2, manual-retries=0

7/12/12 6:48:27.838 AM SystemUIServer: iStat Menus loading extra - cpu

7/12/12 6:48:27.904 AM SystemUIServer: iStat Menus loading extra - network

7/12/12 6:48:28.025 AM SystemUIServer: iStat Menus loading extra - sensors

7/12/12 6:48:28.433 AM com.parallels.vm.prl_pcproxy: QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory

7/12/12 6:48:28.434 AM com.parallels.vm.prl_pcproxy: QFileSystemWatcher: failed to add paths: /Library/Managed Preferences

7/12/12 6:48:44.667 AM FileSyncAgent: PROPFIND /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:CC1BD7FB-3DE0-43CA-9625-DEF815C325EE, auto-retries=0, manual-retries=0

7/12/12 6:48:44.848 AM FileSyncAgent: MKCOL /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:30F051D6-2B19-4E2E-B1A8-FF89874D0815, auto-retries=0, manual-retries=0

7/12/12 6:48:45.029 AM FileSyncAgent: LOCK /.FileSync (FAILED), httpStatusCode:503, errorType:100 (domain=DAVErrorDomain, code=30), transactionState:5, txnId:EE8BDC77-A1E3-4183-AF47-F066178D2ED7, auto-retries=1, manual-retries=0

7/12/12 7:02:00.469 AM com.apple.launchd.peruser.501: (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

7/12/12 7:02:00.472 AM com.apple.launchctl.Aqua: load: option requires an argument -- D

7/12/12 7:02:00.472 AM com.apple.launchctl.Aqua: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...

7/12/12 7:02:00.623 AM com.apple.launchd.peruser.501: (com.apple.launchctl.Aqua[244]) Exited with code: 1

7/12/12 7:02:01.349 AM SystemUIServer: MenuCracker 2.2 (/Library/Application Support/iStat local/extras/MenuCracker.menu)

See http://sourceforge.net/projects/menucracker

MenuCracker is now loaded. Ready to accept new menu extras.

7/12/12 7:02:01.351 AM SystemUIServer: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)

7/12/12 7:02:01.390 AM SystemUIServer: MenuCracker: Allowing "iStatMenusBattery".

7/12/12 7:02:01.404 AM SystemUIServer: MenuCracker: Allowing "iStatMenusCPU".

7/12/12 7:02:01.413 AM SystemUIServer: MenuCracker: Allowing "iStatMenusNetwork".

7/12/12 7:02:01.423 AM SystemUIServer: MenuCracker: Allowing "iStatMenusTemps".

7/12/12 7:02:01.436 AM SystemUIServer: Could not load menu extra NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded) for Class (null)

7/12/12 7:02:01.592 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 7:02:01.594 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 7:02:01.596 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 7:02:01.599 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 7:02:01.947 AM SystemUIServer: iStat Menus loading extra - battery

7/12/12 7:02:01.951 AM com.apple.Finder: Thu Jul 12 07:02:01 2012 Finder[258] (FileSync.framework) _SFSendMessage: gServerMessagePortName = 'com.apple.FileSyncAgent.iDisk'

7/12/12 7:02:02.069 AM SystemUIServer: iStat Menus loading extra - cpu

7/12/12 7:02:02.120 AM FileSyncAgent: GET /internetservices/issupport/2_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:103 (domain=AYNetDBErrorDomain, code=8), transactionState:5, txnId:53F160F5-7E1F-480B-BF2E-D437A51B4BDA, auto-retries=2, manual-retries=0

7/12/12 7:02:02.167 AM SystemUIServer: iStat Menus loading extra - network

7/12/12 7:02:02.311 AM SystemUIServer: iStat Menus loading extra - sensors

7/12/12 7:02:02.792 AM com.parallels.vm.prl_pcproxy: QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory

7/12/12 7:02:02.792 AM com.parallels.vm.prl_pcproxy: QFileSystemWatcher: failed to add paths: /Library/Managed Preferences

7/12/12 7:02:14.237 AM FileSyncAgent: PROPFIND /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:6D87DAF8-9FBE-45A5-ADF4-B29A6BCC874B, auto-retries=0, manual-retries=0

7/12/12 7:02:14.350 AM FileSyncAgent: MKCOL /.FileSync (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:C794B1D2-EC95-426B-997A-A6A24AF7C8A0, auto-retries=0, manual-retries=0

7/12/12 7:02:14.463 AM FileSyncAgent: LOCK /.FileSync (FAILED), httpStatusCode:503, errorType:100 (domain=DAVErrorDomain, code=30), transactionState:5, txnId:4AFF1DAE-025C-4F17-99F5-D12B9EE61606, auto-retries=1, manual-retries=0

Reply

Answer 3

Linc Davis

Level 10

209,547 points

Jul 12, 2012 8:31 AM in response to tomfrenock

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:

Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).

*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem(s)?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Answer 4

tomfrenock Author

Level 1

30 points

Jul 12, 2012 9:55 AM in response to Linc Davis

OK ... decrypted File Vault then started in safe mode. Put the computer to sleep, and it did the same thing. I looked at the console again, with similar results. Here is the text from the 9:44 am event ...

------------------------------------------------------------------------------

7/12/12 9:44:07.432 AM com.apple.launchd.peruser.501: (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

7/12/12 9:44:07.437 AM com.apple.launchctl.Aqua: load: option requires an argument -- D

7/12/12 9:44:07.437 AM com.apple.launchctl.Aqua: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...

7/12/12 9:44:09.033 AM com.apple.launchd.peruser.501: (com.apple.launchctl.Aqua[122]) Exited with code: 1

7/12/12 9:44:11.263 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 9:44:11.272 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 9:44:11.275 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 9:44:11.281 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 9:44:11.429 AM com.apple.Finder: Thu Jul 12 09:44:11 2012 Finder[143] (FileSync.framework) _SFSendMessage: gServerMessagePortName = 'com.apple.FileSyncAgent.iDisk'

7/12/12 9:44:11.526 AM SystemUIServer: MenuCracker 2.2 (/Library/Application Support/iStat local/extras/MenuCracker.menu)

See http://sourceforge.net/projects/menucracker

MenuCracker is now loaded. Ready to accept new menu extras.

7/12/12 9:44:11.530 AM SystemUIServer: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)

7/12/12 9:44:11.616 AM SystemUIServer: MenuCracker: Allowing "iStatMenusBattery".

7/12/12 9:44:11.635 AM SystemUIServer: MenuCracker: Allowing "iStatMenusCPU".

7/12/12 9:44:11.661 AM SystemUIServer: MenuCracker: Allowing "iStatMenusNetwork".

7/12/12 9:44:11.687 AM SystemUIServer: MenuCracker: Allowing "iStatMenusTemps".

7/12/12 9:44:11.721 AM SystemUIServer: Could not load menu extra NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded) for Class (null)

7/12/12 9:44:11.789 AM SystemUIServer: Could not load menu extra NSBundle </System/Library/CoreServices/Menu Extras/Volume.menu> (not yet loaded) for Class AppleVolumeExtra

7/12/12 9:44:12.027 AM SystemUIServer: iStat Menus loading extra - battery

7/12/12 9:44:12.288 AM SystemUIServer: iStat Menus loading extra - cpu

7/12/12 9:44:12.436 AM SystemUIServer: iStat Menus loading extra - network

7/12/12 9:44:12.688 AM SystemUIServer: iStat Menus loading extra - sensors

Reply

Answer 5

Linc Davis

Level 10

209,547 points

Jul 12, 2012 10:02 AM in response to tomfrenock

Uninstall iStat and see whether there's any change.

Reply

Answer 6

tomfrenock Author

Level 1

30 points

Jul 12, 2012 10:28 AM in response to Linc Davis

Did it, and I thought that we were making some progress (wrong). After uninstalling iStat, I was able to go to sleep and wake with my password, but then the finder would crash. I repeated again with same result. I decided to do a PRAM reset ... same result. Then I did a SMC reset, and the crash occurred again at the login/password window. Here is some more script from my 10:22 event ...

--------------------------------------------------------------------------

7/12/12 10:20:25.546 AM com.apple.Finder: Thu Jul 12 10:20:25 2012 Finder[254] (FileSync.framework) _SFSendMessage: gServerMessagePortName = 'com.apple.FileSyncAgent.iDisk'

7/12/12 10:21:03.041 AM com.apple.launchd.peruser.501: ([0x0-0x7007].com.apple.Console[248]) Exited: Killed: 9

7/12/12 10:21:03.049 AM com.apple.launchd.peruser.501: (com.apple.talagent[252]) Exited: Killed: 9

7/12/12 10:21:03.057 AM com.apple.launchd.peruser.501: ([0x0-0x11011].com.apple.iTunesHelper[279]) Exited: Killed: 9

7/12/12 10:21:03.057 AM com.apple.launchd.peruser.501: (com.apple.quicklook[263]) Exited: Killed: 9

7/12/12 10:22:23.539 AM com.apple.launchd.peruser.501: (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

7/12/12 10:22:23.542 AM com.apple.launchctl.Aqua: load: option requires an argument -- D

7/12/12 10:22:23.542 AM com.apple.launchctl.Aqua: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...

7/12/12 10:22:23.754 AM com.apple.launchd.peruser.501: (com.apple.launchctl.Aqua[234]) Exited with code: 1

7/12/12 10:22:24.763 AM com.apple.Finder: Thu Jul 12 10:22:24 2012 Finder[245] (FileSync.framework) _SFSendMessage: gServerMessagePortName = 'com.apple.FileSyncAgent.iDisk'

7/12/12 10:22:24.939 AM com.parallels.vm.prl_pcproxy: QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory

7/12/12 10:22:24.942 AM com.parallels.vm.prl_pcproxy: QFileSystemWatcher: failed to add paths: /Library/Managed Preferences

7/12/12 10:22:25.012 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 10:22:25.013 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 10:22:25.014 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

7/12/12 10:22:25.015 AM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication

Reply

Answer 7

Linc Davis

Level 10

209,547 points

Jul 12, 2012 10:33 AM in response to tomfrenock

Please post the Finder crash report.

Reply

Answer 8

tomfrenock Author

Level 1

30 points

Jul 12, 2012 10:37 AM in response to Linc Davis

If I would find it under the Sys Diagnostic Reports, then there is none. If not in that grouping, then please tell me where to find it.Thanks again for all of this help.

Reply

Answer 9

Linc Davis

Level 10

209,547 points

Jul 12, 2012 10:51 AM in response to tomfrenock

User Diagnostic Reports.

Reply

Answer 10

tomfrenock Author

Level 1

30 points

Jul 12, 2012 11:13 AM in response to Linc Davis

All of my Diagnostic and Usage Information is empty. Sorry, no info.

Maybe I can add something ... I added the SSD after purchase. In setting up my machine, there was no OS 10.7 for the new hardware yet, so the local Mac store that I use cloned my original drive onto the SSD. In doing so, they told me that I will not have a Recovery Partition. Do you think that I am experiencing problems from this "cobbled configuration?" I can live with this situation if you think that it will go away when I update to Mt Lion.

Reply

Answer 11

Linc Davis

Level 10

209,547 points

Jul 12, 2012 11:16 AM in response to tomfrenock

Then the Finder didn't crash. Have you already reinstalled OS X? If not, do that next, after backing up all data.

Reply

Answer 12

tomfrenock Author

Level 1

30 points

Jul 12, 2012 11:53 AM in response to Linc Davis

Here is my history:

1) Purchase new MBP within days of release

2) Installed new OCZ 256GB SSD next day

3) Cloned original OS from HDD in MBP when purchased

4) Fresh installed of all apps and data (had licensing-caused problem with PGP WDE when Symantec took over -- seemed like fresh install would resolve some issues)

5) Reinstalled WDE to have computer completely locked up and unable to start

6) Reformatted SDD and recloned HDD image onto SDD

7) Reinstalled fresh again

8) Discovered sleep issue

9) Attempted variety of disk repairs with Disk Utility and Disk Warrior

10) Gave up and did a third cloning, but had Time Machine backup to use instead of all that reinstallation

------------------------------------------

11) Tried the sleep thing before updating the Apple software

12) -----> Had no sleep issues <------

------------------------------------------

13) Updated the Apple S/W via Software Update function (rolled OS from whatever was delivered wiht the MBP to 10.7.4)

14) Had sleep issue again, where the crash would occur at the login window

I guess that I already did the reinstallation. Note that the cloning was done because the OS10.7 disks do not support the firmware in this machine yet.

Thanks again for your interest and help.

Reply

Answer 13

Linc Davis

Level 10

209,547 points

Jul 12, 2012 12:23 PM in response to tomfrenock

Is PGP WDE still installed?

Reply

Answer 14

tomfrenock Author

Level 1

30 points

Jul 12, 2012 12:28 PM in response to Linc Davis

No, nor will it ever be again. Symatec ruined that product with whatever they did after the PGP acquisition.

I have an idea ... I can copy my original disk image onto another 2.5 SATA drive and install it without the Time Machine part. I can see what version of the OS came with my H/W, then update to 10.7.4 plus the other stuff. I would test the sleep thing with each iteration. Other than that, I can wait for Mt Lion to see if I can do a clean install with OS disks that support the new H/W.

Reply

Answer 15

Linc Davis

Level 10

209,547 points

Jul 12, 2012 1:15 PM in response to tomfrenock

You want to test with a completely clean system. If it doesn't work in that configuration, you have a warranty issue.

Reply