Mem_mang, Bad_pool_header, pfn_list etc BSODs

[ovaisaijaz]

Guys please help me, i am recieving several BSODs from the very first day i assembled this PC and installed win7. All my hardware is 4 months old now.

More often i recieve Memory_managment BSOD, in july i started my research on this and got to this forum. So, i collected my dmp files for the month of july and now reporting to you guys. I tried to comprehend these dmp files using WINDBG but i am unable to comprehend them or to pinpoint the problem.

Please help me on this issue......

I am new to this forum please let me know what more information is needed, I have read the method and followed it but still plz correct me if there are still errors.

 

[Wishmaster]

I beleive this is a hardware error. Might possibly be a bad RAM module.

Have you tried checking the Pc with only 1 of the RAM sticks installed?

This is fairly easy to check. If I were you I would try to rule it out, until someone is able to analze your dump file:

Pull one stick of RAM out, and test with just 1 module and see how it goes. Then, pull it and replace with other one. Test again.

i understand the hardware is only a few months old, but it doesnt rule out the possibility you were sent a bad part. It can and does happen occasionally, unfortunatly.

Also, double check that timings, speed and especially voltage aere set correctly in the bios.

 

[ovaisaijaz]

I have checked the ram with windows diagnostic utility results are fine. also can explain a bit moree about these timings, speed etc....

 

[Thorsen]

The timings for ram can be manually adjusted to change the way the system uses the ram. in the BIOS, you can set it to Auto to make the RAM run at default settings.

The best test even if the Diagnostics didn't show anything is to run it with each individual sticks and see if any issues are seen. You could have a bad stick and it is only showing errors during normal use.


For tech info:
Timing has to do with clock cycles between accessing the info on RAM. Tight timing is low numbers like 5-5-5-15. (or 4-4-4-18) It is a little complex, but generally, lower numbers = better performance.
Memory timings - Wikipedia, the free encyclopedia

 

[Thorsen]

A good tool for finding this info is CPU-Z CPUID - System & hardware benchmark, monitoring, reporting


If you are not overclocking your system or have never changed any settings in the BIOS you should be fine.

 

[ovaisaijaz]

If I feed exactly the same setting as i find on the corsair website for my model, will it do the job. Also should i check the sticks individually with memtest as well, or windows tool is ok?

I have attached my current CPU-ID Profile. Accordinf to corsair site my model data is:
TW3X4G1600C9D
Speed Rating
PC3-12800
Tested Speed
1600Mhz
Size
4GB Kit (2 x 2GB)
Tested Latency
9-9-9-24
Tested Voltage
1.8
Performance Profile
XMP
SPD Speed
1333Mhz
SPD Latency
9-9-9-24
Package
240pin DIMM

Alaso attached todays two minidumps, one memory_management ant other PFN_LIST_CORRUPT.

 

[Thorsen]

Memtest wouldn't hurt. It might catch something Windows missed. I think the suggested process is to run memtest for a few passes as well.

It is also important to check them individually. If you can run just one stick for a while, use it as normal daily use to see if you get the same issues.

It might also not be the RAM itself. the RAM slots can have issues as well. There is a lot going on between all these system parts. try the one stick at a time in each slot

Ex:

Try Stick 1 in Slot A
Try Stick 1 in Slot B
Try Stick 2 in Slot A
Try Stick 2 in Slot B

 

[Capt.Jack Sparrow]

Hello ! Welcome to SF !

Most of them a pointing to Memory Management there are lot of crashes with Svchost.exe with SysMain possibly caused by McAfee. I would recommend to uninstall McAfee completely and use Removal Tool How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

I would recommend http://www.microsoft.com/security_essentials/

Uninstall the LogMeIn and you could reinstall it later seems like one of the LogMeIn driver has cause some trouble to the System.

LogMeIn Kernel Information Provider

Run Hardware Diagnostic: Hardware Diagnostic !! « Captain Debugger

Bugcheck:

[FONT=Book Antiqua][COLOR=Navy]Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 11:03:22.745 2010 (GMT+6)
System Uptime: 0 days 0:04:42.181
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 16:58:22.497 2010 (GMT+5)
System Uptime: 0 days 0:01:29.559
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 02:29:21.126 2010 (GMT+6)
System Uptime: 0 days 1:09:05.562
Loading Kernel Symbols
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 19:30:40.697 2010 (GMT+5)
System Uptime: 0 days 1:05:18.133
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  EFLC.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 19:27:01.841 2010 (GMT+6)
System Uptime: 0 days 2:24:04.277
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  dwm.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 02:13:40.885 2010 (GMT+6)
System Uptime: 0 days 0:08:14.321
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  WerFault.exe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 02:36:34.952 2010 (GMT+5)
System Uptime: 0 days 0:22:02.013
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  mcshield.exe[/COLOR][/FONT]

Hope this helps,
Captain

 

[ovaisaijaz]

plz refer to previous post, some more data from my side

 

[ovaisaijaz]

Thanks alot Captian Jack. I worked as u advices its almost 12hrs and i dnt have a BSOD yet. Hope it will do the trick.

Thanks again.

 

[Thorsen]

good to hear ovai. Hopefully your BSOD days are over.

 

[ovaisaijaz]

It was really perfect till now, as i just terminated GTA EFLC and went for shutdown i got IRQL_NOT_LESS_OR_EQUAL.

I have attached the minidump plz give me assistance on it. I also opened it on WinDbg, but no info i can get like Captian you gave in your reply.

Please help me out again guys.

 

[ovaisaijaz]

WinDBG,

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffff00000000, 2, 1, fffff800030a3188}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+38 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffff00000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030a3188, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c40e0
ffffffff00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeReleaseSemaphore+38
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880080621b0 -- (.trap 0xfffff880080621b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffffff00000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a3188 rsp=fffff88008062340 rbp=fffffa80055f4b60
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeReleaseSemaphore+0x38:
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7 ds:ffffffff`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000308bb69 to fffff8000308c600
STACK_TEXT:
fffff880`08062068 fffff800`0308bb69 : 00000000`0000000a ffffffff`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08062070 fffff800`0308a7e0 : fffff980`19abbc00 ffffffff`00000000 fffffa80`04a05180 00000000`0191bfc9 : nt!KiBugCheckDispatch+0x69
fffff880`080621b0 fffff800`030a3188 : fffffa80`03d594a0 fffff800`030e9cbb 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`08062340 fffff800`030967b3 : fffffa80`03d594a0 fffffa80`00000000 fffff980`19abbdc0 fffff980`19abbc00 : nt!KeReleaseSemaphore+0x38
fffff880`080623c0 fffff880`0123342c : fffffa80`039f63a0 00000000`00000702 fffff8a0`09de44d0 00000000`00000000 : nt!ExpReleaseResourceForThreadLite+0x31e
fffff880`08062420 fffff880`01298bd6 : 00000000`00000000 00000000`00000001 fffffa80`039f63a0 fffffa80`039f63a0 : Ntfs!NtfsReleaseFcb+0x2c
fffff880`08062460 fffff880`012e9bbd : fffffa80`039f63a0 fffffa80`04a05180 00000000`00100001 00000000`00000000 : Ntfs!NtfsFlushVolume+0x4b6
fffff880`08062590 fffff880`012ea5f0 : fffffa80`039f63a0 fffffa80`062a4c10 fffffa80`05dc6f20 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`08062670 fffff880`0104a23f : fffffa80`062a4fb0 fffffa80`062a4c10 fffffa80`039f63a0 fffff880`08062698 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`080626e0 fffff880`010486df : fffffa80`04a00830 00000000`00000000 fffffa80`04a00800 fffffa80`062a4c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08062770 fffff800`033a3c49 : 00000000`00000002 fffffa80`05dc6f20 00000000`00000000 fffffa80`062a4c10 : fltmgr!FltpDispatch+0xcf
fffff880`080627d0 fffff800`033301c1 : fffffa80`062a4c10 fffffa80`055f4b60 fffffa80`05dc6f20 fffff880`02fd3180 : nt!IopSynchronousServiceTail+0xf9
fffff880`08062840 fffff800`0308b853 : fffffa80`055f4b60 fffffa80`036ee890 fffffa80`04a00830 fffffa80`05dc6f20 : nt!NtFlushBuffersFile+0x171
fffff880`080628d0 fffff800`03087df0 : fffff800`032d281d 00000000`00000004 fffffa80`04669b90 fffffa80`060950f0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`08062a68 fffff800`032d281d : 00000000`00000004 fffffa80`04669b90 fffffa80`060950f0 fffffa80`0370e040 : nt!KiServiceLinkage
fffff880`08062a70 fffff800`03331a86 : 00000000`00000000 fffffa80`055f4b60 00000000`00000080 00000000`00000001 : nt!PopFlushVolumeWorker+0x1bd
fffff880`08062d40 fffff800`0306ab06 : fffff880`02fd3180 fffffa80`055f4b60 fffff880`02fddfc0 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a
fffff880`08062d80 00000000`00000000 : fffff880`08063000 fffff880`0805d000 fffff880`080620a0 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeReleaseSemaphore+38
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeReleaseSemaphore+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+38
BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+38
Followup: MachineOwner
---------

 

[Thorsen]

Capt'n Jack is offline right now, but I posted for more help for you. Hopefully a BSOD expert will show up soon.

 

[ovaisaijaz]

Capt'n Jack is offline right now, but I posted for more help for you. Hopefully a BSOD expert will show up soon.

Thanks alot buddy.

 

[Capt.Jack Sparrow]

Hello,

Sorry due to heavy fever i was in hospital that's why I couldn't replay. OK so back to your issue. Lets run some Hardware Diagnostic Hardware Diagnostic !! « Captain Debugger also run Prime95 Test

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Good Luck,
Captain

 

[ovaisaijaz]

Thanks alot Bro, I will go as u have guided.
pray for you to be wall al the times