Windows 7 BSOD two nights in a row, while im asleep.. :S

[illusionxt]

Hi!

First off thanks for helping.

BSOD's only seem to occur during the night when i am asleep and the computer has gone to standby. I usually fall asleep with Windows Media Center left on...

This is a new rig everything is fresh.. I haven't really been able to catch what is causing the BSOD since i have not really seen it. But attached is everything...

But i would like to note that the minidump file 011212-9469-01.dmp was because actually the first one when i was setting the drivers up.. I believe that one is fixed. I'm more concerned about the other two BSOD's from Jan 16th (011612-10686-01) and Jan 15th (011512-9594-01).

There has not been any crashes or problems while the computer is in use.... the dude at NCIX (where i got all the parts) said that it might be the SSD and that i need to update its firmware? I haven't yet though.. just wanted to get some input before i do anything..

Attached are the requested files.


Thankyou kindly.

 

[Trouble]

Looks like both dumps are showing an issue with mv91xx.sys 8/27/2010 Marvell MV91xx AHCI/RAID driver see if you can find an updated driver here Marvell - Support - Driver Downloads
DUMP:

BugCheck 3D, {fffff80000b9bf60, 0, 0, fffff880010c578e}
Probably caused by : [COLOR=#ff0000][U][B]mv91xx.sys[/B][/U][/COLOR] ( mv91xx+3178e )
[COLOR=#ff0000][U][B]INTERRUPT_EXCEPTION_NOT_HANDLED (3d)[/B][/U][/COLOR]
Arguments:
Arg1: fffff80000b9bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff880010c578e
Debugging Details:
CONTEXT:  fffff80000b9bf60 -- (.cxr 0xfffff80000b9bf60)
rax=fffffa80091f4200 rbx=fffffa80092059e4 rcx=0000000000000001
rdx=fffffa80092059e4 rsi=0000000000000000 rdi=fffffa80092164e8
rip=fffff880010c578e rsp=fffff80000b9c940 rbp=fffffa80091f4748
 r8=fffff88004185180  r9=0000000000000003 r10=fffffa8009216560
r11=fffffa80091f50b0 r12=0000000000000100 r13=fffffa8009211f40
r14=fffffa80066f3040 r15=fffff80000b96080
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000293
[COLOR=#ff0000][U][B]mv91xx[/B][/U][/COLOR]+0x3178e:
fffff880`010c578e cc              int     3
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
CURRENT_IRQL:  b
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880010c578e
STACK_TEXT:  
fffff800`00b9c940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  [COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]  +0x3178e
FOLLOWUP_IP: 
  [COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]  +3178e
fffff880`010c578e cc              int     3
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:    [COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]    +3178e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][B][U]mv91xx.sys[/U][/B][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4c778a22
STACK_COMMAND:  .cxr 0xfffff80000b9bf60 ; kb
FAILURE_BUCKET_ID:  X64_0x3D_[COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]+3178e
BUCKET_ID:  X64_0x3D_[COLOR=#ff0000][B][U]mv91xx[/U][/B][/COLOR]+3178e

 

[Trouble]

Checked that link, nothing for that hardware device there that I could find.
Also checked your board mfg here ASUSTeK Computer Inc. - Motherboards- ASUS P8Z68-V PRO/GEN3 and it looks like the latest thing they have available is the one you have installed.
Googled mv91xx.sys seems you are not alone, you may want to check some of those links out or perhaps the support forums for your board here ASUSTeK Computer Inc.-Forum-

 

[illusionxt]

Hi Trouble!

Thanks for the quick reply,

I did a google search and managed to find a blogger who had the exact problem!
I followed his instructions and found a set of updated drivers, installed them and rebooted...

I shall followup tomorrow as to whether or not i wake up with another BSOD T_T

hopefully not! aha


thanks again!

 

[Trouble]

Thanks for the update, I did notice a link to a newer set of drivers on station-drivers.com and downloaded and extracted the executable and found that the version of mv91xx.sys was at least a year more current than the one that you are using.
Hopefully that will remedy your problem.
Keep us posted as you are able.
Regards
Randy