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.


Black Screen in Windows 10

  • Please log in to reply
1 reply to this topic

#1 trevzilla


  • Members
  • 116 posts
  • Local time:01:52 AM

Posted 26 August 2015 - 09:47 AM



I've searched a bit for this problem, but I seem to only come up with results pertaining to a different type of black screen crash in windows 10.


My problem is this: Very randomly - about once a day (sometimes less) my computer will be working just fine, then all of a sudden the screens will go black. As in No signal black. My keyboard freezes up (the num lock light ceases to flash when I press num lock) but the music I was playing continues to play. I usually stream online radio, and it continues to play...(I've been meaning to check if it will play the next song or not...but I haven't gotten there yet so it might just be playing whatever was buffered.)


Regardless after this happens my only option seems to be doing a hard reset. After I've done that once the computer seems to run just fine for the remainder of the day.


It usually happens while I'm working on the computer, but every now and then I'll come back to the computer after I've left it on for a while, and it won't wake up. Whether or not this is the same issue, I don't know, but thought it might be relevent.


I used to get a blue screen every now and then, but currently it's not happening anymore. It seems like with these crashes a dump file is not created. However attached is the only dump file that is in my minidump folder. Again, whether this is relevent info or not, I don't know.


Any help out there? Thanks in advance! :)

Attached Files

BC AdBot (Login to Remove)


#2 blueelvis


    Bleep Blop Bleep

  • Malware Response Team
  • 1,666 posts
  • Gender:Male
  • Location:India
  • Local time:01:22 PM

Posted 27 August 2015 - 04:13 PM

Hi Trevzilla ^_^,

I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-

**************************Tue Aug 18 08:53:25.906 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\081715-67531-01.dmp]
Windows 8 Kernel Version 10240 MP (2 procs) Free x64
Built by: 10240.16430.amd64fre.th1.150807-2049
System Uptime: 0 days 12:26:25.363
*** WARNING: Unable to verify timestamp for win32kbase.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kbase.sys
Probably caused by : win32kbase.sys ( win32kbase+cc954 )
BugCheck 109, {a3a01f59d0a8b535, b3b72be0232a6aa0, fffff9607805c954, c}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000109]CRITICAL_STRUCTURE_CORRUPTION (109)[/url]
Arg1: a3a01f59d0a8b535, Reserved
Arg2: b3b72be0232a6aa0, Reserved
Arg3: fffff9607805c954, Failure type dependent information
Arg4: 000000000000000c, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification
PROCESS_NAME:  csrss.exe
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3000
  BIOS Version                  ASUS P5N-D ACPI BIOS Revision 1401
  BIOS Release Date             06/21/2010
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK Computer INC.
  Product Name                  System Product Name
  Baseboard Product             P5N-D

The bugcheck has got very less information (The parameters do not match what we have). Below is a list of 3rd party drivers present on your system -

**************************Tue Aug 18 08:53:25.906 2015 (UTC + 5:30)**************************
wdcsam64.sys                Wed Apr 16 14:09:08 2008 (4805BB2C)
LVUSBS64.sys                Sat Jul 26 20:36:36 2008 (488B3D7C)
nvmf6264.sys                Thu Apr 21 04:19:36 2011 (4DAF6300)
ASACPI.sys                  Fri Nov  2 07:24:34 2012 (509327DA)
nvstor.sys                  Tue Apr 22 00:04:03 2014 (5355649B)
avgdiska.sys                Wed Mar 11 15:46:03 2015 (550015E3)
avgrkx64.sys                Fri Mar 20 15:48:15 2015 (550BF3E7)
nvhda64v.sys                Fri Apr 17 00:33:16 2015 (55300774)
athwnx.sys                  Mon Apr 27 08:26:55 2015 (553DA577)
avgloga.sys                 Thu May  7 17:20:17 2015 (554B5179)
avgidsha.sys                Tue May 12 18:06:49 2015 (5551F3E1)
RTKVHD64.sys                Tue Jun 16 16:25:05 2015 (55800089)
avgldx64.sys                Tue Jun 16 19:24:55 2015 (55802AAF)
nvvad64v.sys                Thu Jul  2 07:42:51 2015 (55949E23)
avgwfpa.sys                 Wed Jul  8 18:33:20 2015 (559D1F98)
intelppm.sys                Fri Jul 10 08:42:59 2015 (559F383B)
NvStreamKms.sys             Fri Jul 17 07:13:42 2015 (55A85DCE)
avgmfx64.sys                Tue Jul 28 14:31:32 2015 (55B744EC)
avgidsdrivera.sys           Tue Jul 28 14:32:07 2015 (55B7450F)
nvlddmkm.sys                Fri Aug  7 08:49:41 2015 (55C423CD)


Kindly follow the below instructions -

  1. I checked ASUS support and I found one question regarding weird display on Windows 10. Kindly give it a try and see if it resolves your problem or not - https://www.asus.com/support/FAQ/1013130/
  2. Kindly remove the driver wdcsam64.sys since it is very famous for causing problems like BSODs. Just do a system wide manual search of the system and then rename this driver. Once you have renamed this, reboot the system and see if a new driver which has the same name (wdcsam64.sys) is generated or not. If it is generated, let me know.
  3. According to the Dump file, there is ONE Bit Memory Corruption. This is generally caused by faulty RAM. I would suggest you to test the RAM using the Memtest according to **THIS** guide (Thanks usasma!)
  4. Furthermore, I see that the BIOS is dated to 2010 so there is a high chance that Windows 10 is not supported on your system.
  5. With your next post, kindly follow the BSOD Instructions according to this **LINK**. It contains valuable information which helps us a lot.



Let me know how it goes ^_^




Member of the Bleeping Computer A.I.I. early response team!

In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users