Windows 10: First BSOD ever in Win10 x64. "Reference by pointer"

I just had the very first BSOD ever in Win10 x64. "Reference by pointer". *Sad
I was playing "Heroes and Generals", a which is a webbased game, using Chrome. No other app, just Chrome with Whatsappweb, Facebook and Google Calendar.
Here i send the Zip generated by the DM log collector.

:)

 

my phone " keys in " some numbers while talking

As I said in my first post you can either try to update it's software to see if it cures it.

If it doesn't then your phone is faulty and you will need to get it repaired.

 

BSOD "Reference By Pointer" - Minidump File

Hi,

Thank you for posting your query in Microsoft Community.

I understand your concern, can you provide us the specification of the computer?

Sometimes new hardware can cause blue screen errors. If you recently added new hardware to your PC, shut down your PC, unplug the new hardware, and then restart your PC. Many blue screen errors can be resolved by making sure that Windows is up to date.
In the search box on the taskbar, enter Windows Update, select
Windows Update. On the Windows Update page, select Check for updates.

Troubleshoot blue screen errors

http://windows.microsoft.com/en-in/windows-10/troubleshoot-blue-screen-errors

Let us know how it goes, we’ll be glad to assist you.

 

I will debug this and attempt to find an answer.

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

Okay, first of all: Your PC has almost been on 11 and a half days. You should reboot your PC once in a while to prevent/fix problems like memory leakage.

Okay so the error you encountered when you PC crashed was WIN8_DRIVER_FAULT, am I wrong? Probably not.

Since it's a WIN8_DRIVER_FAULT, we can assume it's a software issue. I will look further into the file because there is no obvious file shown other than hng.exe, which is Heros and Generals itself.

 

You need to get rid of all the pirated software first.

Rules

 

Nop, it was a "Reference by pointer"

 

Oh. When I debugged the .dmp file that's the reason I found.

 

mmm, weird, the reason i'm telling you is the one i saw in the BSOD

 

They are both in there,

Code: REFERENCE_BY_POINTER (18)Arguments: Arg1: 0000000000000000, Object type of the object whose reference count is being lowered Arg2: ffffe0018bd67060, Object whose reference count is being lowered Arg3: 0000000000000002, Reserved Arg4: ffffffffffffffff, Reserved The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object. When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This bugcheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles. It may also occur when the object’s reference count drops below zero whether or not there are open handles to the object, and in that case the fourth parameter contains the actual value of the pointer references count. Debugging Details:[/quote] Code: CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x18 PROCESS_NAME: hng.exe[/quote] And I repeat,

Rules