BSOD playing Minecraft

Okay that's good to know :)

My games keep crashing and freezing now but no BSOD

This crash (minecraft, shutting down like it initially did before I started having BSOD come up) left details to why it crashed in a document on my desktop, I've attached it below.

It seems that Java detected a ACCESS_VIOLATION (0xc0000005), this is usually caused by drivers referencing invalid memory addresses and accessing memory beyond pool allocation.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

What do you use Java for? Java has many security flaws and security vulnerabilities.

x BlueRobot said:

What do you use Java for? Java has many security flaws and security vulnerabilities.

Mainly minecraft, but I had my computer up and left for a few hours, came back just now to find out I blue screened sometime while I was out. Im going to run the driver verifier now.

Please upload the new BSOD, and have you updated the Java to the latest version? There will a update tomorrow I believe, which is designed to fix 40 different security flaws found in Java.

I would recommend disabling Java in your browser if it's not needed for any webpages or plugins you visit/use:

• How do I disable Java in my web browser?

Java is at the newest update, yes. And do you mean the dump file? Or the thing I had to do at the start with the diagnostics tool? I'll attach both.

Code:

BugCheck C9, {23b, fffff88006b7b710, fffffa80092ea820, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

Interesting, it seems Windows reported a Driver Verifier initialized error, when Driver Verifier wasn't even running.

Run Driver Verifier, and then report back the results. Upload a new BSOD if it occurs.

Alrighty, new BSOD uploaded

It seems to be the same BSOD as before for some reason

Keep Driver Verifier running, and then post a few BSODs.

Open a elevated command prompt, and then enter this command:

Code:

verifier /query

Post the results of the command.

If the command mentions something like, no drivers or settings are being verified, then Driver Verifier isn't running.