BSODs at random intervals, multiple error codes

[jjup]

Hi everyone, I'm new to this forum and would appreciate some help on some BSOD problems I have been having. The BSODs seem to happen at random ranging from when I'm browsing the web or just simply having a pdf file open and the error codes for each BSOD have been varied. I can't pinpoint exactly what I changed that triggered the first BSOD but I can't remember doing anything drastic to my system. I have been searching for solutions online and currently I've updated my graphics and network drivers and run a disk check but none of these seem to have helped. I heard that running memtest might be useful but I thought I should consult with you guys first.

Thanks in advance!

View attachment 301049

 

[koolkat77]

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\jjup\SF_09-01-2014\010914-13650-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e4f6d0
Debug session time: Fri Jan 10 04:36:20.014 2014 (UTC + 6:00)
System Uptime: 0 days 0:49:12.574
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 15537, 925d0003aa6e}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45f7d )

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000015537
Arg4: 0000925d0003aa6e

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c1b6fc to fffff80002c81bc0

STACK_TEXT:  
fffff880`07ed5ab8 fffff800`02c1b6fc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00015537 : nt!KeBugCheckEx
fffff880`07ed5ac0 fffff800`02c7fcee : 00000000`00000001 00000000`2f324000 00000000`0021de01 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x45f7d
fffff880`07ed5c20 00000000`748a0abb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0044f450 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748a0abb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45f7d
fffff800`02c1b6fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45f7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+45f7d

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+45f7d

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[jjup]

I ran memtest for 8 passes overnight and got no errors. I got another BSOD just now related to NTFS_FILE_SYSTEM which is the third one of this kind. I will post the new dump file below. I'm really not sure where to go from here so any help would be greatly appreciated.

View attachment 301179

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

[COLOR="Red"][B]BugCheck 24[/B][/COLOR], {1904fb, fffff8800317e718, fffff8800317df70, fffff8000318eae9}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlTeardownPerStreamContexts+69 )

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

Suggests disk errors possibly.

Try this:
1. Click Start

2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type chkdsk /R and hit enter.

You will be prompted whether you wish to schedule a chkdsk scan at next startup, type 'Y' and hit enter. Now restart your computer and chkdsk will automatically run. Report on findings.