Sign in with
Sign up | Sign in
Your question

Windows 7 BSOD?

Last response: in Windows 7
Share
February 6, 2011 2:19:19 AM

Im guessing its an issue with he ram since I was having this problem before...


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002D1C540
BCP3: FFFFF88008397FE0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020511-27328-01.dmp
C:\Users\Maziar\AppData\Local\Temp\WER-71734-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

More about : windows bsod

February 6, 2011 2:25:05 AM

if you suspect RAM, have you run Memtest86+? If not, download and burn the ISO, then set your BIOS to boot from CD/DVD first.
http://www.memtest.org/
m
0
l
February 6, 2011 2:26:52 AM

I already did that. (ive had this problem before). It passed. I already ordered new ram to replace it, but im not sure if this is the problem.
m
0
l
Related resources
February 6, 2011 2:31:11 AM

I should also add that sometimes my computer won't post. Ill turn it on, and I can here the GPU trying to turn on, but it keeps failing. After taking out one stick of ram and putting it back, the computer works fine....Until I BSOD.
m
0
l
February 6, 2011 2:45:28 AM

Check your motherboard QVL for memory compatibility for starters. This will give you an idea to start from as far as type and DIMM configuration. Second I would suggest clearing the CMOS by unplugging the computer, removing the battery from the motherboard (move the jumper if applicable as noted in the manual), and remove any and all unneeded parts for boot, if onboard video, use that and only 1 stick of RAM in the first socket (closest to the cpu in most cases is DIMM0) and boot the machine. If no BSOD, shut down and add a second RAM module (and repeat until all are in use). If no issue, then it is not a memory failure. Install your graphics adapter and see if the problem occurs here.

I would even go so far as to say remove the motherboard from the case and set on a phone book to eliminate any short to the case from the motherboard. What you describe could in all actuality be a failure of either hardware or a driver issue from your Windows install.

Also verify if all your drivers are up to date.

This should help you narrow down the problem.
m
0
l
February 6, 2011 4:04:37 AM

maziar321 said:
I should also add that sometimes my computer won't post. Ill turn it on, and I can here the GPU trying to turn on, but it keeps failing. After taking out one stick of ram and putting it back, the computer works fine....Until I BSOD.


It is possible that your PSU may be failing. I would suggest testing it with a PSU test with LCD readout. You can pick one up at Best Buy for $20 or, if you have a spare PSU, throw it in and test it out.
m
0
l
February 6, 2011 4:25:49 AM

heres the thing, when I start the computer sometimes, The gpu makes the spinning sound like before, and it wont post. But as soon as I remove a ram stick, the computer works fine, even when I put the stick back. I've also been able to recreate this with the onboard video. I've had this computer for over a year now, and im just now having problems...
m
0
l
February 6, 2011 5:04:10 AM

It would still help to eliminate another component. I would say test the PSU, then return the tester to the store.

-What is the BSOD code? (ex. 0x0000007E)
m
0
l
February 6, 2011 5:37:32 PM

heres the BSOD after doing what dadiggle said.


==================================================
Dump File : 020511-27328-01.dmp
Crash Time : 2/5/2011 8:13:23 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d1c540
Parameter 3 : fffff880`08397fe0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\020511-27328-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 274,856
==================================================
m
0
l
February 6, 2011 6:45:55 PM

Try updating your audio and video drivers. I have also seen this problem has been with AVG antivirus, pagefile, HDD's, and memory. Since you have ruled out memory I would Uninstall the current drivers and update the drivers first. The could have become corrupted some how. I would also clean the registry with ccleaner.

From personal experience I have had alot of trouble with realtek audio drivers lately, so I uninstalled the realtek drivers and used the drivers that windows 7 installs.
I have also had problems with USB devices causing random BSOD's and no post, so if you have a card reader or expanion slot usb unplug it.
m
0
l
February 6, 2011 7:12:47 PM

d1rtyju1c3 said:
Try updating your audio and video drivers. I have also seen this problem has been with AVG antivirus, pagefile, HDD's, and memory. Since you have ruled out memory I would Uninstall the current drivers and update the drivers first. The could have become corrupted some how. I would also clean the registry with ccleaner.

From personal experience I have had alot of trouble with realtek audio drivers lately, so I uninstalled the realtek drivers and used the drivers that windows 7 installs.
I have also had problems with USB devices causing random BSOD's and no post, so if you have a card reader or expanion slot usb unplug it.

I'm confused, had did I rule out ram? Infact, I think this is the problem, but I need to make sure. Again, when I take a stick out and put it back in, the system works fine and I get a post. But it will still bsod.
m
0
l
February 6, 2011 7:29:03 PM

maziar321 said:
I'm confused, had did I rule out ram? Infact, I think this is the problem, but I need to make sure. Again, when I take a stick out and put it back in, the system works fine and I get a post. But it will still bsod.


Alaskan_IT "if you suspect RAM, have you run Memtest86+?"

Maziar321 "I already did that. (ive had this problem before). It passed. I already ordered new ram to replace it, but im not sure if this is the problem."

You said you ran memtest86, if it passed then it isnt the ram.

I suggest running each stick one at a time and run memtest86 for 5-7 passes on each stick if you are unsure if it is the memory, but if you have already done that it isnt the ram. It could be a possibility it is one of the ram slots. Try to move the ram from slot 1 and 3 to 2 and 4.
m
0
l
February 6, 2011 11:26:34 PM

Oh... I didnt run its for 7 passes. I just did one pass... That could explain it
m
0
l
February 7, 2011 2:46:44 AM

I was using avast when the problem started, but im using Norton now. So i doubt thats an issue.
m
0
l
February 7, 2011 12:41:18 PM

I just ran memtest86+ overnight on one of my ram test and it came back with 5 errors on pass 2. Does this mean that my ram is faulty? I am rerunning the test with the other stick in the same ram slot to make sure its not a faulty slot thats causing the issue. I will bump later today if no replys.
m
0
l
February 7, 2011 6:46:01 PM

just a friendly bump...
m
0
l
February 7, 2011 10:30:38 PM

If the ram came up with errors then yes it could be bad but it could be the slot.
Is it running at stock speed, voltage and latencies?
Is the second stick done being tested?
I would also test each one in another slot just to make sure.
m
0
l
February 7, 2011 11:52:21 PM

Quote:
Could be lets see. What motherboard do you have?

Go in the bios post me your ram timings and its current voltages please


timings are 9-12-12-30 voltage at 1.65

I'd also like to mention that this ram was on the motherboards recomended list of ram. (I think the is called the QVL?)
m
0
l
February 7, 2011 11:59:02 PM

Oh, and I did retest the other ram stick in the same slot and I ran 17 passes ( I was at school all day), and it cameback with no errors.
m
0
l
February 8, 2011 12:07:56 AM

Oh, and I have an ASrock board... my god, I didnt notice that there were so many posts... Honestly, even if its not my ram causing the BSOD, am still going to replace it. One error is too much.
m
0
l
February 8, 2011 12:18:42 AM

I just reran memtest on the same stick that recieved an error with a working ramslot, and I recieved another error on the same pass. Im pretty sure that means unstable ram...
m
0
l
February 8, 2011 3:44:35 AM

I think you have just solved your problem. It is time to purchase some new memory. Good luck and test the memory with Memtest86 first thing to make sure hte new stuff dont error.
m
0
l
February 8, 2011 5:05:19 AM

alright, Ill get back to you If I find problems with the new ram... I actually assumed this was the problem and I ordered it last friday.
m
0
l
February 8, 2011 9:10:28 PM

I have no clue, but I cant statr my computer so I can't check. Question, if memtest shows errors, does that automatically that my ram or ram slot is damaged? Should I always assume that?
m
0
l
!