Upgrade to KT6V-LSR gone wrong, system freezes and BSOD's

Hi guys!
I just recently bought a KT6V-LSR to replace and Asrock K7S41GX motherboard. After putting all together (specs on signature) installed windows from scratch in a new partition on the master drive. Installed VIA 4 in 1, DirectX 9.0c, Catalyst 5.03, Realtek sound driver, LAN driver, USB patch, all of them were the latest versions available from the corresponding site, everything while the pc was not connected to the internet.. When I installed the Catalyst driver, rebooted the computer and it started testing the computer to find the "most stable settings" according to the installation said. The screen got all srambled but it seemed to bel going on, on the installation process it said that it'll take about 1 minute, waited about 5 an then restarted (it said that the test might cause the system not to respond anymore and that if it happened, restart it), it started all right. Then I installed NAV 2005. Installed acrobat reader. Then I tried to install Office 2003 and the system froze when it was about 15% of the copying files process. Restarted it and then the system crashed again the same way. If I leave the system running idle, it crashes randomly. It didn't show up with a BSOD at the beginning but now it shows
kernel_stack_inpage_error
0x00000077 (0xc000000E,0xc000000E,0xc00000000, 0x01b42000)
and another one
kernel_stack_inpage_error
0x0000007A (0xE14F862c,0xc000000E,0xcBF97B704, 0x02c23860)
(once each)
I'm thinking (from what I have read here) it might be the power supply, but since here in costa rica it's almost imposible to find a decent 400W PSU and I won't have the 100 bucks it costs for a couple of weeks more, is there anything I should try?
Temps on the system are 45-49 idle, 53-55 load. Applied thermal grease to the HS&F before installed it.
the 12+ (I've read is very important since the KT6V is very hungry on this rail) is showing up about 12 on the core center, but I've read that is not really representative...
Haven't updated to BIOS version 2.0 yet...
I checked the memory, ran only 1 stick and then the other one, on both slots.
I'm open to any advice, for sure I'll replace the PSU but that's gonna take a couple of weeks and I wanted to check if there's something I could try in the mean time.
Thanks a lot for your help!

Quote from: Olahahacos on 16-March-05, 14:22:12
Hey , Ford Tech , can you give an explanation of what the setup with the CD drive and the master harddrive on IDE 1 will do .
I have the same PSU nazgoth has .
I'm just interested in the affect that setup will have with the power in the system .
If you have noticed my posts its more of a house electricity thing with my setup , the harddrive not getting enough power , temporarily I hope .
Not really a voltage concern.But I guess it could if both drives are running at the same time.With IDE, one is limited to two drives in a chain, and these drives cannot work at the same time. In essence, they must "take turns".So by putting 1 HDD as primary master and cd as slave,you will get the full performance of your drive.Most peeps only run CD roms for program installs and or CD burning or copying anways.
As far as the cable,yes there are 80 wire flat cables that work just fine.The only reason to go to the round cables is to improve air-flow and or the length of the cable itself.
I am sure many people use it the old fashion way with no problems.I just experienced a performance issue when I had HDD's on the same chain.It was mainly because I load all my games on my D drive.It also kept defaulting it to PIO mode which is the slowest mode.Since swaping the drives around on the chain(IDE1=HDD-Operating system-primary master and CD burner as Primary slave)(IDE2=HDD-Storage/gaming-secondary master and my DVD rom as secondary slave)Both drives run in UMDA-MODE-5 set up that way with no more problems

Similar Messages

IMAC 20" intel - System freezes and screen goes blue - why??

this just started yesterday - I did not add any programs or update any software recently. I have since added Norton and scanned for viruses.
PROBLEM: my system freezes and the screen goes blue. It does not "wake" back up right away and after it goes blue a few times, it stays blue and I have to hard boot. If I leave the system off for about an hour, I'll get a few hours out of it before this happens.
DIAG: As stated above, I checked for viruses. I also ran all available diagnostics, and am fresh out of new ideas. Since I can't open my iMac without voiding the warrantee, I can't check for any possible burst or bulging capacitors. I disconnected all perperials and still have the same issue.
HYPOTHESIS: I am heavily leaning toward a hardware problem, but before I take the trip to the Apple store, I wanted to reach out to the forum to see if anyone else has had this problem?
This is an early 2006 Intel based 20" iMac that I have been running (24x7) since late August 2006. I never had an issue with my first iMac (pre-Intel).
HELP!!!
intel IMAC 20" Mac OS X (10.4.8)
intel IMAC 20" Mac OS X (10.4.8)

wrong forum - you should post here:
http://discussions.apple.com/forum.jspa?forumID=1110
max

Power Manager and LCD Brightness, System Freezes, and other Problems

I have a brand new X200 with PM 1.54. At first everything was working great. Over the past few days I've noticed a few things:
1. When running on battaries, the screen brightness changes about every 10 seconds even though the profile I'm using has that feature turned off.
2. After running the computer for about 1/2 hr, suddenly the PM shows a dramatic reduction in amount of time left on my battery which coinsides with:
a) fan consantly running; AND
b) about 10 minuntes later my entire system freezes and I have to push the power button to force a reboot.
Any ideas what's wrong?

Since your Mac Pro is new, you would do well to contact Apple about this problem while the warranty is still in effect.

Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results

Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results which I filed a report but did not receive an answer. The application to block scripts actually worsened the problem and I could not correct the situation for a while (no response from Firefox, at all). I have also been through this procedure without any one contacting me, AT ALL.
== URL of affected sites ==
http://http://www.facebook.com (always) and www.YouTube.com (sometimes)

There does appear to be any support whatsoever from mighty "non caring" FIREFOX & people are getting fed up. We may as well try another system, if they can't be bothered to provide any support for their system, we can't be bothered to use their system.
Brianeng

IMac monitor (my parents), the greys are so light and faint, they are almost impossible to see. especially in icalendar. i've gone into system preferences and i think i've tried everything there and checked the forums. no luck. any other suggestions?

monitor too faint to read. the greays on my monitor are so faint, they're almost impossible to see. especially the numbers of the dates in ical.
i've gone to system preferences and contrast controls. but no luck. any other suggestions? thank you

Thank you. I didn't know about the universal access adjustment. All the way left is a little better, but still much fainter than on my own imac. I'm not sure why apple uses grey typeface, but it's so faint on this imac monitor that it was difficult to find the "reply" option on this post. Are there any other suggestions? thank you

Msi z87 gd 65 gaming freezing and bsod

msi z87 gd 65 gaming freezing and bsod happens in a game or on desktop
build 26/09/2013 08:16 PM
i7 - 4770k
msi z87 gd65 gaming
corsair 32 gb ddr3 cmy32gx3m4a2400c10r
asus r9280x-dc2-3gd5 r9 280x
h110i corsair
corsair hx860i
crucial m4
cooler master cormos 2 case
system started to freeze and bsod
items I have done
osri
new psu
memtest all sticks and one at a time all passed
hd tune smart test passed
increased voltage on memory in case it was that as the x m p does it at 1.5v increase 4 steps from 1.5v to 1.9v all 4 gave the same issue
1.65v bsod as well
who crashed says amd ccc is causing the issue reinstalled with driver from asus and latest also the beta same issue is happening
this is why I think its the main board but was going to run the system from intel gpu by removing the amd gpu from system maybe even test an alt slot x8 to see what happens
currently testing r9 280z card with default gpu clock 850mhz instead of 1000mhz incase that's whats causing it
I know this is another post the other post does not have edit on the post any more so making you aware of this
any one got any ideas as to what to try next
On Sat 06/09/2014 04:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8346-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2DBA1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FFB3BA1, 0xFFFFF8800CFEE540, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 21:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8564-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600012E354)
Bugcheck code: 0x50 (0xFFFFFD00C0873680, 0x0, 0xFFFFF9600012E354, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 17:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-7909-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3267E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004A3267E, 0xFFFFF880060F6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 23:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-9796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00B7F9E50, 0x0, 0x15B641)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:54:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-7878-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800494A12B, 0xFFFFF88011FF4558, 0xFFFFF88011FF3DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-8470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF8F8F0, 0xFFFFF8800907E420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 02/09/2014 18:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8B00E9D800C, 0x0, 0xFFFFF8000397A981, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 15:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-7753-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800413B12B, 0xFFFFF88011DEF558, 0xFFFFF88011DEEDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 31/08/2014 08:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-8424-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880048308F7, 0xFFFFF88008DC2B00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 30/08/2014 22:58:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-9687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFDA801908C040, 0x2, 0x0, 0xFFFFF80003659EC9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No need to edit, just add a reply as flobelix asked for exact models of RAM and motherboard.
As it's double posting, this one gets locked. Please continue this one:
https://forum-en.msi.com/index.php?topic=183138.msg1314803#msg1314803
>>Please read and comply with the Forum Rules.<<
Topic Locked

Object spy on a pdf causes system freeze and reader crash

Hi,
When I try to spy on a a pdf the reader crashes, the Object spy freezes and I have to restart the machine to get back control.
It also makes IE8 crash if its an embeded pdf.
My configuration is QTP 11, IE8, XP, Adobe Reader 9.4 and the latest version of the tool kit.
It works fine if I try to run one of the sample test scripts that come with the tool kit.
The odd thing is that while I'm able do an Alt+Ctrl+Del and open the task manager I'm not able to do anything with it. It seems like the object spy has hijacked the mouse and wont let the system respond.
Does anyone have any suggestions?

Hi
We have lately found that due to some of our changes in Reader 10.1.2 release, the plugins have broken.
They still continue to work with Adobe Reader 10.1.0 and 10.1.1 ON ANY ENVIRONMENT WITH ANY QTP VERSION.
For the time being, before Adobe roll out a fix, we would suggest you not to upgrade the Adobe Reader versions.
Thanks and Regards

P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video

The Problem:
Temporary system freeze with audio stutter. The system recovers 30sec - 2min later.
Key presses made during freeze will execute after system recovers (ctrl+alt+delete for example)
Usually, but not always, I see an error message in the system tray and I do NOT experience bsod.
This happens seemingly at random from 3D accelerated applications, and web browsing. Games such as BF3 (moderate), WoW (seldom), Planetside 2 (frequently), Minecraft (seldom), Hawken (seldom), etc.
Also happens frequently in both Internet Explorer 9/10, Firefox, Chrome, and Steam store browser. Typically when watching steaming video (youtube, HULU, flow player, etc)
but Pandora audio streaming also seems to create the conditions where this happens.
Error Message:
"Display driver stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver 314.07 stopped
responding and has successfully recovered"
The problem also shows up in the Windows reliability history with the following data:
Source
Windows
Summary
Video hardware error
Date
‎3/‎6/‎2013 9:11 PM
Status
Not reported
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name:   LiveKernelEvent
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   1033
Files that help describe the problem
WD-20130306-2010.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode:   117
BCP1:   FFFFFA8011E0C4E0
BCP2:   FFFFF8800654A198
BCP3:   0000000000000000
BCP4:   0000000000000000
OS Version:   6_1_7601
Service Pack:   1_0
Product:   768_1
My System Hardware:
CPU: Intel i7 2600k @ 4.5ghz
Motherboard: MSI p67a-gd65 (B3 stepping)
Memory: G.SKILL Sniper 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
GPU: Originally MSI 6950 2GB. Replaced with EVGA 670 FTW 2GB.
PSU: CORSAIR HX Series HX850 850W
HDD: 3x Western Digital WD RE4 WD5003ABYX 500GB in Raid 0
OS: Windows 7 Home Premium SP1 with all updates
Case/Cooling: Silverstone Raven 2E with Thermalright silver arrow cpu heatsink
What I've tried:
Updated all motherboard drivers and bios (4.3) to current versions (no improvement)
Updated display drivers (in safe mode with driver sweeper. No improvement)
Updated Realtek Audio drivers for onboard sound (no improvement)
Updated Intel Rapid Storage drivers (no improvment)
Cleared CMOS and tested system at default settings with no overlock (no improvement)
Flashed 6950 back to 6950 stock bios and removed overclock (no improvement)
Replaced old 6950 with new GTX 670 (problem still occurs in the same exact way)
Tried GPU in 2nd PCIe slot. No improvement.
Checked GPU Temps. GTX 670 fan profile in EVGA Precision X set to keep temp below 70 degrees Celcius. Card maxes at 60 degrees under heavy gaming load.
Complete reformat of raid array with fresh install of Windows (4 different times) Seemed to help for a few days, then freezes came back
Ran OCCT and Prime 95 Torture tests separately for a few hours at stock and OC settings. System stable with core temps of high 50's overclocked, and low 40's stock.
Ran Memtest86 for 10 hours with zero errors.
Used digital multimeter to test 12v rail on PSU. Noted solid 12v reported. Didn't test other rails.
Unplugged PSU cables from motherboard and reattached firmly
Ran HD Tune and Data Life Guard Tools for error checking on hard disks. Zero errors found.
Disabled Windows Aero (no improvement)
Updated Adobe Flash Player to latest setting (no improvement)
Removed Adobe Flash Player (no improvement)
Turned off Adobe Flash hardware acceleration (no improvement)
*EDIT: Forgot that I also adjusted Nvidia driver profiles for apps that have frozen to include power preference to max performance
All of my hardware with the exception of the new 670 was purchased and configured back in February of 2011. This problem first occured in BF3 multiplayer sometime in early 2012,
and has gradually been happening more frequently. Web searches found many individuals with this error, but the solutions are all over the map, and I've tried just about everything that I've found.
I think I've narrowed the problem down to the motherboard, but I just can't find a clear answer or solution. Maybe it's the raid array? I really thought replacing the GPU would solve my trouble here
and I was...NOT happy when it happened again with the new 670 that I scored for $250 after amazon gift cards. I typically get kicked/disconnected during online game play when this happens and I'm ready to be done with it. I was hoping to fix the issue without needing to buy new hardware, but I don't see any other way at this point.
My patience runs thin. Please help!

Quote from: Froggy Gremlin on 11-March-13, 15:28:36
Might want to ask for the special archive to return the mainboard to pre-Ivy support UEFI/BIOS and then test again with everything set to auto/stock/default.
Already tested that before updating to 4.3. I started having the problem on 1.8, then 1.J0, then 4.3.
Quote from: Bernhard on 11-March-13, 15:30:29
Just a shot in the dark.
The length of time that your CPU has been running at the OC could have accelerated the eventual degradation.
Have you tested your CPU in another board or do you have access to a "known good" CPU to test in your system ?
I do not have another 1155 lga board to test the cpu in unfortunately, hence the CPU stress testing. Based upon previous experiences with multiple overclocked systems that I've run at much more aggressive overclocks, I don't believe I'm seeing a processor failure, though I can't rule out the possibility.
Quote from: xmad on 11-March-13, 23:26:01
Quite a few components can cause this.
Do you have a friend that could lend you a psu to test? A weak of failing PSU can often be the cause of something like this?
No I don't have another PSU to test. I did use a digital multimeter to test the 12v rail, as well as the motherboard contacts for testing voltage to the cpu and system They were all right in line with what I'm seeing reported in the bios. I did not test these contacts while the system was under load however, so I may need to do it again.

System freezes and restart after user login screen shows up

The interesting thing is thing is that the same thing happens on the bootcamp partition. Every time I turn on MBA mid 2012, when the login screen shows up, the computer freezes and than turns off. Same problem when I boot into bootcamp partition, the computer turns on, pass through windows logo and after the login screen shows, it turns off.
...forgot to mention that it's running osx 10.9
I figure out that I can log in with Sage Mode. Every time I log in with Safe Mode, the error popup message shows up saying about the error and its log. There is the log:
Anonymous UUID:       1975668F-0791-B095-A5DD-001905FAF4A7
Mon Nov 4 23:53:40 2013
panic(cpu 2 caller 0xffffff8002adc19e): Kernel trap at 0xffffff7f84801ee1, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000080, CR3: 0x000000003e429024, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0xffffff800f7ebc04, RCX: 0x000000000000000e, RDX: 0x0000000000000000
RSP: 0xffffff8081d32fc0, RBP: 0xffffff8081d32fd0, RSI: 0xffffff801121a03a, RDI: 0x0000000000000000
R8: 0xffffff801121a602, R9: 0x0000000000000000, R10: 0xffffff8003070850, R11: 0xffffff8003089ce8
R12: 0xffffff800fae8644, R13: 0x0000000000000000, R14: 0x00000000000164a4, R15: 0xffffff800fae864c
RFL: 0x0000000000010286, RIP: 0xffffff7f84801ee1, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000080, Error code: 0x0000000000000000, Fault CPU: 0x2
Backtrace (CPU 2), Frame : Return Address
0xffffff8081d32c50 : 0xffffff8002a22f69
0xffffff8081d32cd0 : 0xffffff8002adc19e
0xffffff8081d32ea0 : 0xffffff8002af3606
0xffffff8081d32ec0 : 0xffffff7f84801ee1
0xffffff8081d32fd0 : 0xffffff7f847f6388
0xffffff8081d33070 : 0xffffff7f8480de2d
0xffffff8081d33130 : 0xffffff7f84811951
0xffffff8081d332b0 : 0xffffff7f847fb2b8
0xffffff8081d33390 : 0xffffff7f847f882f
0xffffff8081d333e0 : 0xffffff7f847e7422
0xffffff8081d33790 : 0xffffff8002be2abf
0xffffff8081d33af0 : 0xffffff8002be363d
0xffffff8081d33f20 : 0xffffff8002be31d9
0xffffff8081d33f60 : 0xffffff8002e3db67
0xffffff8081d33fb0 : 0xffffff8002af3af8
      Kernel Extensions in backtrace:
         com.paragon-software.filesystems.ntfs(78.1.10)[C00EE7CC-736F-3A48-AC68-33826B2C4CDF]@0xffffff7f847e4000->0xffffff7f8481dfff
BSD process name corresponding to current thread: mount_ufsd_NTFS
Mac OS version:
13A603
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide:     0x0000000002800000
Kernel text base: 0xffffff8002a00000
System model name: MacBookAir5,2 (Mac-2E6FAB96566FE58C)
System uptime in nanoseconds: 12684772054
last loaded kext at 12348392875: com.paragon-software.filesystems.ntfs          78.1.10 (addr 0xffffff7f847e4000, size 237568)
loaded kexts:
com.paragon-software.filesystems.ntfs          78.1.10
com.protech.NoSleep          1.3.3
org.virtualbox.kext.VBoxUSB          4.2.16
org.virtualbox.kext.VBoxDrv          4.2.16
com.apple.driver.AudioAUUC          1.60
com.apple.filesystems.autofs          3.0
com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
com.apple.driver.AppleHDAHardwareConfigDriver          2.5.2fc2
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AGPM          100.14.11
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.ApplePlatformEnabler          2.0.9d1
com.apple.driver.AppleHDA          2.5.2fc2
com.apple.driver.AppleUpstreamUserClient          3.5.13
com.apple.iokit.IOBluetoothUSBDFU          4.2.0f6
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6
com.apple.driver.AppleMikeyDriver          2.5.2fc2
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.driver.AppleThunderboltIP          1.0.10
com.apple.driver.AppleIntelHD4000Graphics          8.1.8
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleHWAccess          1
com.apple.driver.AppleLPC          1.7.0
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.AppleSMCLMU          2.0.4d1
com.apple.driver.AppleMuxControl          3.4.12
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.12
com.apple.driver.AppleIntelFramebufferCapri          8.1.8
com.apple.driver.AppleUSBTCButtons          240.2
com.apple.driver.AppleUSBTCKeyEventDriver          240.2
com.apple.driver.AppleUSBTCKeyboard          240.2
com.apple.iokit.SCSITaskUserClient          3.6.0
com.apple.driver.AppleUSBCardReader          3.3.5
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          35
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.4.0
com.apple.driver.AirPort.Brcm4331          700.20.22
com.apple.driver.AppleUSBHub          650.4.4
com.apple.driver.AppleAHCIPort          2.9.5
com.apple.driver.AppleUSBEHCI          650.4.1
com.apple.driver.AppleUSBXHCI          650.4.3
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleRTC          2.0
com.apple.driver.AppleACPIButtons          2.0
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          2.0
com.apple.driver.AppleACPIEC          2.0
com.apple.driver.AppleAPIC          1.7
com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
com.apple.nke.applicationfirewall          153
com.apple.security.quarantine          3
com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
com.apple.kext.triggers          1.0
com.apple.iokit.IOSerialFamily          10.0.7
com.apple.driver.DspFuncLib          2.5.2fc2
com.apple.vecLib.kext          1.0.0
com.apple.iokit.IOAudioFamily          1.9.4fc11
com.apple.kext.OSvKernDSPLib          1.14
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
com.apple.iokit.IOSurface          91
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.iokit.IOBluetoothFamily          4.2.0f6
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleThunderboltEDMSink          1.2.1
com.apple.driver.AppleThunderboltDPOutAdapter          2.5.0
com.apple.driver.IOPlatformPluginFamily          5.5.1d27
com.apple.driver.AppleHDAController          2.5.2fc2
com.apple.iokit.IOHDAFamily          2.5.2fc2
com.apple.driver.AppleSMC          3.1.6d1
com.apple.driver.AppleSMBusPCI          1.0.12d1
com.apple.driver.AppleGraphicsControl          3.4.12
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.3.6
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.iokit.IOAcceleratorFamily2          98.7.1
com.apple.AppleGraphicsDeviceControl          3.4.12
com.apple.iokit.IOGraphicsFamily          2.3.6
com.apple.driver.AppleUSBMultitouch          240.6
com.apple.iokit.IOUSBHIDDriver          650.4.4
com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0
com.apple.iokit.IOUSBMassStorageClass          3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
com.apple.driver.AppleUSBMergeNub          650.4.0
com.apple.driver.AppleUSBComposite          650.4.0
com.apple.driver.AppleThunderboltNHI          1.9.2
com.apple.iokit.IOThunderboltFamily          2.8.5
com.apple.iokit.IO80211Family          600.34
com.apple.iokit.IONetworkingFamily          3.2
com.apple.iokit.IOUSBUserClient          650.4.4
com.apple.iokit.IOAHCIFamily          2.6.0
com.apple.iokit.IOUSBFamily          650.4.4
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          2.0.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          278.10
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.AppleKeyStore          2
com.apple.driver.DiskImages          371.1
com.apple.iokit.IOStorageFamily          1.9
com.apple.iokit.IOReportFamily          21
com.apple.driver.AppleFDEKeyStore          28.30
com.apple.driver.AppleACPIPlatform          2.0
com.apple.iokit.IOPCIFamily          2.8
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
com.apple.kec.pthread          1
Model: MacBookAir5,2, BootROM MBA51.00EF.B02, 2 processors, Intel Core i5, 1.8 GHz, 4 GB, SMC 2.5f9
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463235363634485A2D3147364D3120
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463235363634485A2D3147364D3120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 15 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD TS128E, 121,33 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Internal Memory Card Reader
Thunderbolt Bus: MacBook Air, Apple Inc., 23.4
Any ideas?

Problem solved... Figure out that in Safe Mode, the bootcamp partition is unmounted. So I thought that it could be the problem, when the login screen shows up, I guess the system was trying to mount the bootcamp partition and for some reason the computer was restarting. That's why the computer was turning off when I was trying to log in into Bootcamp partition also. So I wiped my bootcamp partition and resized the OSX partition. Now I can succesfully log in my user with out a problem

Spaces causing system freeze and logout

Recently (probably within the last 2-3 weeks) I've been having some issues with switching between spaces. It doesn't happen every time, but occasionally when I switch to another space my entire computer will freeze in the middle of the animation. After a few seconds, my screen will go blue and I'll get logged out.
Anybody else ever encounter this?

I have a similar problem with Spaces under OS X 10.6.4 on my MacBookPro5,3.
When I use Spaces from the keyboard to switch contexts to another window, the screen switching icon "sticks" to the display, and the keyboard only responds to the Spaces switching keystroke and some of the other "special" keys. However, the mouse continues to work, and I'm sometimes able to attempt a restart from the apple menu. But, the system still hangs about 50% of the time, forcing me to do a hard reset by holding down the power button.
I have had the blue screen experience once or twice, but I don't think it's related.
Other users where I work have reported nearly similar experiences with Spaces causing a system freeze.
I have, about 50% of the time, been able to use the mouse to disable other currently running utilities, one at a time, until the screen has become responsive. These utilities include:
Quicksilver
ClipMenu
TypeIt4Me
ShoveBox
It could be one of these is the culprit (my money's on ClipMenu and Quicksilver at the moment.)
I've also logged in via SSH from another machine and started whacking processes with some limited success. It seems there's some collision there with other running utilities, but I'm not sure what.
At this point, my only option is to disable Spaces and muddle through with a single desktop. Spaces crashes my system so consistently that it's not usable.
Sorry I don't have any other ideas to offer at this point.
-kb

X-Fi XtremeMusic - System freezes and crashes, MSI mother bo

Hi,
After installing X-Fi XtremeMusic to my system a problem appeared. As I noticed It appears mostly when I?m connected to the Internet and downloading something. The system freezes but this freezing is related to explorer.exe. The low panel with Start button freezes, connection to Internet finishes. If some other programs are working at that moment they function further but it is not possible to run new programs.So the system freezes or blue screen apears or computer restarts.
I tried to install the OS Windows XP Professional to a new disk dri've Seagate ST36082AS. After installing the OS, original drivers to my MSI mother board the computer was functioning well and downloading well too. Then I installed original driver for Sound Blaster X-Fi, DR release 2.7.3 and tried to start downloading. Soon the system freezed.
Please offer a solution.
Mother board: MSI MS-6590 (KT6 Delta) VIA? KT600 Chipset
BIOS: AMI 5.7 update date 2004--
RAM: 52 Mb.
CPU: Athlon 2500+
Dri've: Seagate ST36082AS 60 Gb
OS: Windows XP Professional SP2

MSI 865 Neo2 V
INTEL Prescott 3200
X-fi Xtreme Gamer
i've tried last bios 6.20 from MSI;
last chipset drivers from MSI
last X-fi drivers from creative SBXF_PCDRV_LB_2_09_0007
System still crashin' when X-fi is called to play any sound more then 2 min.
I know i'm a member of X-fi crash-club just now
good work to all drivers developers and marketing team too :P

System freeze and blue screen, help!

Hi guys,
Hopefully I can get some help on this...
I have a 2011 17inch MacBook Pro, intel core i7, 2.2Ghz, 4mb ram.
I've been having issues with the system freezing, like the screen goes a bit pixely and unresponsive and I'm forced to do a hard shutdown. On one occasion it has frozen with a blank blue screen which is rather scary! Also it has been running slower than normal...
I had issues before and took it to the Genius Bar and had the logic board replaced as well as the hard drive, this was less than a month ago.
Any ideas??
Cheers

You have a 90 day warranty for Apple repairs. It sounds as if you're having problems with the GPU, soldered onto the logic board.
I would advise taking the machine back to the Apple Store/AASP that repaired the machine and have them fix the logic board problem.
Good luck,
Clinton

I have just upgraded to OSX Maverick and now my Apple TV has taken over my iTunes videos. I have tried turning off homeshare and iHave gone into system prefs and disabled the remote, but the problem persists. Any ideas.

After upgrading to OSX Maverick my Apple TV has taken control of my iTunes videos insisting I have to watch it on my TV. I have tried disabling home sharing on iTunes and on the Apple TV menu, I have also checked the disable Infrared facility in Systems Prefs Security. Even if I put the Apple TV in standby as soon as I hit a key on my iMac, Apple TV comes back on and on my Itunes screen I get the Apple TV logo imprinted on the screen, meaning I can no longer watch it on my MAC, I have run out of ideas. Can anyone help.

I think you're headed the right direction. There is an AirPlay icon (on mine it is up near the play/pause controls) that I believe is used to set the default desitination for the video to play.
I'd never seen your issue before, but opened iTunes on a recently-upgraded-to-Mavericks MacBook and it did exactly as you described. While the video was loading, I switched the AirPlay option to the computer instead of ATV and it began playing locally (after a delay as you'd mentioned). I then read this page, which is actually quite old: http://forums.macrumors.com/showthread.php?t=1091073, which lead me to the icon near the play/pause button. It now has Computer selected on it, and defaults to play locally instead of the ATV even after quitting and reopening iTunes. I hope that is helpful.

Since upgrading to Yosemite my system freezes and crashes and gets panic messages

My 2009 13 in Mac freezes, beeps, crashes about 10 minutes after it comes on since I upgraded to Yosemite. Help please.

Good advice from Linc Davis that should sort out your query i think...
However you dont want to set your MBP to never go to sleep...
Adjust reasonable sleep settings...
And the download an APP called caffiene...
When you click it you can have your MBP never go to sleep with a single click of your menu bar... and with another click it can go to sleep normally to maintain the laptop...
Simply click the cup... To toggle never sleep/sleep

System freezes and wireless stopped working after update

Yesterday I ran my updates and the following were updated:
[2012-06-29 21:03] Running 'pacman -Syu'
[2012-06-29 21:03] synchronizing package lists
[2012-06-29 21:03] starting full system upgrade
[2012-06-29 21:08] upgraded ca-certificates-java (20120524-1 -> 20120608-1)
[2012-06-29 21:08] upgraded chromium (20.0.1132.43-1 -> 20.0.1132.47-1)
[2012-06-29 21:08] upgraded cryptsetup (1.4.2-2 -> 1.4.3-1)
[2012-06-29 21:08] upgraded docbook-xsl (1.77.0-1 -> 1.77.1-2)
[2012-06-29 21:08] upgraded grub2-common (1:2.00beta6-1 -> 1:2.00rc1-1)
[2012-06-29 21:08] upgraded grub2-bios (1:2.00beta6-1 -> 1:2.00rc1-1)
[2012-06-29 21:08] upgraded hplip (3.12.6-2 -> 3.12.6-3)
[2012-06-29 21:08] upgraded hyphen (2.8.3-1 -> 2.8.4-1)
[2012-06-29 21:08] upgraded imagemagick (6.7.7.7-1 -> 6.7.7.10-1)
[2012-06-29 21:08] upgraded libsystemd (185-3 -> 185-4)
[2012-06-29 21:08] upgraded systemd-tools (185-3 -> 185-4)
[2012-06-29 21:08] upgraded sysvinit (2.88-3 -> 2.88-6)
[2012-06-29 21:08] upgraded initscripts (2012.06.1-1 -> 2012.06.2-1)
[2012-06-29 21:08] upgraded keyutils (1.5.5-2 -> 1.5.5-3)
[2012-06-29 21:08] upgraded libnl (3.2.9-1 -> 3.2.11-1)
[2012-06-29 21:08] upgraded libusbx (1.0.12-1 -> 1.0.12-2)
[2012-06-29 21:08] upgraded libpcap (1.2.1-2 -> 1.3.0-1)
[2012-06-29 21:08] upgraded libquvi-scripts (0.4.5-1 -> 0.4.6-1)
[2012-06-29 21:08] upgraded linux-firmware (20120227-2 -> 20120625-1)
[2012-06-29 21:08] upgraded netcfg (2.8.3-1 -> 2.8.5-1)
[2012-06-29 21:08] upgraded pciutils (3.1.9-2 -> 3.1.10-1)
[2012-06-29 21:08] upgraded psmisc (22.18-2 -> 22.19-1)
[2012-06-29 21:08] upgraded qt (4.8.2-1 -> 4.8.2-2)
[2012-06-29 21:08] upgraded raptor (2.0.7-2 -> 2.0.8-1)
[2012-06-29 21:08] upgraded whois (5.0.16-1 -> 5.0.17-1)
Now today, after a reboot, my wireless card won't activate (I normally run on wired, but I needed to hook my printer up and its wireless) and the system locks up and freezes at random times (it just stops...the display displays everything as normal except nothing responds. there are no log messages in everything.log about it).
I have determined that the wireless problem probably came from the firmware update since when I tried to start the wireless card it said:
phy0 -> rt2x00lib_request_firmware: Error - Failed to request firmware
My wireless shows up in lspci as an Ralink Corp. RT2800 802.11n PCI which is correct.
How do I go about troubleshooting these issues? I am very new to Arch Linux (it's been a week or so now) so I think this will probably be a handy skill to have.

Looking at my currently loaded modules (using lsmod) it would seem that my wireless driver is loaded at the module level:
rt2800pci 9681 0
rt2800lib 43247 1 rt2800pci
rt2x00pci 5050 1 rt2800pci
rt2x00lib 35928 3 rt2x00pci,rt2800lib,rt2800pci
mac80211 395680 3 rt2x00lib,rt2x00pci,rt2800lib
cfg80211 170074 2 mac80211,rt2x00lib
I also found some handy output from dmesg:
[ 702.101074] systemd-udevd[4835]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 762.590997] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 762.591584] systemd-udevd[4878]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 1285.067769] systemd-udevd[928]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 1345.615907] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 1345.616427] systemd-udevd[931]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 2377.442112] systemd-udevd[24961]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 2438.494258] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 2438.494770] systemd-udevd[26660]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 2606.966231] systemd-udevd[3796]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
[ 2667.394993] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 2667.395348] systemd-udevd[3807]: segfault at 20 ip 000000000040dac7 sp 00007fff334e3580 error 4 in systemd-udevd[400000+2c000]
Since the firmware for this update just came out on the 27th is it possible something made its way in there and broke this? I can't seem to find anyone else who has had this problem and from all appearances it looks like it should be working (and it used to work quite well).
EDIT: One thing I am not sure about is that the firmware is in the firmware directory. Here are all the rt* firmwares. Is this correct or should there be an rt2x00 firmware in there?
-rw-r--r-- 1 root root 8192 Jun 14 20:10 rt2561.bin
-rw-r--r-- 1 root root 8192 Jun 14 20:10 rt2561s.bin
-rw-r--r-- 1 root root 8192 Jun 14 20:10 rt2661.bin
-rw-r--r-- 1 root root 8192 Jun 14 20:10 rt2860.bin
-rw-r--r-- 1 root root 8192 Jun 14 20:10 rt2870.bin
lrwxrwxrwx 1 root root 10 Jun 14 20:10 rt3070.bin -> rt2870.bin
-rw-r--r-- 1 root root 4096 Jun 14 20:10 rt3071.bin
lrwxrwxrwx 1 root root 10 Jun 14 20:10 rt3090.bin -> rt2860.bin
-rw-r--r-- 1 root root 4096 Jun 14 20:10 rt3290.bin
-rw-r--r-- 1 root root 2048 Jun 14 20:10 rt73.bin
rtl_nic:
total 44
-rw-r--r-- 1 root root 2076 Jun 14 20:10 rtl8105e-1.fw
-rw-r--r-- 1 root root 1492 Jun 14 20:10 rtl8168d-1.fw
-rw-r--r-- 1 root root 1324 Jun 14 20:10 rtl8168d-2.fw
-rw-r--r-- 1 root root 5500 Jun 14 20:10 rtl8168e-1.fw
-rw-r--r-- 1 root root 3920 Jun 14 20:10 rtl8168e-2.fw
-rw-r--r-- 1 root root 3872 Jun 14 20:10 rtl8168e-3.fw
-rw-r--r-- 1 root root 3136 Jun 14 20:10 rtl8168f-1.fw
-rw-r--r-- 1 root root 1232 Jun 14 20:10 rtl8168f-2.fw
-rw-r--r-- 1 root root 1824 Jun 14 20:10 rtl8402-1.fw
-rw-r--r-- 1 root root 1840 Jun 14 20:10 rtl8411-1.fw
rtlwifi:
total 272
-rw-r--r-- 1 root root 13540 Jun 14 20:10 rtl8192cfw.bin
-rw-r--r-- 1 root root 16014 Jun 14 20:10 rtl8192cufw.bin
-rw-r--r-- 1 root root 20526 Jun 14 20:10 rtl8192defw.bin
-rw-r--r-- 1 root root 88856 Jun 14 20:10 rtl8192sefw.bin
-rw-r--r-- 1 root root 129304 Jun 14 20:10 rtl8712u.bin
Last edited by Los Frijoles (2012-06-30 16:18:17)

Upgrade to KT6V-LSR gone wrong, system freezes and BSOD's

Similar Messages

Maybe you are looking for