Solved Random BSOD on fresh installed Desktop: (ntoskrnl.exe)

[jroot]

I have been having random BSOD since I have re-installed my Desktop (3 Weeks ago). Before that, my system has been running "perfectly" since 2 years.

- Only changes have been a second SSD and also a new HDD.
- I used the same drivers for the Motherboard again (from CD) - perhaps i should update them some time? Other Drivers should be up to date. It still may be a driver-problem, though.

I performed a full-scan with MSE and in addition downloaded Malwarebytes and did another full-scan - found nothing. SFC /scannown found nothing either. Memtest86+ ran clean, too.


I'd be very grateful, if someone could take a look at this for me.
Minidumps and other files from SF_Diagnostic_Tool should be attachet. For further questions I shall be avaliable!

Thanks in advance.

 

[Arc]

Hello jroot.

All your recent BSODs are BugCheck 4E: PFN_LIST_CORRUPT. The crash dumps are somehow silent about the probable causes, but some Ntfs, fltmgr and fileinfo errors are there. In such a situation, first you try to update your SSD's firmware.

• M4-CT128 M4SSD2: Crucial.com Product Downloads - Firmware Updates
• SAMSUNG SSD 830: Support - Solid State Drives MZ-7PC256N | Samsung Memory & Storage

Uninstall Marvel SCSI drivers. Those are poorly coded and hence problematic.

Start Menu\Programs\Marvell\91xx driver

When done. follow this guide to clean up the leftover:

• Drivers - Clean Left over Files after Uninstalling

You are overclocked.

CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
[COLOR=Red]CurrentSpeed: 3502[/COLOR]

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Moreover, the BIOS is old.

BiosVersion = 0706
BiosReleaseDate = 08/05/2011

As you are using SSDs, you need to use an updated BIOS. Get the BIOS Version 3603(Only for Win7 & Win8, dated 2012/11/27 from ASUS - P8Z68-V PRO (motherboard: ASUS P8Z68-V PRO).

Let us know the results.
__________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 133b30, 0, 134d30}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000133b30, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000134d30, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  wmplayer.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f58a0c to fffff80002ec9c00

STACK_TEXT:  
fffff880`0a6a6258 fffff800`02f58a0c : 00000000`0000004e 00000000`00000099 00000000`00133b30 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a6a6260 fffff800`02e761ef : 00000000`00000000 fffffa80`0518f0d0 0000000f`ffffffff fffff8a0`02375790 : nt!MiBadShareCount+0x4c
fffff880`0a6a62a0 fffff800`02ebe9a1 : cf200000`00000000 fffff680`00036a38 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x3273a
fffff880`0a6a6320 fffff800`02eb6162 : fffffa80`117eabc0 00000000`00000000 fffffa80`0d1d8b30 fffffa80`0d1d8ec8 : nt!MiDecommitPages+0x1a1
fffff880`0a6a6bb0 fffff800`02ec8e93 : ffffffff`ffffffff 00000000`000b90d0 00000000`000b90c8 fffffa80`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0a6a6cb0 00000000`775a14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000b9098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775a14fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f58a0c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

 

[jroot]

Hi Arc

Thank you very much for looking into this for me!
I'll follow your well described instructions ASAP.

I was aware of the old BIOS version, but my lazy opinion was not to change a running / working system.
Better use the BSOD as excuse to get things right!

As for the overclocking - I was not aware, my CPU has been overclocked. Could that just have been my CPU running in "turbo-mode"? Intel core i7 2600K - max Thurbo Frequency


Nevertheless, thanks again for the good tipps! I'll keep you posted.

Kind regards,
jroot

 

[Arc]

As a test, you may disable turbo made. For a crashing system, it is better to use the hardware at default clock settings.

I suggested the BIOS update, as it is needed to run the SSDs properly. A properly running SSD needs the combination or recent firmware, BIOS and storage controller. But if you are reluctant (I can understand your point) you may keep it on pending

 

[jroot]

Problem seems to have been resolved

After following your instructions Arc, I have now been running my system for 1 Week now, without any BSODs appearing.
Seems you have solved the problem.

Thanks again for your awesome help!

 

[Arc]

You are welcome mate
For any further issue, let us know