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.


BSOD Windows 7 blue screen.

  • Please log in to reply
2 replies to this topic

#1 Miracle11


  • Members
  • 9 posts

Posted 23 May 2016 - 01:04 PM

Dell Inspiron N4110 ,

Intel Core i5-2450M CPU @2.5Ghz

6 GB ram

64 bit OS


My problem is this , every time i turn it on the screen suddenly goes grey and then the blue screen appears. I have tried disabling services 1st all non windows , next all (including windows services). I have no recovery options as there is no recovery point. Can someone help me solve this problem?


p/s I couldnt run the 'perfmon/report' in command prompt , it says error in generating report ...


Attached Files

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:02 PM

Posted 23 May 2016 - 06:38 PM

Please keep your posts in one topic.  It gets confusing if different people are giving advice in different topics.

You can PM a moderator and have them merge the topics together.

The other topic is here:  http://www.bleepingcomputer.com/forums/t/615168/windows-7-blue-screen-no-recovery-point/


Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

C: drive only has about 12% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

These devices have problems in Device Manager:


Security Processor Loader Driver    ROOT\LEGACY_SPLDR\0000    This device is not present, is not working properly, or does not have all its drivers installed.
facap, FastAccess Video Capture    ROOT\IMAGE\0000    This device is disabled.

The first device is a Windows device that needs updating.  Please get ALL available Windows Updates

The second device should be enabled.  Then update it's drivers.  If you'd like, feel free to disable it again once the drivers are updated.


The WER section of MSINFO32 reports many, many instances of a service hang in WdiSystemHost.
There appears to be some custom error reporting software on the system.  Is it functioning properly?


The memory dumps are mostly related to your video.

Please follow these troubleshooting suggestions:  http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/35-video-tdr-timeout-0x116-0x117.html#post29532
Also, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html


Out of 9 memory dumps there were 5 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).


In short, it's possible that there's a hardware problem here - and I'd start by suspecting the video card.
Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Start with the video tests first and let us know the results.


The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:


**************************Mon May 23 15:42:09.092 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\052416-24133-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
System Uptime:0 days 0:00:40.341
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :atikmpag.sys ( atikmpag+7408 )
BugCheck 116, {fffffa8009a55010, fffff88004491408, 0, 2}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Arg1: fffffa8009a55010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004491408, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.


3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon May 23 15:42:09.092 2016 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
gdmwmprt.sys                Mon Aug 17 01:02:58 2009 (4A88E482)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
gdmuwm.sys                  Thu Nov 12 23:17:30 2009 (4AFCDDDA)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
btath_rcp.sys               Thu Jun 24 02:17:21 2010 (4C22F871)
btath_flt.sys               Thu Jun 24 02:17:38 2010 (4C22F882)
btath_hcrp.sys              Tue Jun 29 05:30:43 2010 (4C29BD43)
btath_lwflt.sys             Mon Sep 13 04:26:54 2010 (4C8DE04E)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
TurboB.sys                  Mon Nov 29 18:02:31 2010 (4CF43107)
Rt64win7.sys                Tue Nov 30 01:01:28 2010 (4CF49338)
iaStor.sys                  Wed Jan 12 20:50:12 2011 (4D2E5A54)
CtClsFlt.sys                Wed Jan 19 22:20:46 2011 (4D37AA0E)
nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)
btath_a2dp.sys              Mon Feb 14 20:47:47 2011 (4D59DB43)
btath_bus.sys               Fri Apr  8 05:19:05 2011 (4D9ED309)
igdpmd64.sys                Sun Apr 10 14:50:59 2011 (4DA1FC13)
RTKVHD64.sys                Tue Apr 19 06:16:52 2011 (4DAD6114)
athrx.sys                   Thu Apr 21 23:17:08 2011 (4DB0F334)
SynTP.sys                   Fri Apr 22 20:20:25 2011 (4DB21B49)
atikmpag.sys                Wed May 11 22:16:52 2011 (4DCB4314)
atikmdag.sys                Wed May 11 23:08:42 2011 (4DCB4F3A)
btfilter.sys                Wed May 18 06:17:38 2011 (4DD39CC2)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
360Camera64.sys             Fri Mar  7 05:29:56 2014 (53199FA4)
360Box64.sys                Wed Sep  2 03:26:02 2015 (55E6A48A)
360FsFlt.sys                Thu Sep 10 05:27:31 2015 (55F14D03)
360AntiHacker64.sys         Sun Nov  8 22:06:04 2015 (56400D9C)
BAPIDRV64.sys               Tue Dec  1 06:04:56 2015 (565D7ED8)
**************************Mon May 23 14:58:24.178 2016 (UTC - 4:00)**************************
Sftvollh.sys                Fri Sep 30 12:42:46 2011 (4E85F186)
**************************Mon May 23 10:03:19.464 2016 (UTC - 4:00)**************************
idmwfp.sys                  Thu Jun 14 09:50:36 2012 (4FD9EC2C)

gdmwmprt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
gdmuwm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

Edited by usasma, 23 May 2016 - 06:39 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Miracle11

  • Topic Starter

  • Members
  • 9 posts

Posted 24 May 2016 - 12:33 AM

I solved the problem , unintalled amd driver and reinstalling it. Then i dleted setting msconfig.. thank you.. will be clearing the hard disk for space
I solved the problem , unintalled amd driver and reinstalling it. Then i dleted setting msconfig.. thank you.. will be clearing the hard disk for space

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users