Solved BSOD every day , cant take it anymore

[writhziden]

When you switch, I would recommend not using slimdrivers. Automated driver software update programs can cause conflicts and lead to crashes and performance issues. They often recommend driver updates that are designed for different hardware than is installed on the system being updated. This leads to messages in device manager that devices are not configured correctly with a yellow exclamation mark next to them.


Also, make sure to install security software:

Microsoft Security Essentials - Free Antivirus for Windows​

http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627​

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


Loading Dump File [D:\Kingston\BSODDmpFiles\kadulitis\Windows_NT6_BSOD_jcgriff2\032212-20062-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d85250
Debug session time: Thu Mar 22 05:31:52.861 2012 (UTC - 6:00)
System Uptime: 0 days 7:45:56.298
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000002, A list entry was corrupt
Arg2: 000033c3, entry in list being removed
Arg3: 0007ff9f, highest physical page number
Arg4: 00001000, reference count of entry being removed

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


BUGCHECK_STR:  0x4E_2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82cd8d82 to 82d173f4

STACK_TEXT:  
a2f58924 82cd8d82 0000004e 00000002 000033c3 nt!KeBugCheckEx+0x1e
a2f58964 82cae16e 00000000 a3310000 00050000 nt!MiUnlinkPageFromLockedList+0x51
a2f589fc 82ce7321 a3310000 00010000 00000000 nt!MmCheckCachedPageStates+0x297
a2f58a34 82ea8072 85bfdd90 00000001 a2f58aac nt!CcFetchDataForRead+0xb6
a2f58a70 82e9e108 85bfdd90 00050000 00000000 nt!CcMapAndCopyFromCache+0x70
a2f58ab0 8988d09a 85bfdd90 869b913c 00010000 nt!CcCopyRead+0x107
a2f58bd0 89785fec 85bfdd90 a46c5988 00010000 Ntfs!NtfsCopyReadA+0x1d7
a2f58c04 897861bb 00000003 00000000 869b9134 fltmgr!FltpPerformFastIoCall+0x22e
a2f58c30 89798c37 00f58c54 89798ad4 00000000 fltmgr!FltpPassThroughFastIo+0x7d
a2f58c74 82e4a5b8 85bfdd90 a2f58cb4 00010000 fltmgr!FltpFastIoRead+0x163
a2f58d08 82c7a87a 85acf970 00000000 00000000 nt!NtReadFile+0x2d5
a2f58d08 770970b4 85acf970 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
005de878 00000000 00000000 00000000 00000000 0x770970b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+51
82cd8d82 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a381

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_2_nt!MiUnlinkPageFromLockedList+51

BUCKET_ID:  0x4E_2_nt!MiUnlinkPageFromLockedList+51

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

Points to memory corruption. There also may be a hard disk error, hard disk controller error, or corrupted file system. Do you have an HDD or SSD? What motherboard do you have, or was this vendor built? It is difficult to help without knowing what machine we are helping with.

Before I can help you with this problem, I will need a little more information. Fill in your system specs in your profile using http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html as a guide.

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[kadulitis]

Ok i did use slimdriver after i installed the 64 bit just saw your post now ... crap.
i have HDD , i bought the computer as it is now. here comes a few screens
But im using slimdrivers because im not very good to find the correct drivers to use so a friend told me to use it.

 

[writhziden]

If you use slimdrivers, make sure in device manager there are no problem devices present (yellow exclamation marks). You settings look good. You still may have bad RAM; Memtest86+ does not always catch bad RAM on the first run. It could also be your graphics card memory that is bad. Run through the following hardware tests:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ a second time for seven passes, and pay close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[kadulitis]

After 3 min in furmark i got a BSOD ... thats not good right ?
All the other stuff i will run later tonight.

 

[writhziden]

What temperature did your graphics card get to during the 3 minutes? Do you remember? Also, can you upload the crash report?

 

[kadulitis]

I think the temperature was about 70-71 .

 

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\kadulitis\Windows_NT6_BSOD_jcgriff2\032212-29343-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e4d650
Debug session time: Thu Mar 22 09:23:29.808 2012 (UTC - 6:00)
System Uptime: 0 days 2:31:13.292
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffdb00034f66a, 2, 0, fffff80002cbb38f}

Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )

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: fffffdb00034f66a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002cbb38f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb7100
 fffffdb00034f66a 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiMapPageInHyperSpaceWorker+1b
fffff800`02cbb38f 458a481a        mov     r9b,byte ptr [r8+1Ah]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Steam.exe

TRAP_FRAME:  fffff88001fd5110 -- (.trap 0xfffff88001fd5110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000001100011a77
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbb38f rsp=fffff88001fd52a8 rbp=0000000000000001
 r8=fffffdb00034f650  r9=ffffffffffffffff r10=0000000000000002
r11=fffff88001fd5390 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiMapPageInHyperSpaceWorker+0x1b:
fffff800`02cbb38f 458a481a        mov     r9b,byte ptr [r8+1Ah] ds:fffffdb0`0034f66a=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c852e9 to fffff80002c85d40

STACK_TEXT:  
fffff880`01fd4fc8 fffff800`02c852e9 : 00000000`0000000a fffffdb0`0034f66a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`01fd4fd0 fffff800`02c83f60 : 00000000`00000000 00000000`00000000 0f95e9cc`5c9cff42 fffffa80`00417720 : nt!KiBugCheckDispatch+0x69
fffff880`01fd5110 fffff800`02cbb38f : fffff800`02c6d98b fffffa80`00417420 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`01fd52a8 fffff800`02c6d98b : fffffa80`00417420 00000000`00000001 00000000`00000000 00000000`00000080 : nt!MiMapPageInHyperSpaceWorker+0x1b
fffff880`01fd52b0 fffff800`02d3ec0e : 00000000`00000000 fffff880`00000001 fffffa80`00417720 fffff800`02ebad68 : nt!MiRestoreTransitionPte+0x7b
fffff880`01fd5340 fffff800`02cb1f2c : 00000000`00000000 fffff880`01fd5400 ffffffff`ffffffff 00000000`00000064 : nt!MiRemoveLowestPriorityStandbyPage+0x21e
fffff880`01fd53c0 fffff800`02cae39e : fffff980`118fe000 00000000`1192e020 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0xe50
fffff880`01fd55b0 fffff800`02cae954 : fffffa80`03271220 00000000`1192e020 fffff880`01fd56f0 fffff880`00020000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`01fd56a0 fffff880`012b6c18 : 00000000`0b720000 fffffa80`0336c500 fffff880`01fd5790 fffffa80`000a0000 : nt!CcCopyWrite+0x194
fffff880`01fd5730 fffff880`01032102 : fffffa80`0336c5c0 fffff880`010354f2 fffff880`000a0000 00000000`000a0001 : Ntfs!NtfsCopyWriteA+0x208
fffff880`01fd5930 fffff880`010358ba : fffff880`01fd5a00 fffffa80`02b663a8 00000000`118b0000 00000000`000a0000 : fltmgr!FltpPerformFastIoCall+0xf2
fffff880`01fd5990 fffff880`0105383e : 00000000`000a0000 00000000`00000000 fffffa80`0336c5c0 fffff880`01fd5b00 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`01fd59d0 fffff800`02f977be : fffffa80`0336c634 fffff880`01fd5a98 00000000`00000000 fffffa80`0336c634 : fltmgr!FltpFastIoWrite+0x1ce
fffff880`01fd5a70 fffff800`02c84fd3 : 00000000`00000901 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad
fffff880`01fd5b70 00000000`736e2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`09bff0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x736e2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiMapPageInHyperSpaceWorker+1b
fffff800`02cbb38f 458a481a        mov     r9b,byte ptr [r8+1Ah]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiMapPageInHyperSpaceWorker+1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiMapPageInHyperSpaceWorker+1b

BUCKET_ID:  X64_0xA_nt!MiMapPageInHyperSpaceWorker+1b

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

Add the following to your steps and check for data corruption:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. 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.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[kadulitis]

do u still want me to run the tests in the other post ??

 

[writhziden]

Yes, I still recommend the tests in the other post. Start with those in the most recent post, then proceed with the hardware tests again. See if running the disk check and cleaning up the hard disk corruption will allow you to finish the hardware checks.

 

[kadulitis]

I had no errors on the second disk

 

[writhziden]

What about on the Windows disk? Did you schedule a check on the Windows disk for the next time the computer restarts?

 

[kadulitis]

Yes and it was fine to .... i will now go back and run some other tests

 

[kadulitis]

|MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better

That was running for 15 passes with no error.

 

[writhziden]

Good news the graphics card RAM passed. How are things going with prime95?

 

[kadulitis]

I started to run Prime95 at 16:35 and its still running , its shows no error , stop at 19:51 no errors.

 

[kadulitis]

the Windows Memory Diagnostics Tool was running for 8 passes with no erroe

 

[writhziden]

Alright. Do you plan to run memtest86+ tonight?

 

[kadulitis]

I can do that yes

 

[kadulitis]

You write i should pay close attention to Parts 2 and 3 of the tutorial. What do u mean by that ?? i just have to start it and let it run or should i configure something in there ?

 

[writhziden]

You just let it run. No settings need to be changed. Part 2 also says to let it run for at least 7 passes; 10 or more is better if possible. Part 3 gives instructions on what to do if you get any errors during the passes.