The release date of the driver and the timestrap is always different. Timestrap lags by a few days, sometimes by a month too (for the immediate earlier ATI display driver). So it is not a problem. The driver version is the main thing to check.
joX201
Try this driver ( its for iaStor )
http://downloadcenter.intel.com/conf...&Dwnldid=22194
version: 11.7.0.1013
Don't download this until told .
VistaKing, xBluerobot hasnt suggested the latest version, there must be some reason.
Some of the latest versions of the RST drivers suffer from stability issue. I hope that version that XBlueRobot suggested is a good one, and we should continue to suggest that version or similar versions, not the very latest ones .... unless and untill people like Dave76 or NoelDP suggest for another stable version to us.
joX201, stay with the RST version that xBluerobot suggested.
Hi again,
More BSOD's... I don't have the machine with me now, but will post more diagnostics soon. It keeps throwing blue screens, apparently mostly with the same error messages in random order.
I just wanted to thank you guys for your support. You have put much more effort into this than the shameful Lenovo (which since the machine was new was only good to make me waste hours on the phone or writing emails that remain unanswered, and whose only attempt to fix it was to dump the blame on Microsoft because "Lenovo doesn't make software"... what a lame company, if i did this to my clients I'd be out of business in a whiz!).
Have a good weekend!
Cheers,
Jo
Very welcome, always happy to help, and will look forward for the diagnostics folder.
Yes, its true that Lenovo does not make software. But they do something. They bloat up the installations with some really unnecessary things. Suppost the AHCI controller. The system native controller never fails, whereas the intel RST elements are really crash prone. That intel'd driver that crashed your system for the last time we checked does not supplied by microsoft but bloated by (it may cause another debate, but it is always nothing but a bloatware to me) Lenovo.
If you want to get rid of the factory installation by Lenovo, that will be the best option for you. Follow the guide: Clean Reinstall - Factory OEM Windows 7
It will give you the perfect windows installation which will maximize windows efficiency only. And as your hardware are good, all the issues are for drivers and software, there is a fair chance that it will reduce the possibility of another BSOD.
Hi guys,
finally I get around to investing some more time on this machine...
Here are the newest diagnostic logs. Today it even crashed while the SF tool was making them.
BTW, I seem to understand the tool writes info on all the last crashes, not just the last one. Is this correct? In any case, I also added a screen capture of the blue screen tool.
I am considering going down the road of a clean install (again). I did this before contacting the forum, so possibly with small differences compared to its suggestions.
Any concerns with the approach? Anything to get out of the system before I go ahead?
Thanks,
Jo
cdrom.sys is a key Windows driver for the SCSI CD-ROM.Code:Event[15301]: Log Name: System Source: Service Control Manager Date: 2013-05-10 T08:50:35.238 Event ID: 7026 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: jostraso-X201 Description: The following boot-start or system-start driver(s) failed to load: cdrom
A few key Windows services were stopped, or failed to load, the Windows Anti-Malware service failed to update the signatures multiple times, eventually resulting in the Stop 0x3B BSOD. I also noticed that a few Lenovo services started before the Anti-Malware service began to crash, this may just be a coincidence.Code:Event[15314]: Log Name: System Source: Microsoft Antimalware Date: 2013-05-10 T08:50:38.000 Event ID: 2001 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: jostraso-X201 Description: Microsoft Antimalware has encountered an error trying to update signatures
The driver for the service has be seen within the call stack too:
Before performing a clean installation which may be the best option at the moment, have you checked and installed all the available Windows Updates?Code:fffff880`088405c8 fffff800`02ccad04 nt!KeBugCheckEx+0x104 fffff880`088405d0 0000007f`fffffff8 fffff880`088405d8 fffff800`02fe6000 nt! ?? ::NNGAKEGL::`string'+0x8a39 fffff880`088405e8 fffff880`01552000 MpFilter+0xb000 fffff880`088405f0 00000000`00000000 fffff880`088405f8 00000000`00000000 fffff880`08840600 00000000`00000282 fffff880`08840608 fffff800`02cca1a9 nt!KiBugCheckDispatch+0x69
Scan for any malware:
Hi x BlueRobot,
thanks again for your tips. If a clean install is my best chance to sort it out, perhaps I should jump into it and get it over with. I've got no data on this pc anyways. Do you agree?
A clean install would kill also any low-level virus, rootkits, or other mischievous stuff that may be at the origin of the crashes, correct?
@Arc: you also agree?
Yes, I agree. I also think that what is that making cdrom.sys fail at startup.
Download and install CCleaner. Then run it.
Go to "Tools" .... by default it will open the "uninstall" tab.
Click on save as text file. Save it on your desktop.
Upload the text file for us.
But if you opt for a clean reinstall, it will not be needed right now.
Quote