BSOD when running maintenance

Hi, i regularly do maintenance on my computer on saturday, but today,
i seem to have a BSOD issue plaguing me.

The .dmp is attached there. If anyone could please take a look :)

Thanks,
Alex.

Code:

BugCheck 50, {fffff8a012ff4000, 0, fffff80003283b5b, 0}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4514f )

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Code:

1: kd> .trap 0xfffff8800c64c5f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=000000001dff0c00
rdx=fffff89ff50033d6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003283b5b rsp=fffff8800c64c788 rbp=fffff8800c64cb60
 r8=000000001e420000  r9=0000000000000000 r10=0000000000000000
r11=0000000010010040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!memmove+0x14b:

Code:

1: kd> k
Child-SP          RetAddr           Call Site
fffff880`0c64c488 fffff800`03234eec nt!KeBugCheckEx
fffff880`0c64c490 fffff800`0328b0ee nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`0c64c5f0 fffff800`03283b5b nt!KiPageFault+0x16e
fffff880`0c64c788 fffff800`03554de4 nt!memmove+0x14b
fffff880`0c64c790 fffff800`035689f1 nt!CmpQueryKeyValueData+0x3ae
fffff880`0c64c820 fffff800`03568fb7 nt!CmEnumerateValueKey+0x211
fffff880`0c64c910 fffff800`0328c253 nt!NtEnumerateValueKey+0x256
fffff880`0c64ca70 00000000`775d144a nt!KiSystemServiceCopyEnd+0x13
00000000`0cece7e8 00000000`00000000 0x775d144a

Follow these steps:

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Upload a .NFO file:

Start > Type: msinfo32 > Press "Enter" > File, Save

Thanks for the fast response.

You said one of the possible causes could be faulty system service right?
Well, i generated a system health report, and it turns out it failed two tests from system service checks.
I uploaded the .NFO you asked, along with a system health report.

Thanks for the information :)

Remove:

Code:

Start Menu\Programs\Advanced SystemCare 6
Start Menu\Programs\TuneUp Utilities 2013
Start Menu\Programs\TuneUp Utilities 2013\All functions

This seems to be related to TuneUp Utilities:

Code:

Not Available	ROOT\LEGACY_TUNEUPUTILITIESDRV\0000	This device is disabled.

Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.

• Registry Cleaner Tests - Why NOT To Use One!

Scan for any missing, modified or corrupted protected Windows files with:

• SFC /SCANNOW Command - System File Checker

Remove (at least to test):

Code:

Start Menu\Programs\Bitdefender 2013

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system.

You can also view this thread for a complete free and lightweight security protection combination:

• Good and Free system security combination.

Hi,

I finally decided to fix the problem i was having with my system running IDE while it should be running AHCI.
So, what i did was prepare the system to change from IDE to AHCI, uninstall intel rapid storage manager, reboot, set system to AHCI, boot, reboot, boot, install rapid storage manager and BAM. BSOD to the face.

I uploaded the .dmp file, can someone please take a look at it ? :)

Thanks,
Alex

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800c864903, fffff88003969458, fffff88003968cb0}

Probably caused by : iaStor.sys ( iaStor+2c903 )

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

4: kd> lmvm iaStor
start             end                 module name
fffff880`0c838000 fffff880`0cbdc000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Wed May 30 21:40:40 2012 (4FC685C8)
    CheckSum:         00091790
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I suspected this would be the problem after you mentioned about the Intel Rapid Storage drivers, they seem to always cause BSODs, it's best to follow these steps:

1. Start
2. Type: Device Manager
3. Under Disk Devices, remove each driver for each device
4. Reboot

Windows should reconfigure the correct driver for each device, this includes the msahci.sys driver.

It would be best to create a System Restore point or a Backup Image, just in case something does not plan out.

• Backup Complete Computer - Create an Image Backup
• System Restore Point - Create

x BlueRobot said:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800c864903, fffff88003969458, fffff88003968cb0}

Probably caused by : iaStor.sys ( iaStor+2c903 )

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

4: kd> lmvm iaStor
start             end                 module name
fffff880`0c838000 fffff880`0cbdc000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Wed May 30 21:40:40 2012 (4FC685C8)
    CheckSum:         00091790
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I suspected this would be the problem after you mentioned about the Intel Rapid Storage drivers, they seem to always cause BSODs, it's best to follow these steps:

1. Start
2. Type: Device Manager
3. Under Disk Devices, remove each driver for each device
4. Reboot

Windows should reconfigure the correct driver for each device, this includes the msahci.sys driver.

It would be best to create a System Restore point or a Backup Image, just in case something does not plan out.

• Backup Complete Computer - Create an Image Backup
• System Restore Point - Create

Ok, so i did as you suggested and managed to install intel rapid storage manager.
But, the problem is, whenever i install rapid storage, my computer won't shut down. I mean, it will go to the shutting down screen, the display will go into standby mode, but the computer won't shut down.

I Have tried uninstalling the SATA drivers ( including marvell ), have tried installing the rapid storage driver manually through device manager, but nothing works. As long as i have Intel RST on my system, it seems my computer won't shut down properly. This reminds me of that (it's now safe to shutdown) screen that old windows used to have.

Anyone have any idea? Any suggestion would be appreciated.

Thanks,
Alex.

Layback Bear said:

Do you have your drives plugged into SATA II or SATA III. On my ASUS board I have to use SATA II or it will go crazy at times. I really cant tell and speed difference.

They're connected to the sata III plug