Sign in with
Sign up | Sign in
Your question

BSOD Problem, Finally Asking For Help

Last response: in Windows 7
Share
April 2, 2012 6:04:18 AM

I've been getting BSODs for months now, and I try to ignore them, thinking in the back of my head I'll finally get an SSD and reinstall Windows to eliminate the problem. Anyways, just recently I was sobbing over my weak GPU (6950 2GB) and was going to check my PC ratings in the W.E.I. and noticed it needed to be refreshed. I could not refresh it without getting a BSOD. This happened 3 times, so I'm asking for help.







As you can see, the 3 from 4/1/2012 are the crashes from trying to refresh W.E.I.

All the others are just random ones I get for no reason known to me. :/ 

The last picture is from a while ago so I just added it in.

More about : bsod problem finally

April 2, 2012 6:22:21 AM

The most important Blue Screen of Death troubleshooting step you can take is to ask yourself what you just did.

1) Did you just install a new program or a piece of hardware, update a driver, install an update, etc.? If so,

there's a very good chance that the change you made caused the BSOD:
Startup using Last Known Good Configuration to undo recent registry and driver changes.
Use System Restore to undo recent system changes.
Roll Back device driver to version prior to your driver update.

2) Scan your computer for viruses. Some viruses can cause a Blue Screen of Death, especially ones that infect the master boot record (MBR) or boot sector.

3) Update drivers for your hardware. Most Blue Screens of Death are hardware or driver related so updated drivers could fix the cause of the STOP error.

4) Return hardware settings to default in Device Manager. Unless you have a specific reason to do so, the system resources that an individual piece of hardware is configured to use in Device Manager should be set to default.

Non-default hardware settings have been known to cause a Blue Screen of Death.

5) Return BIOS settings to their default levels. An overclocked or misconfigured BIOS can cause all sorts of random issues, including BSODs.
m
0
l
a b $ Windows 7
April 2, 2012 12:23:04 PM

Based on the errors, I'd suspect RAM as all those BSOD's tend to occur due to RAM getting corrupted. Run memtest86/Prime95 on each stick of RAM and make sure they all pass both without errors.
m
0
l
Related resources
a b $ Windows 7
April 2, 2012 12:35:05 PM

0x0000003b error. This issue occurs because of an error in the Microsoft IEEE 1394 driver stack, in which the buffer that is allocated to the driver stack does not initialize correctly.
in other words your firewire buffer is causing issues.... go into bios and disable 1394 firewire support...

http://support.microsoft.com/kb/980932 try here for a hotfix. you may not need it as its o.s/service pack dependent.
m
0
l
April 2, 2012 1:28:16 PM

I have tried to roll back my system to the earliest I could at one point. It didn't work, as I still received BSOD's. As for the RAM, I did buy 2 additional sticks off of eBay and add those to my case to reach 8GBs, and I couldn't tell you if that is the problem, they have been in there for a while now.

I had also tried uninstalling hardware I deemed as new. But at this point, I'm so far into these BSODs that I have no idea what could be causing it.

I'd still like to know why the test fails to rate W.E.I. though.

As for the Hotfix my HEXiT, I couldn't seem to find any link to download anything on that Microsoft website you linked.

m
0
l
April 2, 2012 2:11:57 PM

Obviously W.E.I. triggers the problem and does not finish the test. As for it needing refresh, the additional RAM is certainly one reason.
But really, download memtest86 iso, burn it and boot it. Let it run for a while (at least 1 pass, but others sugest a few hours). If no errors appear, then memory should be ok. I've had 1 error bit on every "cold" system (1st boot after half-day off) which memtest confirmed.
m
0
l
a b $ Windows 7
April 2, 2012 2:36:32 PM

Run Memtest 86+ overnight to see oi memory is the issue. Are the RAM modules mixed specs, mixed brands .... some brands in my experience are better at "playing with others"

http://www.memtest.org/
m
0
l
April 2, 2012 2:39:12 PM

@xxxbobbyfinxxx dude that is Ram issue, I seen those codes more then enough times before to point at that, my second hunch is driver related either a corrupted USB or Firewire driver. Remove all hardware except what is needed to boot the system. leave one stick of ram in and run memtest and prime95 as other have stated, then put in other stick. Do you have any spare ram around? that would help determine it.
m
0
l
April 2, 2012 3:39:42 PM

After I got the RAM I refeshed Windows though, and I do remember taking the two new sticks off and still getting Blue Screens.

If I get the errors with the two new sticks of ram taken out then it's clearly something else right?
m
0
l
April 2, 2012 4:03:28 PM

RAM is a very likely culprit - possible that you have 2 bad sticks or a compatibility issue.

I have also experienced power supply issues causing BSD's as well. Power supplies can an do go out after working great for years. One of the best investments I ever made was getting a power supply tester. For around $15 this little gadget has saved me numerous time on troubleshooting issues.

I concur with the prior comments about the usb/firewire issue. Go into your bios and disable all functions that you are not using - like raid, firewire, network ports.
m
0
l
April 2, 2012 4:07:57 PM

I have the extreme3gen3 motherboard, so if you guys can give me a heads up as to disabling those ports, that would be cool. Also, I think it's stupid how I have to disable stuff to get my computer to work as a solution. You should never have to do that. Just because I don't use it doesn't mean I should turn it off. Plus, does W.E.I. Test the USB ports? How would that crash my computer wen I go to refresh.

So many questions. Gah computers!
m
0
l
a b $ Windows 7
April 2, 2012 7:32:38 PM

I'm saying again: ITS RAM. All four of the error messages are messages I'd expect from a damaged RAM module, and the four of them combined basically rule out any other cause.

Run memtest86/Prime95 and find the bad stick and replace it.
m
0
l
April 2, 2012 9:03:41 PM

Well I'm an hour into Memtest and it's passed the first one, so I'm starting to doubt it is the memory.
m
0
l
April 3, 2012 2:34:56 AM

gamerk316 said:
I'm saying again: ITS RAM. All four of the error messages are messages I'd expect from a damaged RAM module, and the four of them combined basically rule out any other cause.

Run memtest86/Prime95 and find the bad stick and replace it.




Still convinced it's RAM? Just because I got it off eBay doesn't mean it's the problem.
m
0
l
April 3, 2012 2:43:27 AM

So I found out that I get the BSOD when W.E.I. is on "Assembling Windows Media Decoder Performance"...

I hope that helps.
m
0
l
April 3, 2012 7:07:31 AM

First of all you need to update all yor drivers and install all windows updates from
windows update and scan your computer for virusis!
And i also suggest you to run CMD as administrator and write in cmd sfc/scannow
And after that in CMD run chkdsk /f and then chkdsk /r you will need to scan it on next
reboot so press Y!
m
0
l
April 3, 2012 7:47:57 AM

What about doing a 'repair' installation of Windows? That usually fixes problems like this one ...
m
0
l
a b $ Windows 7
April 3, 2012 12:48:40 PM

xxbobbyfinxx said:
http://i206.photobucket.com/albums/bb8/Cataban/IMG_1138.jpg

Still convinced it's RAM? Just because I got it off eBay doesn't mean it's the problem.


Memtest doesn't catch everything, hence why I also said to run Prime95 [which stresses the entire memory subsystem, and not just the RAM]. If, for instance, the northbridge was underpowered, Prime95 would catch it, memtest wouldn't.

PAGE_FAULT_IN_NONPAGED_AREA and MEMORY_MANAGEMENT both near impossible to get without significant memory subsystem problems. Its *possible* a bad driver could cause them, but very unlikely. SYSTEM_SERVICE_EXCEPTION with a parameter 1 of 0xC0000005 [STATUS_ACCESS_VIOLATION] is another indication that memory is somehow getting corrupted, since a 0xc0000005 EXPLICITLY means the application crashed because RAM somehow got corrupted. The three of these combined makes the memory subsystem the most likely culprit by far.
m
0
l
April 3, 2012 1:22:06 PM

I will run Prime95 later today and will look into the Windows repair solution.
m
0
l
!