Solved Sick of BSODs...

[elpeter]

Hello,
Since one week I've formatted my PC, and it gives me BSOD, could you please help me?

Thanks!!

Here is the system info:

Sistema
Modelo P5K Premium
Cantidad total de memoria del sistema 8,00 GB en RAM
Tipo de sistema Sistema operativo de 64 bits
Número de procesadores principales 4
Almacenamiento
Tamaño total de los discos duros 600 GB
Partición del disco (C: ) 58 GB disponibles (112 GB en total) Corsair Force3 SSD
Partición del disco (D: ) 318 GB disponibles (488 GB en total)
Unidad de medios (F: ) CD/DVD
Unidad de medios (G: ) CD/DVD
Gráficos
Tipo del adaptador de monitor Radeon X1950 Pro
Memoria de gráficos disponible en total 3323 MB
Memoria dedicada de gráficos 512 MB
Memoria dedicada del sistema 0 MB
Memoria compartida del sistema 2811 MB
Mostrar la versión del controlador del adaptador 8.593.100.0
Resolución del monitor principal 1680x1050
Resolución del monitor secundario 1280x1024
Versión de DirectX DirectX 9.0 o posterior
Red
Adaptador de red Realtek PCI GBE Family Controller
Adaptador de red Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Adaptador de red Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter​

Attached the needed files too.

P.S.: When I was posting this, the system gave another BSOD to me...

 

[zigzag3143]

Hello,
Since one week I've formatted my PC, and it gives me BSOD, could you please help me?

Thanks!!

Here is the system info:

Sistema
Modelo P5K Premium
Cantidad total de memoria del sistema 8,00 GB en RAM
Tipo de sistema Sistema operativo de 64 bits
Número de procesadores principales 4
Almacenamiento
Tamaño total de los discos duros 600 GB
Partición del disco (C: ) 58 GB disponibles (112 GB en total) Corsair Force3 SSD
Partición del disco (D: ) 318 GB disponibles (488 GB en total)
Unidad de medios (F: ) CD/DVD
Unidad de medios (G: ) CD/DVD
Gráficos
Tipo del adaptador de monitor Radeon X1950 Pro
Memoria de gráficos disponible en total 3323 MB
Memoria dedicada de gráficos 512 MB
Memoria dedicada del sistema 0 MB
Memoria compartida del sistema 2811 MB
Mostrar la versión del controlador del adaptador 8.593.100.0
Resolución del monitor principal 1680x1050
Resolución del monitor secundario 1280x1024
Versión de DirectX DirectX 9.0 o posterior
Red
Adaptador de red Realtek PCI GBE Family Controller
Adaptador de red Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Adaptador de red Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter​

Attached the needed files too.

P.S.: When I was posting this, the system gave another BSOD to me...

Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html




ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).

 

[elpeter]

Thanks!!! I've solved it with your help!! I've needed to format again, because was a problem with mi hdd configuration on BIOS, mi new HDD needs to be as "AHCI" as the manufacturer says on its FAQ (Welcome to Corsair) :banghead:
But I saw the problem with your help! THANKS A LOT!! ^^

Greetings!

 

[elpeter]

Unfortunately I was wrong... BSODs still occurs...
I've done MemTest, it was all 100% perfect
I've done the "verifier" test, and a new BSOD occurs... I'm collecting data to post it now... how can I mark the thread again as unsolved?

Thanks!

 

[elpeter]

Guess what... yeah!! Another BSOD when I was running the "Windows_NT6_BSOD_v3.03_jcgriff2_"... Cleaned results and runned again...

The results is attached. I've also attached the "verifier /query" output too.

Thanks for your help in advance...

 

[mgorman87]

The last crash was caused by avast!. I would uninstall and replace with Microsoft Security Essentials - Virus, Spyware & Malware Protection | Microsoft Security Essentials

Looks like there also might be an issue with your hard disk. I would run a hard drive scan to check it out

Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests


Also showing memory corruption as zigzag had previously stated. I would like you to run memtest again but this time run it from a cold boot. You only need to run it for 15-20 minutes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


I would like for you to also run the three Prime95 tests (Small FFTs, Large FFTs, Blend). Run each test for 3-4 hours or until it fails.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Lastly, I do not see ASACPI being loaded into your system anymore. Did you delete the driver?

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 18:54:48.758 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.257
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSnx.SYS ( aswSnx+4a0a2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_aswSnx+4a0a2
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 10:38:25.618 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.116
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 07:40:35.159 2011 (UTC - 4:00)
System Uptime: 0 days 12:48:29.047
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
[B][COLOR=Red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR][/B]
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[elpeter]

The last crash was caused by avast!. I would uninstall and replace with Microsoft Security Essentials - Virus, Spyware & Malware Protection | Microsoft Security Essentials

Done Hope it was only this...

Looks like there also might be an issue with your hard disk. I would run a hard drive scan to check it out

Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

Done, Both tests was right...

Also showing memory corruption as zigzag had previously stated. I would like you to run memtest again but this time run it from a cold boot. You only need to run it for 15-20 minutes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Done, 8 hours test and all was OK

I would like for you to also run the three Prime95 tests (Small FFTs, Large FFTs, Blend). Run each test for 3-4 hours or until it fails.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Actually running...

Lastly, I do not see ASACPI being loaded into your system anymore. Did you delete the driver?

Didn't delete it, it was update with version you've mentioned above...

I will post results of CPU stress... but I hope it was avast! the guilty one...

Thanks!!

 

[elpeter]

I would like for you to also run the three Prime95 tests (Small FFTs, Large FFTs, Blend). Run each test for 3-4 hours or until it fails.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Actually running...

I ran the first test for three hours and all was ok, nothing happens...

I'm running the second one...

Greetings.

 

[elpeter]

holly cr... another BSOD when running the second cpu stress test...
I attach the info...
Could you please throw me some light?

Thanks!

 

[elpeter]

Tonight another two BSODs while doing nothing...

Info attached...

Thanks.

 

[depthcharge]

Have you tried a Hardware clean Boot? check whether the issue persists after the CB. Its probably the driver issue.

 

[elpeter]

Have you tried a Hardware clean Boot? check whether the issue persists after the CB. Its probably the driver issue.

Sorry for my ignorance... How can I do that?

Thanks in advance paisano

 

[elpeter]

A few BSODs more...

I wrote to the SSD company, cause I think the SSD is the only guilty...

Thanks in advance...

 

[depthcharge]

Sorry, I was busy with work..

Option 1.

first try doing a clean boot with msconfig. Enter msconfig in the search menu. hit selective startup under general tab, uncheck load startup items, hit the services tab, check the option hide all Microsoft services and hit disable all. Then reboot.

Option 2.

Just enter devmgmt.msc into the start search. The device manager window should pop up. Disable the drivers for network adapter, display adapters, and try booting again.

Now check whether you have the BSOD again. If you are not having BSODs update the drivers to the latest version from the manufactures website. If its already up to date you can try a rollback to the previous version.

 

[mgorman87]

Your crashes are all pretty much the same and I'm almost 100% sure it is your SSD that is the culprit. Usually a firmware upgrade will fix the problem but I couldn't find them on the Corsair site. You also have a somewhat old motherboard that may be having issues with the SSD. I would contact both ASUS and Crucial and see if they can help you at all.


EDIT: I found the firmware upgrades. Read through the post and follow the instructions on upgrading your firmware
http://forum.corsair.com/v3/showthread.php?t=97417

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Aug 22 01:02:47.725 2011 (UTC - 4:00)
System Uptime: 0 days 1:02:45.224
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 23:59:06.187 2011 (UTC - 4:00)
System Uptime: 0 days 2:08:48.060
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 20:55:16.327 2011 (UTC - 4:00)
System Uptime: 0 days 0:57:19.199
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 19:57:22.194 2011 (UTC - 4:00)
System Uptime: 0 days 9:34:01.083
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Aug 21 10:22:24.295 2011 (UTC - 4:00)
System Uptime: 0 days 11:04:21.794
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Aug 20 23:16:55.279 2011 (UTC - 4:00)
System Uptime: 0 days 0:38:58.777
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Aug 20 22:36:48.663 2011 (UTC - 4:00)
System Uptime: 0 days 8:59:56.161
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Aug 20 13:35:54.420 2011 (UTC - 4:00)
System Uptime: 0 days 1:36:24.293
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Aug 20 05:57:24.008 2011 (UTC - 4:00)
System Uptime: 0 days 10:55:37.506
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
BiosReleaseDate = 12/17/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K Premium
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2405
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[elpeter]

Well, at first, thanks for your anwers, I've tried many things... Clean boot, driver separately and so on...
I wrote to the ssd company after firmware upgrado of the ssd (thanks for info!) and they told me that I must do a secure erase of all data and a system clean installation after all (unfortunatelly) I made all of this, and (cross my fingers) at the moment (one day after the clean SO installation) it seems to be ok. I'll keep informing of anything and I repeat, thanks for your answers

Greetings!

 

[elpeter]

A couple of days after, the system seems to be ok, no BSOD and I made many tests and all was ok. The solution was to upgrade the SSD firmware, performa a secure erase and make a clean SO installation. Thanls for all your help. I will mark the thread as solved. Thanks!!

Greetings.