I have recently built a new computer, unfortunately it has mostly created BSODs so far. So I was hoping for some help with the dumpfiles:

View attachment Seven Forums.zip

And the result from CPU-Z (only one memory stick in place):

CPU-Z memory.PNG CPU-Z spd.PNG

And a little history:

I've just built a computer with the following:
Motherboard: ASUS P8P67 EVO
CPU: Intel I5 2500K
Graphics: ASUS GTX570 DirectCUII
Memory: CORSAIR VENGANCE 2x4GB CL9 1600 MHz (now just 1x4)
SSD: Intel 320, 120 GB
HDD: 1.5 TB WD Caviar Green
PSU: FSP Aurum 700W
CPU cooler Antec kuler 620 H20
Optical: Samsung SH-b123L Blu-Ray reader

No OC, tried to set memory att different speeds (supposed to be 1600 but bios suggests 1333). I've gotten 2 types of BSODs on this system.

The first, 0x7e:
I got this when trying to install Win 7 Ultimate, which I got from MSDNAA. The BSOD always appeared when trying to boot from the intsllation disc, just when the windows logo animation started:

BSOD 7E Starting windows.jpg BSOD 7E.jpg

Tried different discs burned from the same installation, and one that my roommate used, same result.

I then tried with Win 7 Pro instead and could install it without problem.

The second and current BSOD, 0x3d:
After installing Win 7 Pro, all seamed fine. I installed drivers from the motherboard and graphic card CDs. I tried Crysis on top settings, it worked fine. I installed Avast anti virus. I tried to install a codec for the BD-reader, which didn't work, but no BSOD. The next day, however, I could open the browser and after maybe 5 min I got the BSOD.

From that point I've had plenty of BSODs at random times, even in Safe Mode. Each time I've tried to load the crysis-disc, when browsing, when running Windows update, when in idle, when logging in to windows.

Often when I got a BSOD, I'll get a new directly when logging in to windows the next few times, but after booting the Memtest-disc it usually works again.

I've tried formatting both SSD and HDD and made a new install. Then I installed drivers hand starded windows update. After several installations and reboots with windos update, the BSODs appeared again.

Some times I can run windows for long times, like now I've googled this problem for many hours, and watch streamed TV, with no problems, but I'm sure that I can get a new BSOD with the Crysis disc (since last windows installation, I haven't been able to install crysis).

So any help is greatly appreciated! What can I do about this?



Senior Member
Hello and welcome

can you please upload the minidump files so we can analyse them

they are located at %systemroot%/windows/minidump

once we have them we get data from them :)


Senior Member
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Arg1: fffff800044c9f80
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800115978e

Debugging Details:

CONTEXT:  fffff800044c9f80 -- (.cxr 0xfffff800044c9f80)
rax=fffffa800469e200 rbx=fffffa80046af9e4 rcx=0000000000000000
rdx=fffffa80046af9e4 rsi=0000000000000000 rdi=fffffa80046c0608
rip=fffff8800115978e rsp=fffff800044ca950 rbp=fffffa800469e748
 r8=fffff88003708100  r9=0000000000000002 r10=fffffa80046c0680
r11=fffffa800469f018 r12=0000000000000100 r13=fffffa80046bc1c0
r14=fffffa8005b24000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000293
fffff880`0115978e cc              int     3
Resetting default scope






LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800115978e

fffff800`044ca950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mv91xx+0x3178e

fffff880`0115978e cc              int     3


SYMBOL_NAME:  mv91xx+3178e

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  mv91xx.sys


STACK_COMMAND:  .cxr 0xfffff800044c9f80 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e

BUCKET_ID:  X64_0x3D_mv91xx+3178e

Followup: MachineOwner
fffff800`00bb9000 fffff800`00bc3000   kdcom    kdcom.dll    Sat Feb 05 12:21:45 2011 (4D4D40D9)
fffff800`02210000 fffff800`027ec000   nt       ntkrnlmp.exe Thu Jun 23 03:51:48 2011 (4E02AA44)
fffff800`027ec000 fffff800`02835000   hal      hal.dll      Tue Jul 14 02:27:36 2009 (4A5BDF08)
fffff880`00c14000 fffff880`00c58000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:29:10 2009 (4A5BDF66)
fffff880`00c58000 fffff880`00c6c000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`00c6c000 fffff880`00cca000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`00cca000 fffff880`00d8a000   CI       CI.dll       Tue Jul 14 02:32:13 2009 (4A5BE01D)
fffff880`00d8a000 fffff880`00de6000   volmgrx  volmgrx.sys  Tue Jul 14 00:20:33 2009 (4A5BC141)
fffff880`00de6000 fffff880`00dfa000   termdd   termdd.sys   Tue Jul 14 01:16:36 2009 (4A5BCE64)
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Tue Jul 14 00:19:34 2009 (4A5BC106)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`00e6a000 fffff880`00e9d000   pci      pci.sys      Tue Jul 14 00:19:51 2009 (4A5BC117)
fffff880`00e9d000 fffff880`00eaa000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`00eaa000 fffff880`00ebf000   partmgr  partmgr.sys  Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`00ebf000 fffff880`00ed4000   volmgr   volmgr.sys   Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`00ed4000 fffff880`00edb000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
fffff880`00edb000 fffff880`00eeb000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`00eeb000 fffff880`00ef6000   rdpbus   rdpbus.sys   Tue Jul 14 01:17:46 2009 (4A5BCEAA)
fffff880`00eff000 fffff880`00fa3000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
fffff880`00fa3000 fffff880`00fb2000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`00fb2000 fffff880`00fd3000   jraid    jraid.sys    Tue Aug 10 10:28:44 2010 (4C611BCC)
fffff880`00fd3000 fffff880`00fe4000   blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
fffff880`00fe4000 fffff880`00ff4000   CompositeBus CompositeBus.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1)
fffff880`00ff4000 fffff880`00fff000   mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
fffff880`01000000 fffff880`0103e000   1394ohci 1394ohci.sys Tue Jul 14 01:07:12 2009 (4A5BCC30)
fffff880`0103e000 fffff880`0104d000   mouclass mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
fffff880`0104d000 fffff880`0107c000   SCSIPORT SCSIPORT.SYS Tue Jul 14 01:01:04 2009 (4A5BCAC0)
fffff880`0107c000 fffff880`01096000   mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`01096000 fffff880`0109f000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`0109f000 fffff880`010c9000   ataport  ataport.SYS  Tue Jul 14 00:19:52 2009 (4A5BC118)
fffff880`010c9000 fffff880`010d4000   msahci   msahci.sys   Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`010d4000 fffff880`01160000   mv91xx   mv91xx.sys   Fri Aug 27 10:49:22 2010 (4C778A22)
fffff880`01160000 fffff880`01168000   mvxxmm   mvxxmm.sys   Fri Aug 27 10:49:03 2010 (4C778A0F)
fffff880`01168000 fffff880`01173000   amdxata  amdxata.sys  Tue May 19 18:56:59 2009 (4A12F2EB)
fffff880`01173000 fffff880`011bf000   fltmgr   fltmgr.sys   Tue Jul 14 00:19:59 2009 (4A5BC11F)
fffff880`011bf000 fffff880`011d3000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`011d3000 fffff880`011fd000   cdrom    cdrom.sys    Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`01206000 fffff880`013a9000   Ntfs     Ntfs.sys     Tue Jul 14 00:20:47 2009 (4A5BC14F)
fffff880`013a9000 fffff880`013d9000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`013d9000 fffff880`013f7000   i8042prt i8042prt.sys Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01400000 fffff880`0143a000   fvevol   fvevol.sys   Sat Sep 26 03:34:26 2009 (4ABD7DB2)
fffff880`0143a000 fffff880`01450000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01461000 fffff880`014bf000   msrpc    msrpc.sys    Tue Jul 14 00:21:32 2009 (4A5BC17C)
fffff880`014bf000 fffff880`014d9000   ksecdd   ksecdd.sys   Tue Jul 14 00:20:54 2009 (4A5BC156)
fffff880`014d9000 fffff880`0154c000   cng      cng.sys      Tue Jul 14 00:49:40 2009 (4A5BC814)
fffff880`0154c000 fffff880`0155d000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`0155d000 fffff880`01567000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
fffff880`01567000 fffff880`015b3000   volsnap  volsnap.sys  Tue Jul 14 00:20:08 2009 (4A5BC128)
fffff880`015b3000 fffff880`015ed000   rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A)
fffff880`015ed000 fffff880`015f6000   hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:03:32 2009 (4B21E0B4)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E)
fffff880`01695000 fffff880`01787000   ndis     ndis.sys     Tue Jul 14 00:21:40 2009 (4A5BC184)
fffff880`01787000 fffff880`017e7000   NETIO    NETIO.SYS    Tue Jul 14 00:21:46 2009 (4A5BC18A)
fffff880`017e7000 fffff880`017f9000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`01803000 fffff880`01a00000   tcpip    tcpip.sys    Tue Jun 21 04:44:55 2011 (4E0013B7)
fffff880`03400000 fffff880`03411000   usbehci  usbehci.sys  Tue Jul 14 01:06:30 2009 (4A5BCC06)
fffff880`03411000 fffff880`03467000   USBPORT  USBPORT.SYS  Tue Jul 14 01:06:31 2009 (4A5BCC07)
fffff880`03467000 fffff880`03497000   nusb3xhc nusb3xhc.sys Thu Sep 30 05:00:03 2010 (4CA40B43)
fffff880`03497000 fffff880`03498f00   USBD     USBD.SYS     Tue Jul 14 01:06:23 2009 (4A5BCBFF)
fffff880`03499000 fffff880`034a8000   kbdclass kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
fffff880`03534000 fffff880`0353c000   dump_mvxxmm dump_mvxxmm.sys Fri Aug 27 10:49:03 2010 (4C778A0F)
fffff880`0354f000 fffff880`03558000   Null     Null.SYS     Tue Jul 14 00:19:37 2009 (4A5BC109)
fffff880`03558000 fffff880`0355f000   Beep     Beep.SYS     Tue Jul 14 01:00:13 2009 (4A5BCA8D)
fffff880`0355f000 fffff880`0356d000   vga      vga.sys      Tue Jul 14 00:38:47 2009 (4A5BC587)
fffff880`0356d000 fffff880`03592000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
fffff880`03592000 fffff880`035a2000   watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
fffff880`035a2000 fffff880`035ad000   Msfs     Msfs.SYS     Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`035ad000 fffff880`035be000   Npfs     Npfs.SYS     Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`035be000 fffff880`035e2000   HDAudBus HDAudBus.sys Tue Jul 14 01:06:13 2009 (4A5BCBF5)
fffff880`035e2000 fffff880`035f3000   HECIx64  HECIx64.sys  Wed Oct 20 00:33:43 2010 (4CBE2AD7)
fffff880`035f3000 fffff880`035fc000   wmiacpi  wmiacpi.sys  Tue Jul 14 00:31:02 2009 (4A5BC3B6)
fffff880`035fc000 fffff880`035fd480   swenum   swenum.sys   Tue Jul 14 01:00:18 2009 (4A5BCA92)
fffff880`03c00000 fffff880`03c0a000   dump_diskdump dump_diskdump.sys Fri Apr 22 19:11:55 2011 (4DB1C4EB)
fffff880`03c0a000 fffff880`03c96000   dump_mv91xx dump_mv91xx.sys Fri Aug 27 10:49:22 2010 (4C778A22)
fffff880`03c96000 fffff880`03ca9000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
fffff880`03ccf000 fffff880`03d12000   ks       ks.sys       Thu Mar 04 04:32:25 2010 (4B8F37D9)
fffff880`03d12000 fffff880`03d1d000   btath_bus btath_bus.sys Thu Jun 24 07:17:43 2010 (4C22F887)
fffff880`03d1d000 fffff880`03d2f000   umbus    umbus.sys    Tue Jul 14 01:06:56 2009 (4A5BCC20)
fffff880`03d2f000 fffff880`03d89000   usbhub   usbhub.sys   Tue Jul 14 01:07:09 2009 (4A5BCC2D)
fffff880`03d89000 fffff880`03da2000   nusb3hub nusb3hub.sys Thu Sep 30 05:00:03 2010 (4CA40B43)
fffff880`03da2000 fffff880`03dae000   Dxapi    Dxapi.sys    Tue Jul 14 00:38:28 2009 (4A5BC574)
fffff880`03dae000 fffff880`03dbc000   hidusb   hidusb.sys   Tue Jul 14 01:06:22 2009 (4A5BCBFE)
fffff880`03dbc000 fffff880`03dd5000   HIDCLASS HIDCLASS.SYS Tue Jul 14 01:06:21 2009 (4A5BCBFD)
fffff880`03dd5000 fffff880`03ddd080   HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9)
fffff880`03dde000 fffff880`03deb000   mouhid   mouhid.sys   Tue Jul 14 01:00:20 2009 (4A5BCA94)
fffff880`03deb000 fffff880`03df9000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff960`00030000 fffff960`00342000   win32k   win32k.sys   unavailable (00000000)
fffff960`004c0000 fffff960`004de000   dxg      dxg.sys      unavailable (00000000)
fffff960`006d0000 fffff960`006da000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff960`00900000 fffff960`00909000   framebuf framebuf.dll unavailable (00000000)

Unloaded modules:
fffff880`01685000 fffff880`01693000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`01450000 fffff880`0145a000   dump_scsipor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
fffff880`034a8000 fffff880`03534000   dump_mv91xx.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0008C000
fffff880`0353c000 fffff880`0354f000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`01685000 fffff880`0168d000   spldr.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00008000
OK, from the information it appears to be pointing to " mv91xx.sys" which is related to your SSD ( marvel ) have you checked for a more updated driver

Marvell - Support - Driver Downloads

That is exciting! I was thinking about the SSD due to the suspicious behavior but didn't understood why I couldn't load CDs. But both SSD and BD-reader is connected to the Marvel-SATA-controller. I tried updating the drivers but it appeared that I already had the latest, so I put in the ASUS-CD to install the old driver, got a BSOD, but then installed it successfully.

I'll try Crysis again to see if I can provoke a new BSOD ...

No, didn't work. The auto-run window came up, and even the Crysis menu, but then BSOD. I think I got a glance of " mv91xx.sys" or something similar in the BSOD-window.

Here is the new dump:
View attachment 092411-9219-01.dmp

Could the SSD be damaged? Should I try installing Windows on the HDD? Or should I try connecting SSD and BD-reader to other SATA-ports (got 4x SATA2, 4x SATA3, 2 from Marvel).

Last edited:


Windows Forum Admin
Staff member
Premium Supporter
May I suggest before doing anything you install service pack 1 and update all your drivers. Don't use the ones off the cd as they're old and won't help at all

Firstly uninstall norton for now and replace with microsoft security essentials. Use the norton Removal tool
Rt64win7 Realtek network drivers need updating from here
Realtek HD Drivers need updating to 2,65 from Realtek
There are updated Nvidia GPU drivers at Nvidia
Jraid.sys needs updating from here

Last edited:
Hello, thanks for replying

Thought I had SP1, that might have been before I reinstalled windows. But I like to point out that the machine semed to work best before I tried windows update, I thought the some new driver might have caused problem.

but I'll try to install SP1 now.


Windows Forum Admin
Staff member
Premium Supporter
Hello, thanks for replying

Thought I had SP1, that might have been before I reinstalled windows. But I like to point out that the machine semed to work best before I tried windows update, I thought the some new driver might have caused problem.

but I'll try to install SP1 now.
May I suggest when using windows update to never use it's driver selections as they're normally older than the ones available from the manufacturer of your devices.

May I suggest when using windows update to never use it's driver selections as they're normally older than the ones available from the manufacturer of your devices.
I'll think about that.

Now I installed SP1 and som other things from windows update (no drivers) and all that you suggested except for the realtek HD driver which I couldn't find. I tried to load the Crysis disc again with BSOD as result:

View attachment 092411-9703-01.dmp

EDIT, might be solved!
I tried to connect the SSD and BD-reader to the SATA-2-ports (they only suport 3 Gbit/s), and now I could install Crysis! Now I just hope to be rid of future BSODs, at least these frequent ones.

It would be a loss if I cannot use the Marvel SATA-ports, but not a major one.

Thanks for your help and tips and time! I hope I won't need to bother you again!

Last edited:


Windows Forum Admin
Staff member
Premium Supporter
Was no bother so any questions and we'll be here :)

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.