BSOD using NetBeans with different errors

[D3R1CK]

I started to get BSOD recently when using NetBeans (7.1 and 7.1.1),
both end up the same way.

I'm using netbeans with PHP only.

No BSOD if playing game (tested COD MW3), or using any other applications (photoshop, 3DS, autocad etc)

I will appreciate any help with this issue.

----------------------------------------------------------------------------
My spec:
Processor: AMD Phenom II X6 1100T
RAM: 16GB DDR3
MB: M4A79XTD EVO
VIDEO: ATI FirePro v4800
PSU: 450W
Sound and network: onboard
----------------------------------------------------------------------------

I'll run memtest later and post the results when it finish or get errors.

If someone could take a look in the attached files (followed the instructions),
and report any clue of what is going on, will be a great help.

Thanx in advance for any help with this.

Cheers!

 

[zigzag3143]

Several of the newer crashes were related to ExpressVPN causing a memory exception. Errors are all over the map so I would suggest both memtest (probably a driver though) and driver verifier.


These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[D3R1CK]

Hi zigzag3143, thank you very much for your reply and advices.

My apologies for the delayed reply.

I just did mem test last nigh (GMT+8:00 here), and got several errors, so I guess have nothing else that I could do right?

By the way, the memory is G. Skill F3-12800CL9D-8GBXL (x2 = 16GB), and I bought it around 8 months ago, but the BSODs started only a couple of weeks ago.

I took a picture of the mem test report and have attached it to the post,
please take a look if you think it is important.

Cheers!

 

[zigzag3143]

Just remember that memtest tests both the ram and the mobo slot it is in. YOu may want to test each mobo slot with a known good stick of ram to see if it is the mobo slot.