BSOD's randomly, app crashes, and freezing.

KillianB · 09 Dec 2012

Okay so let me start off by saying this has been going on for about a year now. Before you ask why I had not come here sooner allow me to explain the issue. I first got this computer from Newegg when I was looking for a computer to replace my old out of date office computer. I just wanted a computer that did okay gaming wise as money was tight so my options were not that wide. I had read a lot about computers and their hardware and found this one.

I have included the RAR from the SF Diagnostic Tool. Now the computer was great, high frame rates in games, fluid playing and on medium to high graphics. I'm a basic gamer not really hardcore you'll notice by my rig. About six month into owning this rig there was a graphics driver update and I ran it, installed it and that's when issues started appearing. I have no idea if this was a coincidence or is the source so here's the reason it took so long to come here.

Every single time I had a BSOD I read the dump and in my infinite non-existant knowledge of BSOD's attempted to solve it. Each time I did something it seemed to help and fended off the issue for days, weeks, and even months. Now here I am, the problem getting worse and worse and I just cannot make it better even in the slightest. Games randomly close, files randomly claim to be corrupt, mozilla crashes every three minutes then eventually freezes and has to be end processed and re-opened. Randomly Active X control box pops up stating it's not working properly and some things won't be viewed correctly. Files I download if quite large (600mb-1GB) in size, corrupt.

League Of Legends errors and refuses to work at times, I can't repair files in the game due to blue screening in the middle of repair or it crashing. Minecraft randomly closes with no error notice, when it does error it's a Java environment run time error. My steam always is the first thing to corrupt it seems. The source of 90% of my games and it will error and not open so I just have it removed from my computer entirely.

Most of the blue screens I've gotten are dxgkrnl.exe related. I simply just do no know the issue anymore. I've reseated my graphics card to be sure it was placed tightly and properly, as well as my RAM sticks. My rig is clean as a whistle with simply compressed air, no static damage I've always been cautious. So simply this is the end of my options. Through other BSOD posts I've over the course of this issue checked the hardware with stress tests and so forth and it seems to check out, maybe I did it wrong who knows. Help would be appreciated, because I really can't afford a new computer, maybe a new part, not a whole new rig though.

Regards,
Killian

KillianB · 09 Dec 2012

Just had a memory management BSOD, but as said most of them revolve around dxgkrnl and memory management, bad pool header, and so on :/

koolkat77 · 10 Dec 2012

Welcome to Sevenforums.

Please uninstall Norton, it often contributes in BSOD-s just like it's doing in yours, consider uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials at least to test.

Norton Removal Tool

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

1. Microsoft Security Essentials - Free Antivirus for Windows
2. Malwarebytes - Free
3. Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Click on User CP on the top right of this page
Click on Edit System Spec
Fill in your computer specs
- System Info - See Your System Specs

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

1. Click on the
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Upload a screenshot of your hard disk using crystal disk info and summary tab using Speccy:

Make a hard drive test from the hard drive manufacturers website:

Hard Drive Diagnostic Procedure

Test RAM in the following manner:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.

Postback results.

BSOD BUGCHECK SUMMARY:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, 
Breakpoint with no debugger attached, Hardware incompatibility, 
Faulty system service, Memory, 3rd party remote control, 
BugCheck 1000007E, {ffffffffc0000005, fffff80002e12a9b, fffff880039a4bc8, 
fffff880039a4420}

*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )
PROCESS_NAME:  System
Debug session time: Sun Dec  9 18:01:14.426 2012 (UTC + 6:00)
System Uptime: 0 days 1:39:59.254
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA   

Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {c605990, 1, 7fef81814ac, 8}
Could not read faulting driver name
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
PROCESS_NAME:  rundll32.exe
Debug session time: Sun Dec  9 21:41:33.998 2012 (UTC + 6:00)
System Uptime: 0 days 2:20:15.216
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 

Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff80002c8ff9f, fffff880080b6ef0, 0}
Probably caused by : Unknown_Image ( nt!KiSearchForNewThread+38f )
PROCESS_NAME:  FlashPlayerPlu
Debug session time: Sun Dec  9 14:53:37.480 2012 (UTC + 6:00)
System Uptime: 0 days 0:28:01.697
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, 
Breakpoint with no debugger attached, Hardware incompatibility, 
Faulty system service, Memory, 3rd party remote control, 
BugCheck 1000007E, {ffffffffc0000005, fffff88005970387, fffff880055c5e48, 
fffff880055c56a0}
Debug session time: Sun Dec  9 19:20:41.852 2012 (UTC + 6:00)
System Uptime: 0 days 1:18:54.069
Probably caused by : atikmdag.sys ( atikmdag+102387 )
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 

Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff80002db69bc, fffff880078bbf20, 0}

*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
*** WARNING: Unable to verify timestamp for EX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for EX64.SYS
Probably caused by : Unknown_Image ( nt!ExDeferredFreePool+100 )
Debug session time: Sun Dec  9 15:02:04.644 2012 (UTC + 6:00)
System Uptime: 0 days 0:07:57.472
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x00000019: BAD_POOL_HEADER  

Usual causes:  Device driver
BugCheck 19, {3, fffff8a00c0d7bf0, fffff8a0048e4bf0, fffff8a0048e4bf0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Debug session time: Mon Dec 10 07:27:40.909 2012 (UTC + 6:00)
System Uptime: 0 days 0:03:57.126
PROCESS_NAME:  plugin-contain
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000001A: MEMORY_MANAGEMENT  

Usual causes:  Device driver, memory, kernel
BugCheck 1A, {41790, fffffa80031b9bd0, ffff, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Debug session time: Sun Dec  9 15:45:16.725 2012 (UTC + 6:00)
System Uptime: 0 days 0:23:30.553
PROCESS_NAME:  Skype.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 

Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff960000e54a4, fffff8800887bf50, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Unable to open image file: C:\ProgramData\dbg\sym\win32k.sys\4D2415EA311000\win32k.sys
The system cannot find the file specified.
Probably caused by : Unknown_Image ( win32k+c54a4 )
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e5be90
Debug session time: Mon Dec 10 08:05:52.607 2012 (UTC + 6:00)
PROCESS_NAME:  Skype.exe

KillianB · 10 Dec 2012

Thank you, most of my BSOD browsing brought me here and I saw how helpful the community was. Figured I'd pitch my error here and hope someone knew. Glad to get a reply haha.

- Norton removed, no BSOD's or any issue yet.

- MSE and Malware Bytes installed, both full complete scans, came up clean.

- Edited system spec's the rest I'll have to update in the morning, it's late and niece and nephew live with me and don't want to rattle around and wake them (though the bits you probably require are there).

- System file checker ran, about to restart to complete.

- Crystal Disk screenshot as per request:
Attachment 245056

- Speccy Summary screenshot as per request:
Attachment 245057

- Seagate HD so I ran Sea Tools, all scans. Came up clean no errors and not failing, good shape.

- About to burn the Memtest ISO to disk and run it as per requested, will post back results.

koolkat77 · 10 Dec 2012

Thanks, looks good.

Await the news from memtest.

Notice the motherboard temperature's a lil high. Clear any accumulated dust from inside the case.

KillianB · 11 Dec 2012

koolkat77 said:

Thanks, looks good.

Await the news from memtest.

Notice the motherboard temperature's a lil high. Clear any accumulated dust from inside the case.

There were so many errors it was ridiculous when testing both sticks. I'm a bit embarrassed to even say.

Made it to 'Test #8' with around 595k errors and zero passes. Should I remove a stick and test each stick separately? I'm no expert but seems from that huge number and everything I read on Memtest, my RAM or Motherboard is shot. What is my next step?

koolkat77 · 11 Dec 2012

Yes you should test them individually for at least 3 passes in different slots to make sure it's the RAM and not the RAM slot.

OR

If you do not want to test with memtest, just insert one stick and use the computer for a while (in different slots too), see if it crashes/BSOD-s or anything. Then do the same thing with the other stick.

KillianB · 11 Dec 2012

I'll just run the Memtest per stick, and report back. It'll be faster and more confirmed so to speak. I'm very glad I came to this forum, even though I'm not done yet thank you very much for your help I thought I was at a brick wall.

koolkat77 · 11 Dec 2012

Take your time & No problem.
We're glad to help :)

KillianB · 14 Dec 2012

Well, I found out the next day after making that post. Turns out it was just a bad stick. It's funny how simple the issue was yet how many issues it caused and how miserable it made my life when it came to gaming. Thank you Kat! :)