Home > Windows 10 > Windows 8.1 Freezing Event Id 129 And 153

Windows 8.1 Freezing Event Id 129 And 153

Contents

my Comp specs are: HDD1: 125GB HDD2: 60GB HDD3: 60GB Graphics: 1024 MB DDR3 GeForce GT 520 RAM: 4GB DDR2 Processor: 3.20GHz Intel Celeron D Usual activity: Gaming/Media streaming ISP of I downloaded this driver and i updated it with the device manager and is fixed, i think. Also, if you have any anti-malware stuff installed, disable or remove it and see if that helps. However, I did detail a work around for Win7/8 in the Lenovo forum. have a peek here

Thank you. Refer to the details below for more information." "The Windows write-cache buffer flushing policy can be enabled for all RAID array drives to ensure data integrity or disabled to improve data Still happens. In fact, it will be very nice once all your apps are updated to take full advantage of it.

Storahci 129 Windows 10

I think I'll be using Window's 7 mostly until the folks at Microsoft get their act together and fix Window's H8. I am among those people. My laptop specs are as follows: 2.4 GHz processor (AMD A4-4300M) and 6 GB RAM.

Is this number an exact power of -2? The controller is identified as a "Standard AHCI 1.0 Serial ATA Controller" though. Some other stuff is different, but they also added some cool things like the keyboard shortcut Win-X, which gives you a "Power User" popup menu on the desktop to get to Ahci Link Power Management Windows 10 What a freakin' mess this OS is - why the heck did they release it with all these bugaboos!

WARNING  —  disk  —  The IO operation at logical block address 5b9408 for Disk 1 was retried. Event 129 Reset To Device Device Raidport0 Was Issued Still, I have a few gripes: There are no more gadgets. Tnx very much Reply Mike3 June 2014 at 00:04Permalink I had a customer whose Windows 8 pc would freeze for 30 seconds or so, then the desktop would reset itself. I updated the driver using the "Browse my computer for driver software" option, and browsed to the location of the unzipped chip set package.

Notify me of new posts by email. Reset To Device Device Raidport0 Was Issued Iastora Under the Volumes tab for all (Intel Raid 0 Volume and both M4 devices) no information is shown. I ran chkdsk. In my PC, I chose to turn off some IIS related services which were checked.

Event 129 Reset To Device Device Raidport0 Was Issued

Additional Data: Error Value: C:\Program Files\Microsoft Security Client\MpCmdRun.exe. At least somebody cares enough to fix the problem! Storahci 129 Windows 10 Click Advanced and change the owner to Administrators group. Storahci Error 129 There are many solutions to be found on Google, but there is only 1 that worked for me… If you look in the event viewer, you will see that every time

There is something seriously wrong with Win 8 in the SSD/HDD department, and I'm still amazed that they haven't fixed it yet. navigate here Windows Installer, Windows Module Installer Worker, System, and few others I cant remember right now. I've tried them all.Some other strange items with this notebook (may or may not be related): when cold booting, sometimes the system will power itself right back off after the POST Officially there are no Win7 driver. Storahci Windows 10

I had the problem with Windows 7 after adding a Samsung SSD 850 EVO device. 10 minutes after a reboot / boot, invariably, I had twice the following event: Warning 27/03/2016 The Removal policy is set to Better performance (default) and both have Write-caching enabled, while M4-CT128 M4SSD2 doesn't have a Removal Policy. All the microsoft updates have been installed, drivers updated and registry cleaned. Check This Out windows-8 ssd storage share|improve this question edited Feb 12 '13 at 8:22 asked Feb 7 '13 at 12:14 Artem Tikhomirov 3222414 2 Have you checked your cables?

Thanks in advance for any help. Reset To Device /device/raidport0 Was Issued Windows 10 The BIOS information advises it is version Dell Inc 1.1.8, 18/04/2007 if that helps? I was experiencing something similiar to this.

EDIT: Well now, I installed version 12.8.2.1000 of Intel Rapid Storage Technology, and now I can suspend and hybrid sleep no problem now, even though (perhaps on Windows 8, not 8.1)

Maintenance :: Windows 8.1 Pro X64 Slow And Freezing Windows 8.1 - Mouse Freezing Then Unfreezing Windows 8.1 Freezing When Booting From Shutdown? WarningTaskScheduler414Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Windows\Media Center\PBDADiscoveryW2 definition. Reply 0 0 ChiefNoob Tutor Posts: 7 Member Since: ‎08-27-2015 Message 8 of 12 (3,995 Views) Report Inappropriate Content Re: Event ID 129 storahci followed by 153 causing periodical lock-up Options Event Id 153 Windows 10 Should I be looking to update anything else?

The solution can't be a downgrade to Windows 7 :/[email protected] which drivers did you use? After checking everything, and not finding any issues. With Win 7, everything "just worked". http://themenage.com/windows-10/windows-updating-freezing-laptop-unusable-acer.html Worse yet, I have experienced the infamous hanging/freezing issue that was supposedly fixed during the testing phases of Windows 8.

Sometimes they happen back to back, just minutes apart. View 9 Replies View Related Windows 8.1 - Mouse Freezing Then Unfreezing Feb 15, 2014 Windows 8.1 Pro x64 This is a significant issue and I'm having a lot of trouble Reply Relgoshan15 June 2013 at 11:56Permalink Greetings. The first one is the Event ID 257, Defrag Error.

This SanDisk drive seems to have its own non-Intel built-in controller that plays by its own rules. Reply 0 0 BaronMunchausen Top Student Posts: 3 Member Since: ‎06-10-2015 Message 3 of 12 (4,254 Views) Report Inappropriate Content Re: Event ID 129 storahci followed by 153 causing periodical lock-up I set to enable “hot swap” in the BIOS. If you search Google, you’ll find various explanations of how to fix this problem.

I have to chalk it up to Skype not being very compatible with Windows 8. share|improve this answer edited Jul 13 '16 at 20:52 answered Jul 13 '16 at 19:19 Paul 11 Hi Paul, thank you for your answer. Reply Scottie16 June 2013 at 11:56Permalink @Hector Aguilar M$ support is totally useless. and so on...

Here's all the specifics as recorded in my event log:The backing-file for the real-time session "DiagLog" has reached its maximum size.