0x0000003D BSOD - Windows 7 can't even login - Help?

[FlyingLotus]

My PC now blue screens at what appears to be random times. Sometimes it happens when I'm using the internet or it happens right as my computer starts up, but now it does it as I log into Windows 7. The blue screen says INTERRUPT_EXCEPTION_NOT_HANDLED at the top and at the bottom it says STOP: 0x0000003D. I also have my OS installed on my SSD.

I'm guessing it may be to do with my drivers. My bios version is old and I think I haven't got the latest drivers on some things. My PC only started getting the BSOD after I took it to PC world and I installed my new PSU...

I've tried startup repair - that fails

Last known good configuration - that blue screens right after

I've been trying to figure out how to re install my windows 7 but I can't figure it out....

Before this BSOD I was also getting the c210000a fatal system error BSOD, which I think means I need to reinstall windows?

 

[x BlueRobot]

Are you able to boot into Safe Mode?

 

[FlyingLotus]

Are you able to boot into Safe Mode?

I tried before I think but Safe Mode with Networking and I got the BSOD, I'm basiclally getting the BSOD every time I boot up now. Okay I just did Safe Mode, I'm successfully in although everything is somewhat zoomed in and big. I'm still in safe mode and there's been no BSOD yet.

 

[x BlueRobot]

Okay, it seems to most likely a driver issue at the moment, try and follow these instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html, I'm not sure if the SF_Diagnostic Tool will work within Safe Mode or not, it will gather all the dump files etc.

If the tool isn't able to work, then please - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html - configure a Minidump to be saved, and attempt to boot normally to cause a BSOD, from here either run the SF_Diagnostic Tool (part of the BSOD Posting instructions) or upload the dump files manually with http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.

The dump files will saved within this directory:

C:\Windows\Minidump or %systemroot%\Minidump

 

[FlyingLotus]

Okay, it seems to most likely a driver issue at the moment, try and follow these instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html, I'm not sure if the SF_Diagnostic Tool will work within Safe Mode or not, it will gather all the dump files etc.

If the tool isn't able to work, then please - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html - configure a Minidump to be saved, and attempt to boot normally to cause a BSOD, from here either run the SF_Diagnostic Tool (part of the BSOD Posting instructions) or upload the dump files manually with http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.

The dump files will saved within this directory:

C:\Windows\Minidump or %systemroot%\Minidump

On that my PC already has write debugging information as kernel memory dump.

Should I keep this or change it to small memory dump?

 

[FlyingLotus]

Okay, it seems to most likely a driver issue at the moment, try and follow these instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html, I'm not sure if the SF_Diagnostic Tool will work within Safe Mode or not, it will gather all the dump files etc.

If the tool isn't able to work, then please - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html - configure a Minidump to be saved, and attempt to boot normally to cause a BSOD, from here either run the SF_Diagnostic Tool (part of the BSOD Posting instructions) or upload the dump files manually with http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.

The dump files will saved within this directory:

C:\Windows\Minidump or %systemroot%\Minidump

I have the DMP file here in my C drive - Windows - Minidump - although I'm not sure what to do with it now? I can't use the diagnostics tool... As the files are DMP's how am I supposed to upload them as images?

 

[FlyingLotus]

Okay, it seems to most likely a driver issue at the moment, try and follow these instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html, I'm not sure if the SF_Diagnostic Tool will work within Safe Mode or not, it will gather all the dump files etc.

If the tool isn't able to work, then please - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html - configure a Minidump to be saved, and attempt to boot normally to cause a BSOD, from here either run the SF_Diagnostic Tool (part of the BSOD Posting instructions) or upload the dump files manually with http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.

The dump files will saved within this directory:

C:\Windows\Minidump or %systemroot%\Minidump

I have attatched the .dmp file in a zip folder as I could find no other way of sending it! Hopefully you can help me out.

 

[FlyingLotus]

I managed to be quick enough to download blue screen view and it said my bsod is

caused by driver: mv91xx.sys

caused by address: mv91xx.sys+3178e

 

[FlyingLotus]

What do I do now?? I have no idea I'm in device manager but I'm not sure how to locate this driver and what to do when I do?

 

[FlyingLotus]

Okay so I downloaded this marvell controller driver and made sure it was the latest one, now I got another BSOD on startup.... -.-

 

[FlyingLotus]

Here's my DMP in txt format -

071113-7940-01.dmp 11/07/2013 20:54:01 INTERRUPT_EXCEPTION_NOT_HANDLED 0x0000003d fffff880`0af994e0 00000000`00000000 00000000`00000000 fffff880`0103178e mv91xx.sys mv91xx.sys+3178e x64 ntoskrnl.exe+75c00 C:\Windows\Minidump\071113-7940-01.dmp 8 15 7601 276,720 11/07/2013 20:55:22

 

[FlyingLotus]

now I can't even boot into safe mode without getting the BSOD! Can anyone help me out here?

 

[x BlueRobot]

BSOD Analysis:

[COLOR=Red]BugCheck 3D[/COLOR], {fffff8800af994e0, 0, 0, fffff8800103178e}

*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : [COLOR=Red]mv91xx.sys[/COLOR] ( mv91xx+3178e )

Okay, from my understanding, it seems that a device interrupt was issued, but wasn't able to handled, since the nature of the IRQ didn't have a corresponding ISR within the IDT table for the processor.

0: kd> [COLOR=SeaGreen]!prcb[/COLOR]
PRCB for Processor 0 at fffff780ffff0000:
[COLOR=Blue]Current IRQL -- 11[/COLOR]
Threads--  Current fffffa8006c67510 Next 0000000000000000 Idle fffff80003866cc0
Processor Index 0 Number (0, 0) GroupSetMember 1
Interrupt Count -- 00e03fd3
Times -- Dpc    0000203c [COLOR=Red]Interrupt 00000f93 [/COLOR]
         Kernel 0002fde3 User      0000685b

0: kd> [COLOR=SeaGreen]lmvm mv91xx[/COLOR]
start             end                 module name
fffff880`01000000 fffff880`0108c000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        [COLOR=Red]Fri Aug 27 10:49:22 2010[/COLOR] (4C778A22)
    CheckSum:         00050BB0
    ImageSize:        0008C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

mv91xx.sys belongs to your Marvell MV91xx AHCI/RAID driver, and since you have updated the driver, then it may be best to begin testing the hard drive.

0: kd> [COLOR=SeaGreen]kv[/COLOR]
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0af98c28 fffff800`036dd1a9 : 00000000`0000003d fffff880`0af994e0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0af98c30 fffff800`036d9509 : 00000000`00000000 00000000`00000000 fffff880`0af994e0 fffff800`03708a90 : nt!KiBugCheckDispatch+0x69
fffff880`0af98d70 fffff800`0370875d : fffff800`038eb978 fffff800`0382ce18 fffff800`03668000 fffff880`0af99c88 : nt!KiInterruptHandler+0x29
fffff880`0af98da0 fffff800`03707535 : fffff800`0382ce10 fffff880`0af98e18 fffff880`0af99c88 fffff800`03668000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0af98dd0 fffff800`037184d1 : fffff880`0af99c88 fffff880`0af994e0 fffff880`00000000 fffffa80`07c0e4e8 : nt!RtlDispatchException+0x415
fffff880`0af994b0 fffff800`036dd282 : fffff880`0af99c88 fffffa80`07bfdb60 fffff880`0af99d30 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0af99b50 fffff800`036db0b4 : 00000000`00000000 fffff880`01be2bb8 00000000`00000000 fffff880`01be2b70 : nt!KiExceptionDispatch+0xc2
fffff880`0af99d30 fffff880`0103178f : fffffa80`07823008 00000000`00000000 fffffa80`077d5060 fffff880`039fb100 : [COLOR=Red]nt!KiBreakpointTrap[/COLOR]+0xf4 (TrapFrame @ fffff880`0af99d30)
fffff880`0af99ec0 fffffa80`07823008 : 00000000`00000000 fffffa80`077d5060 fffff880`039fb100 fffffa80`07c0e4e8 : [COLOR=Red]mv91xx+0x3178f[/COLOR]
fffff880`0af99ec8 00000000`00000000 : fffffa80`077d5060 fffff880`039fb100 fffffa80`07c0e4e8 fffffa80`07c0a2b0 : 0xfffffa80`07823008

--------------------------------------------------------------------------

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[FlyingLotus]

BSOD Analysis:

[COLOR=Red]BugCheck 3D[/COLOR], {fffff8800af994e0, 0, 0, fffff8800103178e}

*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : [COLOR=Red]mv91xx.sys[/COLOR] ( mv91xx+3178e )

Okay, from my understanding, it seems that a device interrupt was issued, but wasn't able to handled, since the nature of the IRQ didn't have a corresponding ISR within the IDT table for the processor.

0: kd> [COLOR=SeaGreen]!prcb[/COLOR]
PRCB for Processor 0 at fffff780ffff0000:
[COLOR=Blue]Current IRQL -- 11[/COLOR]
Threads--  Current fffffa8006c67510 Next 0000000000000000 Idle fffff80003866cc0
Processor Index 0 Number (0, 0) GroupSetMember 1
Interrupt Count -- 00e03fd3
Times -- Dpc    0000203c [COLOR=Red]Interrupt 00000f93 [/COLOR]
         Kernel 0002fde3 User      0000685b

0: kd> [COLOR=SeaGreen]lmvm mv91xx[/COLOR]
start             end                 module name
fffff880`01000000 fffff880`0108c000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        [COLOR=Red]Fri Aug 27 10:49:22 2010[/COLOR] (4C778A22)
    CheckSum:         00050BB0
    ImageSize:        0008C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

mv91xx.sys belongs to your Marvell MV91xx AHCI/RAID driver, and since you have updated the driver, then it may be best to begin testing the hard drive.

0: kd> [COLOR=SeaGreen]kv[/COLOR]
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0af98c28 fffff800`036dd1a9 : 00000000`0000003d fffff880`0af994e0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0af98c30 fffff800`036d9509 : 00000000`00000000 00000000`00000000 fffff880`0af994e0 fffff800`03708a90 : nt!KiBugCheckDispatch+0x69
fffff880`0af98d70 fffff800`0370875d : fffff800`038eb978 fffff800`0382ce18 fffff800`03668000 fffff880`0af99c88 : nt!KiInterruptHandler+0x29
fffff880`0af98da0 fffff800`03707535 : fffff800`0382ce10 fffff880`0af98e18 fffff880`0af99c88 fffff800`03668000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0af98dd0 fffff800`037184d1 : fffff880`0af99c88 fffff880`0af994e0 fffff880`00000000 fffffa80`07c0e4e8 : nt!RtlDispatchException+0x415
fffff880`0af994b0 fffff800`036dd282 : fffff880`0af99c88 fffffa80`07bfdb60 fffff880`0af99d30 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0af99b50 fffff800`036db0b4 : 00000000`00000000 fffff880`01be2bb8 00000000`00000000 fffff880`01be2b70 : nt!KiExceptionDispatch+0xc2
fffff880`0af99d30 fffff880`0103178f : fffffa80`07823008 00000000`00000000 fffffa80`077d5060 fffff880`039fb100 : [COLOR=Red]nt!KiBreakpointTrap[/COLOR]+0xf4 (TrapFrame @ fffff880`0af99d30)
fffff880`0af99ec0 fffffa80`07823008 : 00000000`00000000 fffffa80`077d5060 fffff880`039fb100 fffffa80`07c0e4e8 : [COLOR=Red]mv91xx+0x3178f[/COLOR]
fffff880`0af99ec8 00000000`00000000 : fffffa80`077d5060 fffff880`039fb100 fffffa80`07c0e4e8 fffffa80`07c0a2b0 : 0xfffffa80`07823008

--------------------------------------------------------------------------

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

I don't think I'm going to be able to update stuff as I can't boot into windows normally and when i boot into safe mode i get to my login password bit and it blue screens straight away... Do you think if I bought another ssd or just bought a hdd to install windows on that may solve it? (I also got overclocking failed appear on some of my boots, I looked and it seems like when I took my PC for repair they manually oc'd in my bios, I'm afraid if I set it to auto it might not work at all haha....

 

[x BlueRobot]

The diagnostic tools can be burned to a DVD or maybe even a bootable USB, and then run without even starting the Windows boot process.

I'll rather identify the problem for definite, then have you spend money unnecessarily.

 

[FlyingLotus]

The diagnostic tools can be burned to a DVD or maybe even a bootable USB, and then run without even starting the Windows boot process.

I'll rather identify the problem for definite, then have you spend money unnecessarily.

There is no diagnostics test for my M4 Crucial SSD, I can run the additional tests on my SSD though I'm guessing?

 

[FlyingLotus]

Trying to do the diagnostic checks on my HDD getting no drive found error but I'll keep trying.

Is the marvell controller problem linked to my WD HDD which is not my C drive or my Crucial M4 SSD which is my C drive?

Also is the ntoskrnl.exe a problem because that came up too in my blue screen view the other day, I think it's missing or corrupted as I wasn't able to open it at the time.

 

[x BlueRobot]

ntoskrnl.exe is part of the Windows kernel, and is not the problem, it's just blamed since Windows wasn't able to find a particular driver or instruction which was actually causing the problem.

The controller will be for both hard disks, are the disks shown within the BIOS?

 

[FlyingLotus]

ntoskrnl.exe is part of the Windows kernel, and is not the problem, it's just blamed since Windows wasn't able to find a particular driver or instruction which was actually causing the problem.

The controller will be for both hard disks, are the disks shown within the BIOS?

The m4 SSD doesn't show up in the bios boot priority bit but it shows up in the boot menu.

The HDD shows up everywhere

 

[x BlueRobot]

This may give you some ideas - The BIOS does not detect or recognize the ATA / SATA hard drive

Have you checked the SSD is connected to the motherboard properly with the SATA cables?

It seems that the SSD may be the cause of the problem at the moment, does it have any return policy or warranty? I'm just checking, because if it does, then you ask for a free replacement.