Solved Random BSOD any help/advice welcome

[Bodsville]

Random BSOD any help/advice welcome zip file attached

 

[koolkat77]

Uninstall McAfee and replace it with Microsoft Security Essentials.

Uninstallation method: Revo Uninstaller

Use Revo Uninstaller to uninstall stubborn software.

• Download and install the software
• Opt for Advance Mode while uninstalling which allows you to remove leftover registry.
• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Download TDSSkiller and run a scan on your PC:

Download Kaspersky TDSSKiller 3.1.0.9 - FileHippo.com

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 10.0.10240.9 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\HOME-PC-15_12_2015_230500_81\121515-28546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\Visualizers.
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03a1a000 PsLoadedModuleList = 0xfffff800`03c61730
Debug session time: Wed Dec 16 03:49:28.224 2015 (UTC + 6:00)
System Uptime: 0 days 0:46:25.208
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88011a3e1c8, fffff88011a3da20, fffff80003aa85ee}

Probably caused by : ntkrnlmp.exe ( nt!SepMandatoryIntegrityCheck+2ae )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88011a3e1c8
Arg3: fffff88011a3da20
Arg4: fffff80003aa85ee

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


SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  3.0

BIOS_DATE:  01/07/2010

BASEBOARD_PRODUCT:  MSI X58 Pro-E (MS-7522)

BASEBOARD_VERSION:  3.0

BUGCHECK_P1: 1904fb

BUGCHECK_P2: fffff88011a3e1c8

BUGCHECK_P3: fffff88011a3da20

BUGCHECK_P4: fffff80003aa85ee

EXCEPTION_RECORD:  fffff88011a3e1c8 -- (.exr 0xfffff88011a3e1c8)
ExceptionAddress: fffff80003aa85ee (nt!SepMandatoryIntegrityCheck+0x00000000000002ae)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88011a3da20 -- (.cxr 0xfffff88011a3da20)
rax=ae3ad92da47e9ba5 rbx=0000000000000080 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff8a003b324f0 rdi=fffff88011a3e510
rip=fffff80003aa85ee rsp=fffff88011a3e400 rbp=0000000000000000
 r8=fffffa8005c2d600  r9=fffff8a003b324f0 r10=fffff880089c9768
r11=fffff88011a3e468 r12=fffff88011a3e780 r13=fffff8a0049c231c
r14=fffff8a003b324f0 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!SepMandatoryIntegrityCheck+0x2ae:
fffff800`03aa85ee 0fb74804        movzx   ecx,word ptr [rax+4] ds:002b:ae3ad92d`a47e9ba9=????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: c02

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 1a

CPU_STEPPING: 5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbamscheduler.

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ccb100
GetUlongPtrFromAddress: unable to read from fffff80003ccb2e0
GetUlongPtrFromAddress: unable to read from fffff80003ccb490
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!SepMandatoryIntegrityCheck+2ae
fffff800`03aa85ee 0fb74804        movzx   ecx,word ptr [rax+4]

FAULTING_IP: 
nt!SepMandatoryIntegrityCheck+2ae
fffff800`03aa85ee 0fb74804        movzx   ecx,word ptr [rax+4]

BUGCHECK_STR:  0x24

ANALYSIS_VERSION: 10.0.10240.9 x86fre

LAST_CONTROL_TRANSFER:  from fffff80003aa006b to fffff80003aa85ee

STACK_TEXT:  
fffff880`11a3e400 fffff800`03aa006b : 00000000`00000080 00000000`3b4dc85c fffff8a0`03b324f0 00000000`00000000 : nt!SepMandatoryIntegrityCheck+0x2ae
fffff880`11a3e470 fffff880`012c3dd3 : fffffa80`05490180 fffff8a0`049c231c 00000000`00000000 00000000`00000000 : nt!SeAccessCheckWithHint+0x3fb
fffff880`11a3e570 fffff880`012bf347 : fffffa80`05c2d610 00000000`00000000 fffff8a0`13899b40 00000000`00000080 : Ntfs!TxfAccessCheck+0x123
fffff880`11a3e6e0 fffff880`012acdf3 : fffffa80`0b279500 fffff880`089c9290 fffff8a0`13899b40 fffff8a0`03a40510 : Ntfs!NtfsAccessCheck+0x1b7
fffff880`11a3e8c0 fffff880`012ad1df : 00000000`00000000 fffff8a0`13899b40 00000000`00000002 fffffa80`07b38000 : Ntfs!NtfsCheckExistingFile+0xc3
fffff880`11a3e950 fffff880`012a8f5b : fffff880`089c9290 fffffa80`0b279500 fffff8a0`13899ed8 fffff8a0`00000084 : Ntfs!NtfsOpenExistingAttr+0x20f
fffff880`11a3ea10 fffff880`012ac1cf : fffffa80`0b279500 fffffa80`06841bd0 fffff8a0`13899ed8 fffff880`00000084 : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab
fffff880`11a3eba0 fffff880`012bc306 : fffffa80`0b279500 fffffa80`06841bd0 fffff8a0`13899ed8 00000000`00000701 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`11a3ec90 fffff880`012b9af3 : fffffa80`0b279500 fffffa80`06841bd0 fffff880`11a3ee70 fffff880`11a3eea8 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`11a3ed60 fffff880`012243ad : fffffa80`0b279500 fffffa80`06841bd0 fffff880`089c9290 fffffa80`09de6b00 : Ntfs!NtfsCommonCreate+0x3d3
fffff880`11a3ef30 fffff800`03a85737 : fffff880`089c9200 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`11a3ef60 fffff800`03a856f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`089c90d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!SepMandatoryIntegrityCheck+2ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c

IMAGE_VERSION:  6.1.7601.19045

STACK_COMMAND:  .cxr 0xfffff88011a3da20 ; kb

FAILURE_BUCKET_ID:  X64_0x24_nt!SepMandatoryIntegrityCheck+2ae

BUCKET_ID:  X64_0x24_nt!SepMandatoryIntegrityCheck+2ae

PRIMARY_PROBLEM_CLASS:  X64_0x24_nt!SepMandatoryIntegrityCheck+2ae

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x24_nt!sepmandatoryintegritycheck+2ae

FAILURE_ID_HASH:  {ed6e1db0-56d3-e899-d50e-149228313dde}

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

[/FONT]

 

[Bodsville]

Thanks @koolkat77 for the info/advice, I did follow your advice, all went well up until chckdsk when another BSOD happened... file attached

 

[koolkat77]

Please wait a while and see if the BSOD's occur again.

 

[Bodsville]

Thanks @koolcat77 No BSOD's for over a week now your advice seems to have worked