Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

A problem with BSODs, spanning 3 years ;) Help appreciated!


  • Please log in to reply
14 replies to this topic

#1 IainP

IainP

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 09 April 2015 - 09:57 PM

Hi minds of Bleeping Computer.

I've been having this problem for quite some time now,
Appeared 3 years ago after moving from Linux system to Windows Server 2008 for Voice chat, and Multiplayer server hosting with some local & overseas friends. Back then, I had complaints that the server was inaccessible while I was out at work, which turned out to be it BSOD'ing randomly, even when idle.. I tried everything I could think of at the time with no luck. So it was boxed up and put away in the attic.

Today, 3 years later, I felt like having another bash at it.

 

-Initially it wouldn't even post. Fixed by clearing cmos.

-Used Memtest to check installed Ram individually, (Originally 2x4GB, Currently 1x4GB) One of the cards had a few errors. Removed in hope of fixing the underlying problem.

-Clean install everything a-ok apart from a problem with the onboard LAN not starting with code 10. Downloaded an older version of the problem driver.. Hey presto working internet connection.

-After getting the usual updates installed, and the third-party server hosting apps running, all seemed well! Thinking what ever had happened was fixed in an update. Nope, tried to log in through rdc after letting it idle overnight, Unable to initialize connection.. Completely unresponsive until hard reset. (Exact same symptoms as before)

System info:
 

-Computer Type:   ACPI x64-based PC

-Operating System:   Microsoft Windows Server 2008 - Service Pack 2

-CPU Type:   QuadCore Intel Core 2 Quad Q9650, 3000 MHz (9 x 333)

-Motherboard Name:   ASRock G31M-GS (2 PCI, 1 PCI-E x1, 1 PCI-E x16, 2 DDR2 DIMM, Audio, Video, Gigabit LAN)

-System Memory:   4GB [3317 MB] (DDR2-800 DDR2 SDRAM)

-BIOS Type:   AMI (05/20/11)

-Network Adapter: Realtek PCIe GBE Family Controller [RTL8168/8111] (192.168.1.217)

(Any other info about system needed, let me know)

I've gathered all the information I think could help, starting with the BSODs:
 

==================================================
Dump File         : Mini041015-02.dmp
Crash Time        : 10/04/2015 01:27:29
Bug Check String  : 
Bug Check Code    : 0x00000101
Parameter 1       : 00000000`00000030
Parameter 2       : 00000000`00000000
Parameter 3       : fffffa60`017d2180
Parameter 4       : 00000000`00000003
Caused By Driver  : WMILIB.SYS
Caused By Address : WMILIB.SYS+c4e180
File Description  : WMILIB WMI support library Dll
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Processor         : x64
Crash Address     : ntoskrnl.exe+57150
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\Mini041015-02.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 270,000
Dump File Time    : 10/04/2015 01:44:25
==================================================
==================================================
Dump File         : Mini041015-01.dmp
Crash Time        : 10/04/2015 00:09:21
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`000000e8
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffffa60`0254fb68
Caused By Driver  : USBPORT.SYS
Caused By Address : USBPORT.SYS+2b68
File Description  : USB 1.1 & 2.0 Port Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.0.6002.18875 (vistasp2_gdr.130628-1536)
Processor         : x64
Crash Address     : ntoskrnl.exe+57150
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\Mini041015-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 270,000
Dump File Time    : 10/04/2015 01:09:06
==================================================
Dump files available here [http://we.tl/b8wRNnj2vb]{WeTransfer}
(Available for 7 days from 10/04/2015)

 
Had a look through event viewer for anything that stood out that could be the problem..

Found the below which occurs every so often but doesn't appear to cause any problems:

------------------------------------------------------------------------------------------------------------------------------------------------------------
Information 09/04/2015 16:23:16 Microsoft-Windows-Kernel-Processor-Power 4 None "Processor 0 exposes the following:
1 idle state(s)
0 performance state(s)
0 throttle state(s)"
 
Information 09/04/2015 16:23:16 Microsoft-Windows-Kernel-Processor-Power 4 None "Processor 3 exposes the following:
1 idle state(s)
0 performance state(s)
0 throttle state(s)"
 
Information 09/04/2015 16:23:16 Microsoft-Windows-Kernel-Processor-Power 4 None "Processor 2 exposes the following:
1 idle state(s)
0 performance state(s)
0 throttle state(s)"
 
Information 09/04/2015 16:23:16 Microsoft-Windows-Kernel-Processor-Power 4 None "Processor 1 exposes the following:
1 idle state(s)
0 performance state(s)
0 throttle state(s)"
 
Error 09/04/2015 16:23:16 Microsoft-Windows-Kernel-Processor-Power 6 None Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Repeats every so often.


Thanks for taking the time to read this, 
Any information or help would be greatly appreciated as I don't want this machine to go to waste.

-Iain

 



BC AdBot (Login to Remove)

 


#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:42 AM

Posted 12 April 2015 - 11:02 AM

The wmilib.sys driver is part of Windows Management Instrumentation, which allows for various monitoring services to report. The 0x00000101 bugcheck code indicates the processor was deadlocked and not processing interrupts while WMI was running.

 

Based on the Event Viewer logs, particularly the very last one, you probably need to update the firmware as the current version isn't fully compatible with the processor, or replace the processor with one that is compatible.



#3 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 16 April 2015 - 08:13 AM

The wmilib.sys driver is part of Windows Management Instrumentation, which allows for various monitoring services to report. The 0x00000101 bugcheck code indicates the processor was deadlocked and not processing interrupts while WMI was running.

 

Based on the Event Viewer logs, particularly the very last one, you probably need to update the firmware as the current version isn't fully compatible with the processor, or replace the processor with one that is compatible.

Thanks for reply, will update the firmware and edit the topic if it resolves the problem. 

I noticed on the spec sheet for the Q9650 that it does not support Turbo boost and Hyper-threading. Although during initial bios setup I think turbo-boost was enabled. Could this maybe cause the processor problems? Will also try disabling this in bios.

Thanks again for the reply!



#4 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 16 April 2015 - 08:54 AM

[UPDATE] BIOS Updated, after update Turbo-boost option disappeared. Will run stability test and report back.



#5 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 16 April 2015 - 11:05 PM

Bios Update did not resolve problem.. Processor stress test lasted for about 12 hours then failed. The below bsod report details a different problem:

Any thoughts sflatechguy? Sorry for the bother.

 

==================================================

Dump File         : Mini041615-01.dmp
Crash Time        : 16/04/2015 02:09:46
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff280`03f6a398
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`0189c221
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57150
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+57150
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\Mini041615-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 270,000
Dump File Time    : 16/04/2015 13:27:24
==================================================
 
Trying to include as much information as possible so heres a bug check of the above minidump.
*******************************************************************************
*                                                                             *
*                        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: fffff28003f6a398, 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: fffff8000189c221, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a37080
 fffff28003f6a398 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
nt!ExpScanGeneralLookasideList+51
fffff800`0189c221 418b41d8        mov     eax,dword ptr [r9-28h]
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
TRAP_FRAME:  fffffa6001b2ba20 -- (.trap 0xfffffa6001b2ba20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000080 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff800019a1a40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000189c221 rsp=fffffa6001b2bbb0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff28003f6a3c0 r10=0000000000000004
r11=fffffa8003f6a340 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!ExpScanGeneralLookasideList+0x51:
fffff800`0189c221 418b41d8        mov     eax,dword ptr [r9-28h] ds:bce0:fffff280`03f6a398=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80001866eee to fffff80001867150
 
STACK_TEXT:  
fffffa60`01b2b8d8 fffff800`01866eee : 00000000`0000000a fffff280`03f6a398 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`01b2b8e0 fffff800`01865dcb : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`019a1a50 : nt!KiBugCheckDispatch+0x6e
fffffa60`01b2ba20 fffff800`0189c221 : fffffa80`00000000 00000000`00000000 fffff800`019c0408 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`01b2bbb0 fffff800`0187a390 : 00000000`00000000 fffff800`0187acb0 fffffa80`02798b00 00000000`00000001 : nt!ExpScanGeneralLookasideList+0x51
fffffa60`01b2bbe0 fffff800`0187adcb : fffffa80`02798b00 00000000`00000008 00000000`00000001 00000000`00000000 : nt!ExAdjustLookasideDepth+0x40
fffffa60`01b2bc10 fffff800`01a71bd7 : fffffa80`02798bb0 00000000`00000080 00000000`00000000 184b8d48`80000001 : nt!KeBalanceSetManager+0x11b
fffffa60`01b2bd50 fffff800`018a4446 : fffff800`01983680 fffffa80`02798bb0 fffff800`01988b80 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffa60`01b2bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!ExpScanGeneralLookasideList+51
fffff800`0189c221 418b41d8        mov     eax,dword ptr [r9-28h]
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+51
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  54ee68c3
 
FAILURE_BUCKET_ID:  X64_0xA_nt!ExpScanGeneralLookasideList+51
 
BUCKET_ID:  X64_0xA_nt!ExpScanGeneralLookasideList+51
 
Followup: MachineOwner
---------
From the above, I cant really see anything that points to a specific driver..
Found a support article here which looks fairly close to the problem but don't want to apply any hotfixes until confirmation:
https://support.microsoft.com/en-us/kb/979444
 

Will be doing another memtest on the currently installed ram tomorrow to rule that out completely. 


Edited by IainP, 16 April 2015 - 11:14 PM.


#6 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:42 AM

Posted 17 April 2015 - 07:08 AM

Blue screens involving the ntlkrnlmp.exe driver are usually caused either by incorrect settings in the BIOS, or faulty system memory.

The 0xa bugcheck code usually results from a faulty device driver, a system service that isn't running or configured properly, or problems with the BIOS.

 

The hotfix could well solve your particular issue. But before applying it, you might want to doublecheck your BIOS settings first, particularly the power management settings and any CPU settings. Are you overclocking your CPU?

Also make sure your Windows Updates and drivers are up to date.



#7 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 18 April 2015 - 10:42 AM

Have just modified the bios: Enhanced Halt State is now enabled aswell as No-execute Memory protection, Seeing if that will make a difference in stability.
Other changes include: ACPI HPET Table set to enabled; 

CPU is not overclocked, All updates and drivers are up to date.

 

Currently running memtest will report results on currently installed ram (Should be clean) and previously removed ram (Reported errors).

[EDIT]

No-Execute reverted to disabled after page fault. 
Memory test completed on installed memory, 2 pass successful. No errors.
Running stress test to check if remaining bios changes have solved problem.


Edited by IainP, 18 April 2015 - 12:49 PM.


#8 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 20 April 2015 - 04:08 PM

Stress test failed. This time with a Bug check code: memory_management 0x1a

Failed again after that with a Bug check code: kmode_exception_not_handled 0x1e

If any more information is required on the above stops let me know.


Even though memtest was clear on currently installed ram I'm still a bit skeptical, Have switched out the 4GB with a 2GB I found the other night. Will update if it has made any difference. 



#9 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:42 AM

Posted 20 April 2015 - 06:47 PM

Can you include the first parameter that appeared with the memory_management 0x1a bugcheck code? It will appear as Arg1. More than a few of those point to hardware issues.

 

The kmode_exception_not_handled 0x1e bugcheck code is pretty common and covers a lot of things. Any other information from that minidump would be appreciated. The most common causes are hardware incompatibility and faulty drivers.

 

You may want to run some tests on your CPU. Here is the link for the Intel Processor Diagnostic Tool: http://www.intel.com/support/processors/sb/CS-031726.htm



#10 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 21 April 2015 - 06:12 AM

BugCheck 1A, {30, fffffa8004064280, fffffa6001d91000, fffff88007edf70c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+1ce6 )
==================================================
Dump File         : Mini041915-01.dmp
Crash Time        : 19/04/2015 08:34:10
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00000030
Parameter 2       : fffffa80`04064280
Parameter 3       : fffffa60`01d91000
Parameter 4       : fffff880`07edf70c
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+56290
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+56290
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\Mini041915-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 270,072
Dump File Time    : 19/04/2015 15:03:05
==================================================
 
Interesting, with the old 2GB DDR2 800 Unbuffered Non-ecc memory in it appears to be running smoothly. The intel processor diagnostics returned a pass.
Could this be a problem with the 4GB ram modules I bought back in 2012, even though memtest has checked and ok'd on 7 Passes? There 'shouldn't' be any compatibility errors.. 

Here are the links to the 8GB(2x4GB) memory and the motherboard spec sheet. Just to see if you can see a compatibility problem I might have overlooked:
mem: http://www.amazon.co.uk/dp/B0043BF3AE/ (£120 of ouch)
mb: http://www.asrock.com/mb/Intel/G31M-GS/

Will keep this stress test going for a further day and then test with the intel processor diagnostics in the following configurations(as it also appears to test installed memory also):

         |Test1|Test2|Test3|Test4|
Slot 1|4GB  |2GB  |2GB  |-------|
Slot 2|2GB  |4GB  |-------|2GB  |
         |         |         |PASS|         |

Will update with results. 
 
Here is the kmode_exception information you also asked for:
==================================================
Dump File         : Mini042015-01.dmp
Crash Time        : 19/04/2015 17:19:01
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff960`002c84ad
Parameter 3       : 00000000`00000000
Parameter 4       : 00001200`00000208
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+1e84ad
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+56290
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\Mini042015-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 6002
Dump File Size    : 270,072
Dump File Time    : 20/04/2015 18:33:49
==================================================
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff960002c84ad, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000120000000208, Parameter 1 of the exception
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
 
FAULTING_IP: 
win32k!vRestartKillEudcRFONTs+a1
fffff960`002c84ad 488bb308020000  mov     rsi,qword ptr [rbx+208h]
 
EXCEPTION_PARAMETER1:  0000000000000000
 
EXCEPTION_PARAMETER2:  0000120000000208
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a46080
 0000120000000208 
 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
 
BUGCHECK_STR:  0x1E_c0000005
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
 
PROCESS_NAME:  csrss.exe
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  fffffa6004a52790 -- (.trap 0xfffffa6004a52790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff900c000f410
rdx=fffff900c0777ee0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002c84ad rsp=fffffa6004a52920 rbp=fffff900c000f410
 r8=fffffa6004a529b8  r9=fffff90000411ff8 r10=fffff90000012000
r11=fffff900c0015010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!vRestartKillEudcRFONTs+0xa1:
fffff960`002c84ad 488bb308020000  mov     rsi,qword ptr [rbx+208h] ds:00000000`00000208=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80001858267 to fffff80001875290
 
STACK_TEXT:  
fffffa60`04a51fa8 fffff800`01858267 : 00000000`0000001e ffffffff`c0000005 fffff960`002c84ad 00000000`00000000 : nt!KeBugCheckEx
fffffa60`04a51fb0 fffff800`018750e9 : fffffa60`04a526e8 00001200`00000000 fffffa60`04a52790 fffff900`c000b680 : nt! ?? ::FNODOBFM::`string'+0x29177
fffffa60`04a525b0 fffff800`01873ee5 : 00000000`00000000 00000000`00000000 fffff6fb`7e580000 00001200`00000000 : nt!KiExceptionDispatch+0xa9
fffffa60`04a52790 fffff960`002c84ad : fffffa80`05ec2800 00001f80`01000bb0 00000000`00002000 fffff900`00000021 : nt!KiPageFault+0x1e5
fffffa60`04a52920 fffff960`002c86b8 : fffffa80`04928a70 fffffa80`04928a70 fffff900`c000b8e0 00000000`00000000 : win32k!vRestartKillEudcRFONTs+0xa1
fffffa60`04a52970 fffff960`002c87f5 : fffff900`c001ff58 00000000`00000000 fffff900`c000f410 fffff900`c07806c0 : win32k!vRestartKillEudcRFONTs+0x2ac
fffffa60`04a529b0 fffff960`002c9717 : fffff900`c000f3f0 00000000`00000001 fffff900`c0025d20 fffff960`00365a30 : win32k!vRestartKillEudcRFONTs+0x3e9
fffffa60`04a52a10 fffff960`002c97f4 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000144 : win32k!ParseFontLinkEntry+0xaef
fffffa60`04a52a70 fffff960`002d162b : fffff6fb`800083f8 fffff880`06b63d90 fffff6fb`7dc00040 fffff800`01855aa8 : win32k!GreEnableEUDC+0xa0
fffffa60`04a52aa0 fffff960`002d0e59 : fffffa80`05ec2800 00000000`0000095c 00000000`00000000 00000000`74756d63 : win32k!GdiMultiUserFontCleanup+0x3b
fffffa60`04a52ad0 fffff960`001d040c : 00000000`00000080 fffffa60`0476e000 fffff880`06b63d70 00000000`4d504f20 : win32k!MultiUserNtGreCleanup+0x71
fffffa60`04a52b10 fffff800`01a53e38 : fffffa60`0476ec00 fffffa80`05d878a0 fffffa60`0476e000 fffffa80`05d87800 : win32k!Win32KDriverUnload+0xa8
fffffa60`04a52b40 fffff800`01b26655 : 00000000`00060107 fffffa80`05ec2800 fffffa60`04a52bc8 fffffa60`0476e000 : nt!MiDereferenceSessionFinal+0xf8
fffffa60`04a52bc0 fffff800`018551c4 : 00000000`00000001 00000000`00000000 fffffa80`05ec2800 fffffa80`05d878a0 : nt! ?? ::NNGAKEGL::`string'+0x11965
fffffa60`04a52bf0 fffff800`01ad84d5 : fffff880`075b7240 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmCleanProcessAddressSpace+0x638
fffffa60`04a52c40 fffff800`01ada94d : fffffa80`00000000 00000000`00000001 00000000`00000000 fffff800`01a80977 : nt!PspExitThread+0x4ad
fffffa60`04a52d30 fffff800`018b24a6 : fffffa60`005ec180 00000000`00000080 fffffa80`05d878a0 00000000`00000000 : nt!PspTerminateThreadByPointer+0x4d
fffffa60`04a52d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
win32k!vRestartKillEudcRFONTs+a1
fffff960`002c84ad 488bb308020000  mov     rsi,qword ptr [rbx+208h]
 
SYMBOL_STACK_INDEX:  4
 
SYMBOL_NAME:  win32k!vRestartKillEudcRFONTs+a1
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: win32k
 
IMAGE_NAME:  win32k.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  54ee6961
 
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_win32k!vRestartKillEudcRFONTs+a1
 
BUCKET_ID:  X64_0x1E_c0000005_win32k!vRestartKillEudcRFONTs+a1
 
From the above highlighted points it does look like its having problems with memory...
Did a wee bit of digging and found this on another forum:

 

 

Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Can't help but notice on the amazon page where I bought the ram 
  • "Well tested, Non-ECC Non parity"
I'm not quite familiar with parity/parity errors but it just might be the problem..


#11 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:42 AM

Posted 21 April 2015 - 01:55 PM

The parameters for those bugchecks do point to memory, although it still isn't clear if it's hardware, drivers, or the system memory itself.

However, if swapping out the memory has reduced the blue screens, it looks like the RAM wasn't compatible with your system. Your motherboard does support non-ECC memory.

Parity was more of an issue with older RAM and motherboards and shouldn't be a factor; your motherboard doesn't require parity RAM.

And you are correct about memory tests -- they aren't foolproof.



#12 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 23 April 2015 - 08:23 AM

Well it appears the problem has been solved! System is still running stable and below are the results for the different slots. Sure am glad I managed to find that spare 2GB stick.

         |Test1|Test2|Test3|Test4|
Slot 1|4GB  |2GB  |2GB  |-------|
Slot 2|2GB  |4GB  |-------|2GB  |
         |FAIL |FAIL  |PASS|PASS|

Feel fairly disappointed that it was simply the ram that was causing the problem. I'm not sure wither I should buy a fresh set from the above supplier or go with a more common 2GB DDR2 and stick with 4GB total, instead of trying for the maximum addressable. 

Even though 'Komputerbay' boasts a lifetime warranty, it only covers products found on the active market today, so I'm stuck with these faulty modules and down £120.

Ach well, Thanks sflatechguy for the time you've put in to help with this, and giving me better knowledge on identifying errors in BSOD dumps.

 


Edited by IainP, 23 April 2015 - 08:24 AM.


#13 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:42 AM

Posted 23 April 2015 - 09:04 AM

Glad you got that resolved. :)

Pity about the RAM though; given what you are using the server for, it could do with more than 4GB total. You may want to check with ASRock and see what types of RAM they recommend for that motherboard.



#14 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:42 AM

Posted 23 April 2015 - 06:36 PM

I've had similar problems with off brand or "gaming" ram that wouldn't operate properly unless the timings and voltage are set manually, and even then still had intermittent problems.

Generally I'd recommend to stick with oem (samsung, hynix, etc.) or name brand ram like Crucial or Kingston that meets one of the supported voltage and timing combinations, or anything from the motherboard manufacturer's compatibility list.


Have you tried turning it off and on again?


#15 IainP

IainP
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:06:42 AM

Posted 26 April 2015 - 05:24 PM

Yeh 4GB isn't ideal.. Good Idea! Will get in contact with ASRock and see what they recommend for getting ram that will utilize the entire 8GB max addressable.

That's the thing! The only ram modules I can find that are 4GB DDR2 240-pin and non-ecc and unbuffered, seem to only be from off brand suppliers as they are old and apparently rare.

 

[EDIT] Saying that, was checking the compatibility list for the motherboard there seems to be only three compatible 4GB DDR2-800s, Did a we search and found that the Kingston & OCZ ones just don't seem to be available anymore these days... and the Aeneon Sticks are available but are ranging from £136 to £200.. Better off just buying a new board that is in the ddr3 range of things (Waste of a perfectly good board though).

http://www.asrock.com/mb/memory/G31M-GS%20R2.0.pdf

 


Edited by IainP, 26 April 2015 - 05:57 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users