BSOD please help.

SonnyBlack

New member
Joined
Dec 14, 2013
Posts
4
Hi , After a fresh install of win 8.1 i got blue screen of death a lot of times.Memory_managment and othera lot of times i downgrade it to win 7 and win 8, but nothing i got all updates and other drivers.



Windows 8.1
x64
Fresh Install of 8.1 before was win 7 then win 8 and now Windows 8.1


AMD Phenom II x6 1100T BE
GIGABYTE GA-990XA-UD3
16 GB RAM Corsair Venegrance
ASUS 6870 1GB



View attachment Windows7_Vista_jcgriff2.zip
Capture.JPG
 
Have you installed all the Windows Updates?

Code:
[COLOR=#ff0000]BugCheck 19[/COLOR], {[COLOR=#0000cd]3[/COLOR], [COLOR=#008000]fffff9014492e010[/COLOR], fffff9014492ff10, fffff9014492e010}

Probably caused by : win32k.sys ( win32k!AllocCallbackMessage+fa )

Code:
0: kd> [COLOR=#008000]!pool fffff9014492e010[/COLOR]
fffff80079cb5340: Unable to get special pool info
fffff80079cb5340: Unable to get special pool info
Pool page fffff9014492e010 region is GetUlongFromAddress: unable to read from fffff80079d50208
Unknown
*[COLOR=#ff0000]fffff9014492e000[/COLOR] size:  990 previous size:    0  (Free)      *Gh15
        Pooltag Gh15 : [COLOR=#ff0000]GDITAG_HMGR_SPRITE_TYPE[/COLOR], Binary : win32k.sys
 fffff9014492e990 size:  670 previous size:  990  (Allocated)  Gh15

Code:
0: kd> [COLOR=#008000]!poolval fffff9014492e010[/COLOR]
Pool page fffff9014492e010 region is Unknown

Validating Pool headers for pool page: fffff9014492e010

Pool page [ fffff9014492e000 ] is [COLOR=#ff0000]VALID[/COLOR].

It's interesting that the free linked list is corrupt, but the pool page and it's headers still seem to be valid.

Code:
[COLOR=#ff0000]BugCheck 1A[/COLOR], {[COLOR=#0000ff]5003[/COLOR], [COLOR=#008000]fffff58010804000[/COLOR], 15c9, 15f80005c92}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6327 )

The other bugcheck reveals that your working set free list is corrupt, the second parameter contains the address of the working set free list.

Code:
0: kd> [COLOR=#008000]!wsle fffff58010804000[/COLOR]
Not enough space to read nt!_MMWSL-FirstDynamic
c0000005 Exception in kdexts.wsle debugger extension.
      PC: 00000000`752b812f  VA: 00000000`00000000  R/W: 1003f  Parameter: 00000000`00000000

Since this is a Minidump, the !wsle extension and _MMWSLE data structure aren't going to display properly.

Suggestions:

I would suggest testing the RAM with MemTest86+ for at least 9 to 10 passes - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-with-memtest86.html
 
** LOL, Harry, every single time.

Hi,

We have various bug checks:

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

BugCheck 1A, {411, fffff680003b9f80, 6d00, fffff68000000003}

The 1st parameter of the bug check is 411 which indicates a page table entry (PTE) has been corrupted.

BAD_POOL_HEADER (19)

This indicates that a pool header is corrupt.

Code:
0: kd> !poolval fffff9014492e010
fffff80079cb5340: Unable to get special pool info
fffff80079cb5340: Unable to get special pool info
Pool page fffff9014492e010 region is unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
Unknown

Validating Pool headers for pool page: fffff9014492e010

Pool page [ fffff9014492e000 ] is [B][COLOR=#ff0000]VALID[/COLOR][/B].

So far this doesn't look hardware memory related (RAM) but likely a device driver causing the corruption.

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+b2fbe )


FAILURE_BUCKET_ID: X64_0x50_atikmdag+b2fbe

^^ ATI/AMD video driver.


SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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.

FAILURE_BUCKET_ID: X64_0x3B_win32k!RFONTOBJ::vDeleteRFONT+32

BUCKET_ID: X64_0x3B_win32k!RFONTOBJ::vDeleteRFONT+32


^^ Possible corrupt font cache.

------------------------------

1. Create a Restore Point - Restore Point - Create in Windows 8

2. After doing #1, navigate to C:\Windows\System32. Once inside, find and rename FNTCACHE.DAT to FNTCACHE.OLD

Restart the system and let Windows rebuild the font cache.

3. AODDriver2.sys - Wed Nov 21 02:44:04 2012

^^ AMD Overdrive; also in EasyTune6 for Gigabyte motherboard - Known BSOD issues in Win 7, especially 8 and/or 8.1 Remove ASAP.

Regards,

Patrick
 
Okay i did let windows to rebuild the font cache.I didnt have any probs before but i mean that is graphic drivers cuz sometimes i got some red lines and also i got them when i am on chrome :| so any chance to know it is RAM broken or what..4 Sticks of Ram 4x4 Vengeance Corsair. What to do or any chance to fix it? to try to get back on windows 7 because of drivers that are not (maybe) updated with win 8.1 :( i have these RAM abt a year and never had probs with them..
 
Please also follow my 3rd suggestion.

Ensure you also have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

If you continue to crash after all of that, follow BlueRobot's suggestion of running Memtest.

Regards,

Patrick
 
Okay Patric i also did Run the Memory Diagnostics Tool and no problems detected.Okay thanks i will back tomorrow.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top