8.1 blue screen on fresh OS

i barely have anything installed on this machine. mostly windows updates and drivers. i counted 7 applications that i installed myself. i was hoping for a headache free experience on a fresh OS but i just got my first blue screen after a few days of loading windows. i usually just ignore them cause they don't happen to often but i have had enough of the blue screens and i want to figure out what is causing them. i have attached my W7F scan. thanks for the help.



Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003c3a661, fffff88004f054d8, fffff88004f04d10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4d )

Followup: MachineOwner
Hi MisterDean,
the above Bugcheck can be caused by hardware faults (usually graphics), drivers, no free space on the HDD or very little and Bios incompatibilities. The dump file also shows that the reason for the bsod was that data held in the memory (probably Video memory in this instance) couldn't be read because either the data or the memory was corrupt.
I can also see from the Stack Text (a kind of blow by blow account of the last routines before the crash) that Vdimm is mentioned a few times.
This could simply be down to a corrupt driver but let's test your Vram.
Run the app found here:

You could also try changing GPU drivers.

Can you post what PSU you have please including make and model.

i ran the full test, no errors. using 1000w EVGA super nova.


Windows Forum Admin
Staff member
Premium Supporter
Ok, good.
I went and had a look over your drivers and some are in need of updating.

Please run the Intel driver update utility as it seems your missing one or two drivers:

Your motherboard support page is here:

If you have had this bsod for a long period of time despite fresh installs then it might be worth testing your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Also if you have anymore dump files that would really help too.

i doubt the problem is hardware. everything was bought brand new and the computer runs fine 99% of the time. i have a feeling the problem is software related. when i check the device manager there are no question marks saying a driver is missing. how do i give you dump files?

i ran that intel driver program and it did not show any drivers that needed to be updated. i also ran the windows memory test and no errors were found.


Windows Forum Admin
Staff member
Premium Supporter
i doubt the problem is hardware. everything was bought brand new and the computer runs fine 99% of the time. i have a feeling the problem is software related. when i check the device manager there are no question marks saying a driver is missing. how do i give you dump files?
Just because hardware is new doesn't mean it can't be faulty.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
As I mentioned above windows memory app just doesn't cut it. You need to run memtest86 as outlined above. I also notice you have bios updates available too so you may want to consider updating.

Dump files are created when a machine blue screens. You can find them in a folder marked minidump which is in the main windows folder. The more we can see the better as having just one doesn't always show the whole picture.

I see your running an SSD. Is the firmware fully updated?

this is true, but the odds of faulty equipment when bought new is slim.

the windows memory test works just fine. memtest86 is just more rigorous. i ran that too and it found no errors.

the SSD firmware is up to date. i just updated the motherboard bios.

i have attached my dump file.



Windows Forum Admin
Staff member
Premium Supporter
Dump file was exactly the same.
The chances of new hardware being faulty when bought is slim your right but that still doesn't mean to say yours isn't faulty.
Windows memory test is simply not up to the job otherwise we would recommend using it. Testing memory isn't as cut and dried as you seem to think. I've even seen cases where the memory despite passing the Windows and Memtest86 tests was still bad. .
How long did you run memtest86 for? As I pointed out above it needs at least 12hrs as some errors won't appear until at least that length of time as passed.

Can you try the gpu in a different machine?

Obviously it's entirely up to you whether you follow my advice or not.

Bug Check 0x7E

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include the following:

  • 0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.

  • 0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

  • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
For a complete list of exception codes, see the Ntstatus.h file that is located in the inc directory of the Microsoft Windows Driver Kit (WDK).

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.

  • Make sure you have enough disk space.

  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

  • Try changing video adapters.

  • Check with your hardware vendor for any BIOS updates.

  • Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.

If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame supplies additional information.

If you do not know the specific cause of the exception, consider the following issues:

  • Hardware incompatibility. Make sure that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at theWindows 7 Compatibility Center.

  • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.

i ran memtest86 for 2 passes. that and the windows memory test is sufficient for me. by your own admission even memtest86 doesn't always sniff out bad ram so it's not gonna tell me anything without a doubt. i was hoping somebody who understood the dump files would be able to say with certainty what is causing the blue screen. but it appears this is not the case and it's just a guessing game. unless you have any other suggestions i guess i will just have to accept blue screens and windows are a package deal.

thanks for the help.


Windows Forum Admin
Staff member
Premium Supporter
Troubleshooting an issue even using dump files isn't always a cut and dried process. You only have to look through the history of some of the threads in this section to see that it can sometimes take up to 3 pages of dialogue before a solution is reached.

As I can see you do not have much faith in my abilities to help you then it's probably best we stop here.

If won't believe me then pop over here:

They'll probably tell you the same thing but see how you go..

don't make assumptions about what other people think. i know you have more knowledge than myself when it comes to reading dump files and i do appreciate your effort. but to be honest i have been down this road too many times. every since i started messing with computers all the way back to windows XP there have been blue screens. that's years and years of blue screens and dozens of individual hardware components. i would not be surprised if there was faulty hardware in a few of them, but not all of them. based on my own experiences i am more inclined to believe most windows problems are software related. i have also reached out for help in other forums in the past and i have noticed a tread that people ALWAYS suspect hardware. if they don't think it's the memory they think it's the GPU. if they don't think it's the GPU they think it's the PSU. i have done my due diligence with memtest86, furmark, intel burn test, and many other stress tests and i have never found any hardware errors. i have tried testing with other parts and even built entire new computers from scratch just to beat the blue screens. i am starting to believe blue screens and windows go hand and hand and i don't think we will ever truly be rid of them. if you have any other suggestions i am all ears. but if the only advice i'm going to get is drivers stress tests and swap parts i don't really need help with that cause i have plenty of experience with that stuff. like i said i was hoping somebody could read through the logs and tell me without a doubt what is causing the blue screen but i guess it does not work like that.

Last edited:


Windows Forum Admin
Staff member
Premium Supporter
All I can tell you is what the Dump file is telling me.

If it had mentioned software of any type I'd have said so.

The only reason I asked you to do the scan is because of what the dump file is saying not because I 'instantly think it's hardware'.

Look I know running these scans are a ball ache but troubleshooting generally is and often one troubleshoots just so something can be ruled out.

Have you had any further bsod's since updating the bios as this is one of the main causes for that bugcheck?

i understand your position. it's a shame windows has not advanced enough to the point where it can pinpoint the problem.

i recently had the check engine light come on my BMW. i assumed oxygen sensor cause every car i owned that had the check engine light it was the oxygen sensor. i recently found out autozone will scan the computer for free so i had that done. sure enough it was throwing up oxygen sensor codes. i called around and everybody said the same thing. it's probably the oxygen sensor, but there is a chance the sensor is fine and something else is causing the sensor codes. so now that i had my dump file read i feel like i'm in the same position with my computer. all somebody can do is read the codes but that still does not always tell you what is causing the problem.

i have not had any more BSOD or any other problems. my computer functions as expected but every now and then i get that random BSOD and i just got fed up with it so i decided to see if somebody could make sense of these dump files.


Windows Forum Admin
Staff member
Premium Supporter
Agreed.. :)

I guess the best thing to do then perhaps, especially if you've not had a bsod since updating, is if you do have another bsod please post it and we'll have another look?

i probably won't have another for quite some time. they don't pop up often. i usually see one after 4-6 weeks. but i will keep your offer in mind when it decides to happen again.

BTW, i suspect a program i'm using might be causing the blue screens. it's called bluestacks. i've noticed it's performance is rather questionable. when i start the program it doesn't always start. it just hangs at the loading screen. this happens often and i noticed my bluescreens usually happen when i'm using this program. i also noticed even after i close the program there are processes related to it still running in the task manager. after a bluescreen when i look in the event viewer there are critical errors listed with this program. but i'm not sure if the program is causing the bluescreen or the bluescreen is causing the system to throw up errors in the logs.

any thoughts?

i also have 5 processes related to this program running at startup which really pisses me off. i check the task manager to see if i can disable this program from starting with windows but it's not listed in the task manager. i checked the services that start when my computer starts and it is shown in the services page. i disabled everything related to this program in the services page but this stupid program still has processes running at startup.

any other ideas how i can prevent this program from starting with my computer?

Last edited:


Windows Forum Admin
Staff member
Premium Supporter
I wish you'd have brought this up earlier lol.. Weirdly neither did i see it in the dump file. I did a check on Bluestacks using the windows compatibility page for Windows 8. The results were varied meaning that some users had posted it was compatible and some had not.
http://www.microsoft.com/en-gb/windows/compatibility/CompatCenter/ProductDetailsViewer?Name=BlueStacks App Player&vendor=BlueStacks&Locale=1033,2057,3081,4105,16393&ModelOrVersion=0&BreadCrumbPath=bluestacks app player&LastSearchTerm=bluestacks+app+player&Type=Software&tempOsid=Windows 8.1
As you can see more found it compatible than not. I would hazard that if you feel your getting issues with it you may fall into the latter group.

This 'How to' will give you a couple of way's to stop it from starting up:

Let me know if these are unsuccessful.

i wanted to hear what other people had to say about the dump file before i suggested this program might be causing problems.

thanks for the information. i will post another dump file when i get another bluescreen.

have a good weekend.


Windows Forum Admin
Staff member
Premium Supporter
Sounds good MisterDean. Have a great weekend yourself.. :)

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.