New
#11
You dont need Rapid storage. Sata AHCI is controlled by its own drivers. Rapid Storage is practically is not anything necessary.
You dont need Rapid storage. Sata AHCI is controlled by its own drivers. Rapid Storage is practically is not anything necessary.
Thank you. I have uninstalled Rapid Storage. I will let you know how I get on this week.
Nope didnt work. Another bsod
iastor.sys is still rumbling around the system... what do I do with it? Rapid is now uninstalled? is the problem still being caused by iostor.sys?
From whocrashed
On Sun 23/09/2012 19:40:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-7004-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x16DF)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x57005C, 0xFFFFF8A015632250)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that the current thread is making a bad pool request.
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 which cannot be identified at this time.
attached dump files
The posted system logs are only till 27/08/012.
Please go to event viewer directly and right click on the system logs and application logs and save it as .evtx file as shown below and upload here
Attachment 233289
1. Why are you running Kaspersky and Windows Defender together ???
2. Please Remove System Requirements lab..
3. Please remove driver scanner... to update you driver.
4. Whats the firmware version of your SSD ?? Use this post to find out
Do these and let me know so the next set of advice can be given
Hi
1. Kaspersky was only installed last week and the problems have been happening a while before the install. Originally I had MSE installed and the problems were happening then. Defender is now disabled.
2. Done
3. Driver scanner uninstalled. Installed DS last week after the problems started.It never ran at startup so not sure why that would be a problem?
4. The SSD has latest firmware from Crucial 000F
I have attached the event logs as requested. I do not understand why you need these as I used the SF Diagnostic Tool previously to upload - grab all
I will wait and see if any further blue screens after doing the above
Last edited by ITeamdaytona; 24 Sep 2012 at 06:32.
Blus screen again after doing all of the above. Attached dump files. Please help someone
You need to check your HDD for errors.
- Reseat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.- If you are using a SSD, update the firmware.
Let us know the results.
Hi,
Not going to run chkdsk on the ssd as from what I have read that performs a lot of writes.
The latest firmware to the Crucial M4 was applied before installing Windows 7.
Are you saying there is nothing found then in all the dumps which points to a driver error?
It is Ntfs.sys.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffffffffe8, 0, fffff88001c5474a, 0} Could not read faulting driver name Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a ) Followup: MachineOwner ---------Ntfs.sys in the NT File System Driver, and it is a system driver. You cannot get it from outside, only via windows update. But, updating drivers via windows update is not always recommended.Code:fffff880`03b93c90 fffff880`01ca2050 Ntfs!NtfsData+0xd0 fffff880`03b93c98 fffffa80`039e5040 fffff880`03b93ca0 fffff880`01cd11f8 Ntfs!NtfsFspClose fffff880`03b93ca8 fffff800`030dd841 nt!ExpWorkerThread+0x111 fffff880`03b93cb0 00000000`00000000 fffff880`03b93cb8 fffff800`033c6600 nt!ObpWaitForMultipleObjects+0x4ca fffff880`03b93cc0 fffffa80`039e5001 fffff880`03b93cc8 00000000`00000003 fffff880`03b93cd0 fffff880`03b93ce0 fffff880`03b93cd8 20000500`00000001 fffff880`03b93ce0 fffff880`01ca2050 Ntfs!NtfsData+0xd0 fffff880`03b93ce8 020100a2`e4000804
Generally if the hard disk drive errors are there, the Ntfs.sys errors occur. That is why I suggested you to do that.
If you want, you may enable Driver Verifier again, to verify if any other driver is causing the crashes.
Ok reseated sata cable with a new one. Also power
Ran chkdsk and windows found no faults..
See results below
Will await the results