Random BSOD's over a month

[Lazyslacker24]

Been getting blue screens this month i have ran memtest, check disk and swapped out ram and hdd's rust to be safe and used driver versifier and still blue screens i am out of ideas

 

[koolkat77]

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

Start Menu\Programs\ASUS\AI Suite II    Public:Start Menu\Programs\ASUS\AI Suite II    Public

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

4. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor

​

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80004424598, 0, fffff800034097d0, 0}


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

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80004424598, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800034097d0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100
GetUlongFromAddress: unable to read from fffff800030c21c0
 fffff80004424598 Nonpaged pool

FAULTING_IP: 
hal!KeQueryPerformanceCounter+dc
fffff800`034097d0 8b0dc2ad0100    mov     ecx,dword ptr [hal!HalpQueryPerformanceCounterOriginalSource (fffff800`03424598)]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TAG_NOT_DEFINED_c000000f:  FFFFF88002F94FB0

TRAP_FRAME:  fffff88002f8d9a0 -- (.trap 0xfffff88002f8d9a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000965fd7500f rbx=0000000000000000 rcx=0000010381738f0a
rdx=0002587b00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034097d0 rsp=fffff88002f8db30 rbp=0000000000000000
 r8=0000000000000000  r9=00000000003a21c8 r10=000000000002ab34
r11=fffff88002f65100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
hal!KeQueryPerformanceCounter+0xdc:
fffff800`034097d0 8b0dc2ad0100    mov     ecx,dword ptr [hal!HalpQueryPerformanceCounterOriginalSource (fffff800`03424598)] ds:fffff800`03424598=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f08bf0 to fffff80002e8abc0

STACK_TEXT:  
fffff880`02f8d838 fffff800`02f08bf0 : 00000000`00000050 fffff800`04424598 00000000`00000000 fffff880`02f8d9a0 : nt!KeBugCheckEx
fffff880`02f8d840 fffff800`02e88cee : 00000000`00000000 fffff800`04424598 fffff800`02e95f00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`02f8d9a0 fffff800`034097d0 : 00000000`00000010 00000000`00000246 fffff880`02f8db58 00000000`00000018 : nt!KiPageFault+0x16e
fffff880`02f8db30 fffff800`02e93786 : 00000000`003a21c8 00000000`00000000 fffff880`02f700c0 00000000`00000001 : hal!KeQueryPerformanceCounter+0xdc
fffff880`02f8db60 fffff800`02e8289c : fffff880`02f65180 fffff880`00000000 00000000`00000000 fffff880`04455480 : nt!PoIdle+0x5a7
fffff880`02f8dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4518f
fffff800`02f08bf0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4518f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4518f

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4518f

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