Hi Dave76,
I'd run the memtest86+ appropriately, 1 stick at a time. I didint found any errors.
I didnt get it about the :snipping tool' you were talking about, so here my cpu-z ss :
Attachment 190218Attachment 190219Attachment 190220
Attachment 190221Attachment 190222
Here's also my last BSOD report:Attachment 190217
Sorry man i'm not so familiar with BIOS, perhaps u could tell me where is it exactly?
Your CPUZ information looks good.
To enter your BIOS press the 'Delete' key repeatedly when you first start the computer.
Go to the 'Cell Menu' section, towards the bottom of the page you will see:
CPU Voltage
CPU-NB Voltage
DRAM Voltage
They will say auto, select it and change to 'Manual' to see what the actual voltage readings are, let us know the voltages for the three listed above.
Alright then, Here you go:
CPU Voltage:
Auto : 1.401 V
Min : 1.049 V
Max : 2.049 V
CPU-NB Voltage:
Auto : 1.112 V
Min : 0.041 V
Max : 1.656 V
D-RAM Voltage :
Auto : 1.504 V
Min : 0.843 V
Max : 2.575 V
Actually I couldnt change the menu into manual but its written on the right panel so i just wrote it down, hope its works
No errors when testing the RAM cards separately indicates a possible voltage bump is required.
Just select where it says 'Auto', that will give you the options.
Download your motherboard manual: MSI 870A-G54
Read pages 3-3, 3-18.
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Bump your DRAM voltage to 1.550v and your CPU-NB voltage to 1.150v.
Test for stability by re-creating the crash scenario or run your most resource intensive game.
Let us know the results.
I'm using prime 59 to test the CPU, for its max temps, and here it is:
Attachment 190576
I have changed the voltage also acccording to your order: DRAM V=1.550V( its more like 1.567 or such, cause I cant get an exact 1.550V) & CPU-NB: 1.150V (Turn RED).
I played ModernWarfare 3, no error occured, played Trine2 no error occured.
Your CPU temps look good.
How long did you run Prime95?
Let us know if you get any more crashes.
I ran all three test for around 3hours or more.
This BSOD only occured when I turn on my PC. And then it was like 5 or more BSOD everytime after restart, so I have to turn the PC off first, and turn it on again to stop the BSOD keep coming.
This is my last BSOD report (just about 15minutes ago) : Attachment 190650
Last edited by dragontiger; 30 Dec 2011 at 11:12.
Three hours is good enough for CPU temp testing.
We have some crash info to work with, you can turn off the driver verifier now.
Which RAM do you have installed now?
Have you update your motherboard drivers?
If not go to the motherboard website and update all drivers.
The last two crashes:
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Cause: This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8000379be30, Address of the instruction which caused the bugcheck Arg3: fffff88008332ec0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!MiMapViewOfImageSection+3c0 fffff800`0379be30 80783200 cmp byte ptr [rax+32h],0 CONTEXT: fffff88008332ec0 -- (.cxr 0xfffff88008332ec0) rax=fff7f8a0027a9518 rbx=0000000000098000 rcx=fffff88008333b50 rdx=00000000000001c2 rsi=fffffa8006d4f010 rdi=fffffa8006e9a380 rip=fffff8000379be30 rsp=fffff880083338a0 rbp=fffffa8006e9a598 r8=00000000000001b9 r9=00000000ffffffff r10=fffffa8005a2be10 r11=fffffa8006e9a7c8 r12=fffff88008333b58 r13=fffff88008333b50 r14=0000000000000000 r15=fffffa8006d4f010 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!MiMapViewOfImageSection+0x3c0: fffff800`0379be30 80783200 cmp byte ptr [rax+32h],0 ds:002b:fff7f8a0`027a954a=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x3B PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000379be30 STACK_TEXT: fffff880`083338a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiMapViewOfImageSection+0x3c0 FOLLOWUP_IP: nt!MiMapViewOfImageSection+3c0 fffff800`0379be30 80783200 cmp byte ptr [rax+32h],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiMapViewOfImageSection+3c0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff88008332ec0 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!MiMapViewOfImageSection+3c0 BUCKET_ID: X64_0x3B_VRF_nt!MiMapViewOfImageSection+3c0 Followup: MachineOwner ---------
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Cause:
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Code:******************************************************************************* * * * 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: fffff8800339a558 Arg3: fffff88003399db0 Arg4: fffff88000d73626 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800339a558 -- (.exr 0xfffff8800339a558) ExceptionAddress: fffff88000d73626 (fltmgr!TreeUnlinkNoBalance+0x0000000000000006) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88003399db0 -- (.cxr 0xfffff88003399db0) rax=fffffa80039ccb60 rbx=fff7f8a00155c6b8 rcx=fff7f8a00155c6b8 rdx=ffffffffffffffff rsi=fffffa8006d51240 rdi=0000000000000000 rip=fffff88000d73626 rsp=fffff8800339a790 rbp=fffffa8006d51248 r8=ffffffffffffffff r9=ffffffffffffffff r10=fffff8a003009660 r11=0000000000000398 r12=ffffffffffffffff r13=fffffa8005590e58 r14=0000000000008000 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 fltmgr!TreeUnlinkNoBalance+0x6: fffff880`00d73626 488b5118 mov rdx,qword ptr [rcx+18h] ds:002b:fff7f8a0`0155c6d0=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003710100 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsDeleteScb+108 fffff880`0128fbac 488b03 mov rax,qword ptr [rbx] FAULTING_IP: fltmgr!TreeUnlinkNoBalance+6 fffff880`00d73626 488b5118 mov rdx,qword ptr [rcx+18h] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff88000d712c8 to fffff88000d73626 STACK_TEXT: fffff880`0339a790 fffff880`00d712c8 : 00000000`00000703 fffff8a0`03009600 fffff8a0`73634946 fffff8a0`03009630 : fltmgr!TreeUnlinkNoBalance+0x6 fffff880`0339a7c0 fffff880`00d8f2af : fffffa80`06d51218 fffff880`00d8f178 fffff8a0`030095b8 fffff880`00d6c000 : fltmgr!TreeUnlinkMulti+0x148 fffff880`0339a810 fffff880`00d91341 : fffffa80`06d511d0 fffffa80`05590800 00000000`00000130 fffff8a0`0300b140 : fltmgr!DeleteNameCacheNodes+0x9f fffff880`0339a850 fffff880`00d913fb : fffffa80`05590800 00000000`00000000 fffffa80`05590800 00000000`000007ff : fltmgr!CleanupStreamListCtrl+0x51 fffff880`0339a890 fffff800`0379690e : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`0300ae01 : fltmgr!DeleteStreamListCtrlCallback+0x6b fffff880`0339a8c0 fffff880`0128fbac : fffff8a0`0300b140 fffffa80`039ccb60 fffff880`0339a998 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2 fffff880`0339a910 fffff880`01294cc1 : 00000000`00000000 00000000`00000000 fffff800`0367e200 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108 fffff880`0339a950 fffff880`0120d85c : fffff8a0`0300b040 fffff8a0`0300b140 fffff800`0367e200 fffff8a0`0300aac0 : Ntfs!NtfsRemoveScb+0x61 fffff880`0339a990 fffff880`0120ca3f : fffff8a0`0300b010 fffff800`0367e260 fffff880`0339ab01 fffffa80`05f8a010 : Ntfs!NtfsPrepareFcbForRemoval+0x50 fffff880`0339a9c0 fffff880`0129263c : fffffa80`05f8a010 fffffa80`0560a180 fffff8a0`0300aa90 fffff8a0`0300aed0 : Ntfs!NtfsTeardownFromLcb+0x2af fffff880`0339aa50 fffff880`012140e2 : fffffa80`05f8a010 fffffa80`05f8a010 fffff8a0`0300aa90 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc fffff880`0339aad0 fffff880`012a2193 : fffffa80`05f8a010 fffff800`0367e260 fffff8a0`0300aa90 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2 fffff880`0339ab10 fffff880`01291357 : fffffa80`05f8a010 fffff8a0`0300abc0 fffff8a0`0300aa90 fffffa80`0560a180 : Ntfs!NtfsCommonClose+0x353 fffff880`0339abe0 fffff800`034e8001 : 00000000`00000000 fffff800`0367e200 fffffa80`039ccb01 fffffa80`00000003 : Ntfs!NtfsFspClose+0x15f fffff880`0339acb0 fffff800`03778fee : 00000000`00000000 fffffa80`039ccb60 00000000`00000080 fffffa80`039b3840 : nt!ExpWorkerThread+0x111 fffff880`0339ad40 fffff800`034cf5e6 : fffff880`03164180 fffffa80`039ccb60 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0339ad80 00000000`00000000 : fffff880`0339b000 fffff880`03395000 fffff880`0339a9e0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: Ntfs!NtfsDeleteScb+108 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b STACK_COMMAND: .cxr 0xfffff88003399db0 ; kb FAILURE_BUCKET_ID: X64_0x24_VRF_Ntfs!NtfsDeleteScb+108 BUCKET_ID: X64_0x24_VRF_Ntfs!NtfsDeleteScb+108 Followup: MachineOwner ---------
Hi Dave,
Happy New Year there man, Sorry for late Reply, having a newyear party last few days..
Alright, I turn off the verifier already.
I'm using the same RAM, since the first post of this thread, i'm using dimm slot 1&2 now.
I haven't do a lot update for mobo drivers, now i'm donwloading the audio drivers only.
Do you have any idea about why the BSOD only occur when i do startup?
Since the last bsdo occured, i haven't turn off my pc, cause when I startup my PC bsod will showup continously, until several times, or until I turn off my PC and turn it on again.
I'm afraid there's something wrong with my PC component, might be mobo, hdd, or even PSU.
What is the bugcheck (STOP error) on the BSOD during startup?
Any driver listed?
It sounds like Driver Verifier may be flagging a driver..?
Quote