Getting random BSODs excessively, memory management, win32k.sys, etc

BranKeye · 02 Jun 2012

I need your help kind readers, for the past few months I've been getting a large amount of BSODs such as memory management, irql_not_less_or_equal, win32k.sys, page fault in nonpaged area, etc. I've tried to solve the problem myself through reading a million and one forum posts, but my problem is so wide ranged that I simply don't stand a chance.

In the zip folder I have attached is the contents retrieved by the SF Diagnostic Tool. I need help in resolving these BSODs, thanks for your time.

Dave76 · 03 Jun 2012

Welcome to Seven Forums.

The cause noted is memory corruption.
This can be a problem with the RAM, RAM settings, or caused by a driver.

Can you fill in your system specs?
This program will help with the info gathering.
Speccy Free System information Utility
Age of your system?
Any hardware installed recently?
Any new apps installed?

Code:

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.

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

TRAP_FRAME:  fffff8800a19b3a0 -- (.trap 0xfffff8800a19b3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0400000000000020
rdx=00000000000bb23b rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003b3138f rsp=fffff8800a19b530 rbp=fffffa80063d5a50
 r8=00000000000bb23c  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiIdentifyPfn+0x26f:
fffff800`03b3138f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a88769 to fffff80003a891c0

STACK_TEXT:  
fffff880`0a19b258 fffff800`03a88769 : 00000000`0000000a 00000000`00214780 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a19b260 fffff800`03a873e0 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`001b3d05 : nt!KiBugCheckDispatch+0x69
fffff880`0a19b3a0 fffff800`03b3138f : 00000000`00000000 02000000`000be5f4 00000000`42506600 fffff800`03d7034f : nt!KiPageFault+0x260
fffff880`0a19b530 fffff800`03b3203b : 00000000`00000000 00000000`00000004 fffffa80`0e57e4c8 fffffa80`0e57d000 : nt!MiIdentifyPfn+0x26f
fffff880`0a19b5d0 fffff800`03e96a85 : fffffa80`0e57d000 fffff880`0a19bb60 fffff880`0a19b6a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`0a19b610 fffff800`03dd9ae8 : 00000000`00000006 00000000`00000000 fffffa80`0e57d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`0a19b660 fffff800`03d8e863 : 00000000`00000000 00000000`00000000 fffff880`0a19b7e8 fffff880`0a19b701 : nt! ?? ::NNGAKEGL::`string'+0x47bfd
fffff880`0a19b6f0 fffff800`03d8f0d9 : 00000000`010fb9a8 fffff800`03a947b8 00000000`010fba00 00000000`00000001 : nt!ExpQuerySystemInformation+0x1193
fffff880`0a19baa0 fffff800`03a88453 : 00000000`01715978 fffff880`0a19bb60 00000000`0176f160 00000000`010fd1b0 : nt!NtQuerySystemInformation+0x4d
fffff880`0a19bae0 00000000`7786167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`010fb8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7786167a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+26f
fffff800`03b3138f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiIdentifyPfn+26f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f

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

Your 8GB RAM may need some adjustments.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important in order to make RAM settings adjustments.

BranKeye · 03 Jun 2012

Specs: Windows 7 64bit, i5 2500k @ 3.3GHz, 8GB Dual-Channel DDR3 1333MHz (9-9-9-34) Mushkin Silverline, ASUS Pro Rev 3.1 mobo, Zotac GTX 570, 2TB Western Digital (FAEX) HDD, ASUS Xonar DS soundcard. My system is about 2 and a half years of age, I recently switched to a new case with all the same components. New apps that were installed include Steam games, CCleaner, almost every Auslogics product, and DriverUpdate.

Idle CPU temps are 29, 37, 28, 35 degrees Celsius for each core.
Full load temps are 47, 53, 51, 50 degress Celsius for each core.

I'll get the BIOS CPU, RAM, and CPU integreated memory controller voltages after this post.

BranKeye · 03 Jun 2012

The CPU voltage is about 1.120V and the RAM voltage is about 1.518V.
Now, I think the VCCIO voltage on my mobo is the integrated memory controller voltage, so the VCCIO voltage reads 1.065V. There's a second voltage on my mobo titled VCCSA, so in case I'm incorrect and this is actually the correct voltage, this one reads 0.925V.

My computer crashed again today with an irql_not_less_or_equal BSOD. BSODs occur daily, but aren't limited to just that one.

Dave76 · 04 Jun 2012

The CPU voltage is good.

Bump the RAM voltage to 1.550v.
The VCCIO Voltage is the IMC (integrated memory controller) voltage, bump this to 1.150v.

Change the RAM 'Command Rate' to 2T, in 'DRAM Timing Control'.

Save and Exit the BIOS.

Let us know if you get any more crashes.
The settings may need a little more adjusting.

BranKeye · 04 Jun 2012

Alright, I changed all the settings successfully. Had trouble finding the Command Rate, but it turned out be called DRAM Command Mode, their similar enough I suppose. If any other BSOD occurs, which is normally daily, I'll be sure to post back with a minidump. If nothing else occurs within the next few days, I'll be sure to post back and let you all know. Thanks a lot!

Dave76 · 04 Jun 2012

Hope it is more stable for you, let us know your status.

BranKeye · 05 Jun 2012

During light web browsing with google chrome, I got another BSOD. This time, it was one I've never had before. IRQL_GT_ZERO_AT_SYSTEM_SERVICE with the stop code 0x0000004A.

I have the sptd driver that's installed by Daemon Tools, and I've tried to get rid of it before because it may be the problem, but it will not uninstall.

Attached is the minidump of the crash.

Dave76 · 05 Jun 2012

Be sure to always (unless requested not to) include the full BSoD report files, there is a lot of useful information in those files.
If the dmp file had evrything needed it would be a simple one click to fix everything, sadly this is not the case.

Can you enter your system specs in the 'My System Specs' dropbox in the lower left corner of any of your posts?
This will help anyone that is trying to help you, they won't have to search through the thread looking for information.

Code:

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

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 000000007786138a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff8800726db60, 0

Usual causes:  Device driver
This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
PROCESS_NAME:  vsserv.exe
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80003a86769 to fffff80003a871c0
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_vsserv.exe_nt!KiSystemServiceExit+245

What Anti-Virus are you using?
The vsserv.exe, is normally used by BitDefender and some other AVs. This can be caused by AV conflicts.
Have had other AVs installed previusly?
Where they completely removed by specific program removal apps?
Are you using any Acronis products?

BranKeye · 05 Jun 2012

Ok, I filled out my system specs. I've also included absolutely everything that the SF Diagnostic Tool could grab, if you need anything else just let me know. Again, thanks for the help.