BSOD at Random times. Locale ID 1033 BCCode 3B

[itsJustThomasHD]

First let me start off with saying good afternoon to the members of the seven forums, today i'm here to ask you for some advice and help regarding my custom built gaming computer. Up until a few weeks ago my computer was running perfectly then all of a sudden the screen started flickering while playing a few games. Now the flicker didn't happen all the time or constantly but it would happen in certain areas and for a short time, so i replaced the monitor figuring it was going bad. Now i keep getting a bsod at random times with the local id 1033. My friend and my gut says my graphics card is on it's last leg which if this is true it kinda ticks me off since this card is only about 4 months old.

Anyways i did some pre-emptive reading on this site and used the grab tool to get my information, anything about my pc you want to know should be on my profile or wherever it saved when i had to enter all of it when i registered. I'd be happy if ya'll can help me resolve this problem as gaming is a big part of my life.

Here's the folder with all the information that the tool gave me.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff960001963c5, fffff88003a66f30, 0}

Probably caused by : win32k.sys ( win32k!HANDLELOCK::vLockHandle+51 )

2: kd> [COLOR="SeaGreen"]!error 00000000c0000005[/COLOR]
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

It seems to be most likely drivers referencing invalid memory addresses, which are either have some form of protection bit on them or MMU can't physically translate the page.

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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Please upload your MSINFO32 file too:

1. Start rb:
2. Type: msinfo32
3. File, Save
4. Place into a zipped folder
5. Upload in your next post with http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[itsJustThomasHD]

Please delete this post if a administrator may do so.

 

[itsJustThomasHD]

Alright i hate to double post/bump a topic but i wanted to state that i have done a few tests and nothing has come back conclusive for me. I've ran a memtest program and nothing had a problem, tried memtest86 but wasn't sure how to use it and i ran the verifier that didn't do a single thing except slow the computer down and cause crackling in the speakers. Oddly enough however i have not had a BSoD since i started the verifier test, yet. Anyways i'm uploading the MSINFO32 file now in zip format and then if i get another BSoD i will post the new dump files.

Edit: Also talked to a friend this afternoon who "claims" to be great when it comes to errors and he said it sounds like the memory on my gpu is failing or my single 8gb stick of ram. I think it was a gimmick to get me to buy them from him since he's also a part time pc parts salesman.

I'm eagerly awaiting a response seeing as this computer is my lively hood at the moment and i need to know what i can do to solve these problems. If i do need a new GPU then it won't be a problem, however i do want to ask if a radeon gpu would be better for my pc then a nvidia card.

 

[x BlueRobot]

Driver Verifier may not necessarily create a BSOD straight away, how long has Driver Verifier been running for?

I wouldn't say it is a hardware issue as of yet.

 

[itsJustThomasHD]

Driver Verifier may not necessarily create a BSOD straight away, how long has Driver Verifier been running for?

I wouldn't say it is a hardware issue as of yet.

Well blue it's been running since you told me to run it yesterday and i've still got it going as we speak, as a matter of a fact since it's been running i have not had a bsod. (Knocks on wood) I do know that a week or so ago i installed the latest drivers for the gpu due to the screen flicker thinking it would help but i quickly found out that th 320 drivers were faulty so i went back to the 301 drivers. It bsod'ed a bit but i guess i didn't get rid of the remnants of the 320 files.

 

[x BlueRobot]

You may have to enable the Special Pool option if it doesn't crash, and then enable Driver Verifier again for a further 24 hours.

So, in order to do so:

• Start rb:
• Open a elevated command prompt
• Type: verifier /reset
• Follow Driver Verifier tutorial again (see below for changes)
• Select Individual Settings
• Enable all the options; do not select Low Resources Simulation.
• Follow the rest of the Driver Verifier tutorial normally