BSOD @ Enterprise Server (used as home workstation)

#1
Good evening, in an attemp to be brief: I've been using this build for several months without any issues, but suddenly a week or so ago I start having seemingly random BSODs. I believe I've narrowed down the problem to these suspects: AIMP3 (music player, causes some graphical glitches if set to be "always on top" and another app goes fullscreen, althought I've used it for *a while* without any real problems), TeamSpeak (voice chatting program, recetly installed), Ragnarok (an "old" game, recently installed, tried several compatibility modes just in case but with no effect), KeyMaestro (keyboard driver and utility, an older version was responsible for BSODs on Windows 7, but I've been using this one for month without issues), Firefox Aurora (alpha version, updated constanly), CCleaner (foolishly used it's "registry cleaner" capabilities, already undone changes and awaiting to see effect) and Windows Search (recently installed, haven't tried disabling it yet). But finding wich one is the real culprit is proving to be a troublesome task, hence I turn to you, hoping you may help me solve this irksome situation.

I attach more than enough information about the system, you can have a quick look at this CPU-Z Screenshot or this Speccy generated report: http://speccy.piriform.com/results/WaFyPAniYnvfPsgX6gcFNPw
 


Attachments

Last edited:

kaos

Senior Member
#2
MINIDUMP
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80048e8084, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88002a2e224, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001eb4100
 fffffa80048e8084 
FAULTING_IP: 
Maestro2+1224
fffff880`02a2e224 410fb74704      movzx   eax,word ptr [r15+4]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  0
DEVICE_OBJECT: fffffa80033784d0
TRAP_FRAME:  fffff8800a1fbf80 -- (.trap 0xfffff8800a1fbf80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000240 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002a2e224 rsp=fffff8800a1fc110 rbp=0000000000000000
 r8=fffffa8001f6b770  r9=0000000000000004 r10=0000000000000000
r11=00000000ffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Maestro2+0x1224:
fffff880`02a2e224 410fb74704      movzx   eax,word ptr [r15+4] ds:a000:00000000`00000004=????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80001c30a0c to fffff80001c84d00
STACK_TEXT:  
fffff880`0a1fbe18 fffff800`01c30a0c : 00000000`00000050 fffffa80`048e8084 00000000`00000000 fffff880`0a1fbf80 : nt!KeBugCheckEx
fffff880`0a1fbe20 fffff800`01c82e2e : 00000000`00000000 fffffa80`048e8084 00000000`00000000 fffffa80`048e7e40 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`0a1fbf80 fffff880`02a2e224 : 00000000`00000001 fffff800`01c8abcc ffffffff`ffb3b4c0 fffff880`02a225cf : nt!KiPageFault+0x16e
fffff880`0a1fc110 00000000`00000001 : fffff800`01c8abcc ffffffff`ffb3b4c0 fffff880`02a225cf fffffa80`048e7e40 : Maestro2+0x1224
fffff880`0a1fc118 fffff800`01c8abcc : ffffffff`ffb3b4c0 fffff880`02a225cf fffffa80`048e7e40 fffff880`02a225cf : 0x1
fffff880`0a1fc120 fffffa80`04bfd3e0 : 00000000`00000028 00000000`00000004 00000000`00000026 fffff880`02a1f0a0 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`0a1fc190 00000000`00000028 : 00000000`00000004 00000000`00000026 fffff880`02a1f0a0 fffff900`c01c0027 : 0xfffffa80`04bfd3e0
fffff880`0a1fc198 00000000`00000004 : 00000000`00000026 fffff880`02a1f0a0 fffff900`c01c0027 fffff880`0a1fc218 : 0x28
fffff880`0a1fc1a0 00000000`00000026 : fffff880`02a1f0a0 fffff900`c01c0027 fffff880`0a1fc218 00000000`00000028 : 0x4
fffff880`0a1fc1a8 fffff880`02a1f0a0 : fffff900`c01c0027 fffff880`0a1fc218 00000000`00000028 fffff880`0a1fc218 : 0x26
fffff880`0a1fc1b0 fffff880`02a2067e : 00000000`00000048 00000000`00000048 ffffffff`fd050f80 fffff900`c01c9010 : kbdclass!WPP_RECORDER_SF_+0x98
fffff880`0a1fc1f0 fffff880`02a207e3 : fffffa80`04bfd3e0 fffffa80`04bfd300 00000000`00000103 00000000`00000000 : kbdclass!KeyboardClassReadCopyData+0x236
fffff880`0a1fc260 fffff880`02a208f5 : 00000000`00000103 fffffa80`033784d0 fffffa80`01f6ce30 fffffa80`01f6ce30 : kbdclass!KeyboardClassHandleRead+0x137
fffff880`0a1fc2b0 fffff880`02a2e742 : fffffa80`01f71f80 fffffa80`04bfd3e0 fffffa80`01f71e30 fffffa80`01f71e30 : kbdclass!KeyboardClassRead+0xf1
fffff880`0a1fc2f0 fffffa80`01f71f80 : fffffa80`04bfd3e0 fffffa80`01f71e30 fffffa80`01f71e30 fffffa80`04bfd3e0 : Maestro2+0x1742
fffff880`0a1fc2f8 fffffa80`04bfd3e0 : fffffa80`01f71e30 fffffa80`01f71e30 fffffa80`04bfd3e0 fffff800`01f8c8ab : 0xfffffa80`01f71f80
fffff880`0a1fc300 fffffa80`01f71e30 : fffffa80`01f71e30 fffffa80`04bfd3e0 fffff800`01f8c8ab 00000000`00000000 : 0xfffffa80`04bfd3e0
fffff880`0a1fc308 fffffa80`01f71e30 : fffffa80`04bfd3e0 fffff800`01f8c8ab 00000000`00000000 00000000`00000000 : 0xfffffa80`01f71e30
fffff880`0a1fc310 fffffa80`04bfd3e0 : fffff800`01f8c8ab 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`01f71e30
fffff880`0a1fc318 fffff800`01f8c8ab : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04bfd3e0 : 0xfffffa80`04bfd3e0
fffff880`0a1fc320 fffff800`01f6e223 : fffffa80`033784d0 00000000`00000000 fffffa80`033784d0 fffff880`01e5c180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0a1fc390 fffff800`01c83f93 : 00000000`00000101 00000000`00000000 fffff960`00137fe0 fffff900`c0e639a0 : nt!NtReadFile+0x631
fffff880`0a1fc480 fffff800`01c80530 : fffff960`00193873 fffffa80`046b4830 00000000`00000000 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a1fc688 fffff960`00193873 : fffffa80`046b4830 00000000`00000000 00000000`00000001 fffffa80`04a14490 : nt!KiServiceLinkage
fffff880`0a1fc690 fffff960`00138064 : fffff900`c0e639a0 00000000`00000000 00000000`00000010 00000000`00000282 : win32k!StartDeviceRead+0x1df
fffff880`0a1fc6f0 fffff800`01c783b1 : 00000000`00000100 00000000`00000000 0000020d`00000000 00000000`00000000 : win32k!InputApc+0x84
fffff880`0a1fc720 fffff800`01c8a19d : fffffa80`04a14440 00000000`00000000 fffff960`00137fe0 00000000`00000000 : nt!KiDeliverApc+0x201
fffff880`0a1fc7a0 fffff800`01c894aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`0a1fc830 fffff960`00103ab9 : 00000000`00000004 fffffa80`03527320 00000000`00000001 00000000`0000000d : nt!KeWaitForMultipleObjects+0x272
fffff880`0a1fcaf0 fffff960`0009474c : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000294 : win32k!RawInputThread+0x6ed
fffff880`0a1fcbc0 fffff960`0011459a : fffffa80`00000002 fffff880`0a1b7f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`0a1fcbf0 fffff800`01c83f93 : fffffa80`04a14440 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`0a1fcc20 000007fe`fdd51eda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00a9f9a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdd51eda

STACK_COMMAND:  kb
FOLLOWUP_IP: 
Maestro2+1224
fffff880`02a2e224 410fb74704      movzx   eax,word ptr [r15+4]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  Maestro2+1224
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Maestro2
[B][COLOR=#FF0000]IMAGE_NAME:  Maestro2.sys[/COLOR][/B]
DEBUG_FLR_IMAGE_TIMESTAMP:  45500365
FAILURE_BUCKET_ID:  X64_0x50_Maestro2+1224
BUCKET_ID:  X64_0x50_Maestro2+1224
Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        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: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000000723e1, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0
Debugging Details:
------------------

BUGCHECK_STR:  0x4E_7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME:  firefox.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80001d2e138 to fffff80001cced00
STACK_TEXT:  
fffff880`02bef978 fffff800`01d2e138 : 00000000`0000004e 00000000`00000007 00000000`000723e1 00000000`00000001 : nt!KeBugCheckEx
fffff880`02bef980 fffff800`01d3e546 : fffff880`02bef900 fffff880`02befaa0 fffffa80`02f40000 fffff800`01cffb2d : nt! ?? ::FNODOBFM::`string'+0x175b6
fffff880`02bef9c0 fffff880`03fc4ed5 : 00000000`00000082 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x37875
fffff880`02befa50 fffff880`03fc3cc3 : 00000000`00000000 00000000`00000000 fffffa80`000000e8 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+0x31
fffff880`02befa80 fffff880`03fbe8e5 : fffff8a0`035494b0 fffff8a0`035494b0 fffffa80`032d4f00 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x87
fffff880`02befae0 fffff880`03fb125d : fffff8a0`035494b0 fffffa80`02f40000 fffffa80`032d4f70 fffffa80`02f40000 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x155
fffff880`02befb30 fffff880`03fac358 : fffffa80`03433340 fffffa80`02f7c010 00000000`00000000 fffff880`02befca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`02befc50 fffff880`03fca16d : fffffa80`00000000 fffffa80`02f21410 00000000`0000000f fffff880`03fcbf09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`02befca0 fffff880`03fc93f8 : fffff880`01e60f00 fffffa80`036db010 00000000`00000000 00000000`00000202 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`02befcd0 fffff880`03fc8e96 : 00000000`00000000 fffffa80`02f7c010 00000000`00000080 fffffa80`02f21410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`02befd00 fffff800`01f6b32e : fffff880`021632a0 fffffa80`02f0fb60 fffffa80`018a89e0 ffffffff`80000248 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02befd40 fffff800`01cc0666 : fffff880`01e5c180 fffffa80`02f0fb60 fffff880`01e66f80 fffff880`01224cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`02befd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_IP: 
dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
fffff880`03fc4ed5 4c8b1ddcd1fdff  mov     r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`03fa20b8)]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
FAILURE_BUCKET_ID:  X64_0x4E_7_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
BUCKET_ID:  X64_0x4E_7_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
Followup: MachineOwner

[h=3]PFN_LIST_CORRUPT - Possible faulty RAM[/h]download a program called Memtest86+
this program will test your ram for faults

Take all the ram out of your pc except one,
stop at 7 passes ( the pass count in the middle not
the top)
OR
untill you get errors ( red lines accross lower part
of screen) + error count will increase
which ever comes first
if the RAM passes then this is ok, if the ram fails
then put this to the side
You need to check all RAM you have and do the same
as above
7 passes may take a few hours so be patient :)

_____________________________


PAGE_FAULT_IN_NONPAGED_AREA - Hardware fault , since the above error speculates faulty ram , i would say the RAM is at fault,

do the Memtest steps
 


zigzag3143

Honorable Member
Microsoft MVP
#3
Good evening, in an attemp to be brief: I've been using this build for several months without any issues, but suddenly a week or so ago I start having seemingly random BSODs. I believe I've narrowed down the problem to these suspects: AIMP3 (music player, causes some graphical glitches if set to be "always on top" and another app goes fullscreen, althought I've used it for *a while* without any real problems), TeamSpeak (voice chatting program, recetly installed), Ragnarok (an "old" game, recently installed, tried several compatibility modes just in case but with no effect), KeyMaestro (keyboard driver and utility, an older version was responsible for BSODs on Windows 7, but I've been using this one for month without issues), Firefox Aurora (alpha version, updated constanly), CCleaner (foolishly used it's "registry cleaner" capabilities, already undone changes and awaiting to see effect) and Windows Search (recently installed, haven't tried disabling it yet). But finding wich one is the real culprit is proving to be a troublesome task, hence I turn to you, hoping you may help me solve this irksome situation.

I attach more than enough information about the system, you can have a quick look at this CPU-Z Screenshot or this Speccy generated report: http://speccy.piriform.com/results/WaFyPAniYnvfPsgX6gcFNPw
Because of Kaos' excellent work a pattern is beginning to emerge. It seems that something (maestro2 ?) is requesting a thread lock at the same time your directX (portion of the video driver) is. In one the relationship is obvious and in another probable.

Maestro2+0x1224
fffff880`0a1fc118 fffff800`01c8abcc : ffffffff`ffb3b4c0 fffff880`02a225cf fffffa80`048e7e40 fffff880`02a225cf : 0x1
fffff880`0a1fc120 fffffa80`04bfd3e0 : 00000000`00000028 00000000`00000004 00000000`00000026 fffff880`02a1f0a0 : nt!ExAcquireResourceExclusiveLite+0x14f

Since I assume you want to continue to run maestro (a 2006 app) your other option is to update the video driver and directX.

If/when you do please follow these instructions to remove the current one and install the newest version you can find.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.


Ken
 


#4
Hi there!

Thanks for replying and sorry for my delay replying, I had just undone CCleaner's doings on the registry and it seemed to had done the trick, but now I had another stop screen (attached for your pleasure).

I'll try uninstalling KeyMaestro and see how that goes (althought it bugs me greatly that it had been working perfectly fine for months up until recently, but hell, let's try)
 


Attachments

zigzag3143

Honorable Member
Microsoft MVP
#5
Hi there!

Thanks for replying and sorry for my delay replying, I had just undone CCleaner's doings on the registry and it seemed to had done the trick, but now I had another stop screen (attached for your pleasure).


I'll try uninstalling KeyMaestro and see how that goes (althought it bugs me greatly that it had been working perfectly fine for months up until recently, but hell, let's try)
This one was caused by your directx. I would re-install the video driver with most current.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.
 


#6
Well, sadly as expected removing the keyboard driver solved the problem..

But the thing is, I really miss the extra functionality that only works when the driver is working: integrated scroll wheel and 4 custom keys.

Anyone kwnows a program that could enable this? Or pointers on creating a custom keyboard driver or something? I'm REALLY accustomed to having a scroll wheel available to my left pinky finger '^^
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.