Bluescreens and MP crashes with new SSD (1 Viewer)

[regeszter]

chk the firmware of the ssd and upgrade if needs

 

[atlantic]

chk the firmware of the ssd and upgrade if needs

Yes good idea, but I think it's not possible to upgrade firmware when an OS is installed.
he will have to format the ssd and install again the OS.
(I have an OCZ SSD, and it's a restriction for it)

 

[regeszter]

I have OZC ssd (Aggility) too. You can upgarde the fw with a bootable linux cd which came from OZC.

 

[henning]

The firmware is upgradable, but not necessary. It is the most actual one.

 

[henning]

Ups, just pressed pause, a strange beeping sound appeared and voila, BSOD. There is no specific information about the cuase. It only says, that a problem hs been detected. Technical information is 0x0000001E. Rest of the hex values is 0x0. Does this give a clue to anybody?

 

[henning]

Checked the dump files with the BSOD viewer. The possible drivers that caused the BSOD are highlighted. Unfortunately there is no common result.

The ntoskrnl is mentioned quite often. But this is an NT kernel driver. This is nothing I can change, I would assume... The atikmpag.sys gives a link to my graphik card. The cmudaxp.sys seems to have something to do with my Asus Xonar DS. The drivers are all the most actual.

Hmm, this is still compleetly unclear to me.

051412-8517-01.dmp 14.05.2012 21:07:40 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 atikmpag.sys atikmpag.sys+5dbf x64 ntoskrnl.exe+7f190 C:\Windows\Minidump\051412-8517-01.dmp 2 15 7601 276.328
051112-12105-01.dmp 11.05.2012 20:38:34 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000018 00000000`00000002 00000000`00000000 fffff880`0407ef81 cmudaxp.sys cmudaxp.sys+1d1f81 x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\051112-12105-01.dmp 2 15 7601 276.360
051112-8517-01.dmp 11.05.2012 20:11:16 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc50 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17803 (win7sp1_gdr.120330-1504) x64 ntoskrnl.exe+7cc50 C:\Windows\Minidump\051112-8517-01.dmp 2 15 7601 276.328
051012-8985-01.dmp 10.05.2012 23:00:25 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000018 00000000`00000002 00000000`00000000 fffff880`04066f81 cmudaxp.sys cmudaxp.sys+1d1f81 x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\051012-8985-01.dmp 2 15 7601 276.328
050312-10826-01.dmp 03.05.2012 20:52:25 PNP_DETECTED_FATAL_ERROR 0x000000ca 00000000`0000000b fffffa80`01df4690 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+80640 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17803 (win7sp1_gdr.120330-1504) x64 ntoskrnl.exe+80640 C:\Windows\Minidump\050312-10826-01.dmp 2 15 7601 276.328
mbuzina: Will check your hint. Have reconnected the SSD and conacted everything as good as I can. Waiting for the next BSOD.

 

[atlantic]

Wow!
Not easy to understand.
Have you try to connect the ssd on another plug?
Try with another power supply, another sata cable.
Have you try to install again all your system?

 

[Scythe42]

0x1E is a general crash of the system due to hardware problems from the point of Windows, meaning a driver crashed for unknown reasons. For storage I would have expected something else.

First things to try:

• Re-install DirectX9. Problems with cmudaxp.sys are common when a Directx9 version are not ok.
• atikmpag.sys indicates that there is a problem with DVXA hardware acceleration during playback as cause of the crash. This could be driver related. Make sure you have the latest chipset drivers for your system installed.

Funny thing is. In your dump nothing is related to storage. But it could be that the latest change in the system triggered some other underlying problems.

When you installed your SSD, did you change any other hardware around the same time? Or was any additional software installed?

 

[henning]

I changed the sytsem from HDD with WinXP32 to SSD with Win7 64 bit. Nothing else - and nothing less. So the system itself is very fresh and no additional SW is installed. All drivers are of course different compared to my old system. And yes, it might be that the error is not SSD related at all. Thinking about, this was an assumption of mine and maybe a little bit overhasty.

Yesterday I checked the driver versions. Everything is the most actual, except the graphic card. The driver version info says version 09.7 is installed. That seemed strange, because I downloaded the 12.4 ati catalyst. So downloading again and reinstalled. The installation routine told me that everything is up to date. I nevertheless overinstalled the driver. At the end it is still version 09.7.

Maybe I will reinstall the system from the scratch.

 

[porky996t]

I don't know if it helps any, but when I went from Standard HDD to SSD I also went from Win 7 32 bit to 64 bit and kept getting BSOD. After much messing about, I eventually went back to a fresh install of Win7 32 bit and it has been stable ever since. I only went to x64 so I could access the extra RAM, but my RAMdrive software does that anyway.