BSOD on a HP dc7900 SFF with M500 Crucial SSD

[Rayon]

Hi all,

I have encountered several BSOD since I have upgraded my computer with a SSD see reference in the above subject.

Ex. When I have tried to install MS Office 2010 and/or the complete HP driver for my AIO printer ..

Please find herewith the report.

Hope that helps ..

Thank you so much in adavance.

Olivier.

 

[Arc]

Hi Rayon.

I am seeing two different things there.

First, the USB wireless adapter is failing when the computer wakes up from sleep.

• Search for any possible update to the device in Downloads - MediaTek
• And, Disable USB Selective Suspend too.
  USB Selective Suspend - Turn On or Off

The other one is more dense, and more frequent. The Crucial M500 240GB 2.5-inch Internal SSD.

• Make it sure that it is running with the latest firmware. Firmware Update MU03 dated 09/24/2013.
  Crucial.com Product Downloads - Firmware Updates
• Post a screenshot of the SSD using CrystalDiskInfo - Software - Crystal Dew World.

Let us know the results.
_____________________________________________________________

[COLOR=Red]BugCheck 9F[/COLOR], {3, 85a5d030, 8078adb0, 872f28b8}

Probably caused by : usbhub.sys

Followup: MachineOwner
--------------------------------------
>[ 16, 2]   0  0 85ab0028 00000000 00000000-00000000    
          [COLOR=Red]*** WARNING: Unable to verify timestamp for netr28u.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28u.sys
 \Driver\netr28u[/COLOR]
            Args: 00015400 00000001 00000004 00000003
 [ 16, 2]   0 e1 85af3e08 00000000 00000000-00000000    pending
           \Driver\vwifibus
            Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-85043ec8    

            Args: 00000000 00000000 00000000 00000000

[COLOR=Red]BugCheck F4[/COLOR], {3, 85a85978, 85a85ae4, 82a2deb0}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  [COLOR=Red]Typically caused by
a bad block in the paging file or disk controller error.[/COLOR] Also see
KERNEL_STACK_INPAGE_ERROR.
[COLOR=Blue]If the error status is 0xC000000E,[/COLOR] 0xC000009C, 0xC000009D or 0xC0000185,
[COLOR=Blue]it means the disk subsystem has experienced a failure.[/COLOR]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.

[COLOR=Blue]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.[/COLOR]

[COLOR=Red][B]DISK_HARDWARE_ERROR: There was error with disk hardware[/B][/COLOR]

[COLOR=Red][B]4077 errors : !nt[/B][/COLOR] (82b38000-82b38fff)