Several BSOD while using Windows 7 64-bit

[brunoredline]

Hello!

During the last week I have had several bsod's while using windows 7.

I searched the forums I already updated all the drivers, applied windows updates, uninstall security protection, tried the sfc / scannow command, the chkdsr /r but no luck.
Every now and then I get a BSOD.

I tried everything and still can't fix this problem.


The bugchecks are:
IRQL_NOT_LESS_OR_EQUAL (0x0000000a)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x1000007e)
MEMORY_MANAGEMENT (0x0000001a)
SYSTEM_SERVICE_EXCEPTION (0x0000003b)
NTFS_FILE_SYSTEM (0x00000024)

 

[koolkat77]

Temp Monitoring

Check for heating issues using Speccy or HWMonitor.

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Upload a screen shot with either of the tools: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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


Loading Dump File [C:\Users\KOOLKAT\Downloads\Compressed\SARA-PC-21-04-2015_153208,11\042115-46176-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a3890
Debug session time: Tue Apr 21 18:26:03.243 2015 (UTC + 6:00)
System Uptime: 0 days 4:49:01.022
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 1A, {31, fffffa80040028f0, fffff88004416000, fffff8a0149cc50e}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7171 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa80040028f0
Arg3: fffff88004416000
Arg4: fffff8a0149cc50e

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


BUGCHECK_STR:  0x1a_31

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000332fe55 to fffff800030d0a40

STACK_TEXT:  
fffff880`080f1078 fffff800`0332fe55 : 00000000`0000001a 00000000`00000031 fffffa80`040028f0 fffff880`04416000 : nt!KeBugCheckEx
fffff880`080f1080 fffff800`033a7297 : fffff800`00000000 00000000`00000000 00000000`00000059 fffff8a0`149c8000 : nt! ?? ::NNGAKEGL::`string'+0x7171
fffff880`080f10e0 fffff800`030b25d2 : fffffa80`03273c60 00000000`00058400 fffffa80`0194b830 fffff8a0`14778310 : nt!MiRelocateImagePfn+0xf7
fffff880`080f1140 fffff800`033ab3d9 : fffffa80`0437c010 fffff6fc`4001fcc0 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x362
fffff880`080f11f0 fffff800`033ab518 : ffffffff`ffffffff 00000000`00000001 fffff8a0`149c8000 00000000`00000069 : nt!MiSwitchBaseAddress+0x61
fffff880`080f1220 fffff800`033cd10f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`080f1270 fffff800`033aac5e : fffff880`080f14c0 fffff8a0`17c2ebd0 fffff880`080f1568 fffff880`080f14b8 : nt!MmCreateSection+0x2df
fffff880`080f1470 fffff800`03534da5 : fffff8a0`16648308 00000000`00000000 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x171
fffff880`080f14f0 fffff800`03535157 : 00000000`00000010 fffff8a0`15c70c10 fffff880`080f1680 00000000`0000002c : nt!PfSnGetSectionObject+0x2d5
fffff880`080f15e0 fffff800`03535587 : fffff880`080f1700 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x247
fffff880`080f16d0 fffff800`035359af : 00000001`ca7612d8 fffffa80`044004d0 fffff8a0`17c2e000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187
fffff880`080f1940 fffff800`03436a3f : 00000000`00000000 00000000`a033f7a0 fffffa80`0643bbb0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`080f1a10 fffff800`033be5dc : fffffa80`0498cb50 fffffa80`0643bbb0 00000000`14050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x4b730
fffff880`080f1a40 fffff800`030c2555 : fffff800`03250e80 00000000`00000000 fffff800`033be494 fffffa80`0498cb50 : nt!PspUserThreadStartup+0x148
fffff880`080f1aa0 fffff800`030c24d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`080f1be0 00000000`772bb870 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`001cfcf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772bb870


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+7171
fffff800`0332fe55 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+7171

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5507a73c

IMAGE_VERSION:  6.1.7601.18798

FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7171

BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+7171

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_31_nt!_??_::nngakegl::_string_+7171

FAILURE_ID_HASH:  {24b8ace0-b14a-5ac9-7ef7-9e04460e37c9}

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

Memtest should be done overnight.

 

[brunoredline]

Attached is the screenshot of the speccy. Every temperature was green.

As for the memtest, I only had time to do the test with both sticks on and it stated several errors after 2 passes:

Total: 47116 errors
Error confidence value: 177
Lowest error address: 0002fe68000 - 766.4 MB
Highest error address: 0007fefefffc - 2046.9 MB
Bits in error mask: ff00ffff
Bits in error Total: 24 Min: 1 Max: 19 Avg: 4
Max contiguous errors: 256

Test 5: 3552 errors
Test 8: 43564 errors

I will test the individual sticks now.

 

[essenbe]

Hello brunoredline, did you download the test from Memtest86+ - Advanced Memory Diagnostic Tool? As Koolkat has explained, you are trying to determine if you have bad Ram sticks or bad Dimm Slots. Keep track and run each stick, one at a time, in each Dimm Slot. That way we can determine which is the problem. If you have any problems, please let us know and one of us will help you.

 

[brunoredline]

Hi essenbe.

No, I downloaded from MemTest86 - Offical Site of the x86 Memory Testing Tool.

Which one should I use?

 

[essenbe]

Memtest86+ is the best one. Please don't ask why they have names so much alike. I would not run the same test you ran over again, but I would use memtest86+ for the tests you have yet to run.