Sign in with
Sign up | Sign in
Your question

Frequent BSODs

Tags:
Last response: in Windows 7
Share
January 4, 2012 8:20:46 PM

Hello I am requesting urgent help on this BSODs I am losing my valuable data and other stuffs please can anyone give me solution? :cry: 

Here is the .dmp files for the BSODs

https://skydrive.live.com/?cid=01923c48eef0ea71&sc=docu...!103

More about : frequent bsods

a b $ Windows 7
January 4, 2012 8:39:06 PM

When are they bsod's happening?

Is this a newly built computer?

Is this an established computer that worked fine and is now bsod'ing?
m
0
l
a b $ Windows 7
January 4, 2012 10:53:10 PM

If you are loosing your data, and its important, take out the HDD and hook it up to an enclosure and back it all up onto another computer until you have the BSOD sorted, and then transfer that data back over. Happy days..
m
0
l
Related resources
a b $ Windows 7
January 4, 2012 11:57:02 PM

BSOD are normally caused by memory problems or driver problems (particularly video drivers) and some viruses can also cause them. Check your memory first by downloading and running memtest86 overnight.
m
0
l
January 5, 2012 2:05:08 AM

BSOD's are cause by all kinds of stuff. The first thing you should do is backup your data elsewhere as combat wombat said.

Then attempt to methodically nail down what's triggering the blue screens. Does it BSOD on your desktop? Does it crash in Linux (run Linux Mint off of a CD)? Does it BSOD when you play games? You can try testing your memory with Memtest86+ on a flashstick.

Which do you guys like better: Memtest86+ or memtest86?
m
0
l
January 5, 2012 2:19:05 AM

ya i tried memtest but it didnot give any problems and I think all my drivers are upto date especially video drivers
m
0
l
January 5, 2012 2:22:36 AM

ya its an established computer it did fine until I installed win 7 64 bit from win XP 32 bit. So I am guessing that might have triggered the problem, but I cant seem to find why cause I dont think there was any wrong with OS installation.
m
0
l
January 5, 2012 2:38:43 AM

Windows 7 has better memory management and stress out the memory more than XP. While Memtest is good for finding errors, the fact that it run alone without any component stressing the system may indicate that the memory voltage may not be able to hold stable while the computer is running and loaded.

Go into BIOS and give the ram voltage a little more voltage to help to compensate. Maybe your PSU is loosing a bit power too so that might help.
m
0
l
January 5, 2012 3:13:14 AM

Have you been monitoring your temps and voltages? Install HWMonitor. A bad PSU can cause crashes--so can overheating.

There's a respectable chance your Windows install is broken. You can try another HDD with a different Windows install or reinstall.
m
0
l
January 5, 2012 4:17:03 AM

So I need another HDD no matter what. Thanx guys i will try out the advises given and will update.
m
0
l
a b $ Windows 7
January 5, 2012 11:00:23 AM

Since the link to the minidump is blocked at work, and my work PC doesn't have my usual debug tools on it, can you at least provide the BSOD stop code?
m
0
l
January 5, 2012 11:08:41 AM

Stopcode error would be extremely usefull
m
0
l
January 5, 2012 11:40:01 AM

Try running a lot of different programs at once to see if you can replicate BSOD and report back.
m
0
l
a b $ Windows 7
January 5, 2012 12:16:14 PM

Uninstall any antivirus programs you have, uninstall display driver and then run driversweeper from http://phyxion.net/item/driver-sweeper.html then reinstall driver, download ccleaner and run ccleaner to clear temp files and then run its registry cleaner.

once you have done this run programs like you normally would to see if you can reproduce the crash, if it does not then reinstall antivirus and see if it crashes again, more often than not i have found bad antivirus updates to cause a majority of bsods and system problems. if it does crash then choose a different antivirus, i would reccomend eset smart security or mse if you want a free one, stay clear of AVG and AVIRA, have had more problems than not with them.
m
0
l
a b $ Windows 7
January 5, 2012 12:58:52 PM

Everyone, STOP.

Get the BSOD stop code next time it happens, then report back. Trying to solve the problem without first knowing what the problem is is an execise in futility.
m
0
l
January 5, 2012 2:14:00 PM

gamerk316 said:
Everyone, STOP.

Get the BSOD stop code next time it happens, then report back. Trying to solve the problem without first knowing what the problem is is an execise in futility.



Correct dear chap

Click on the Start button and then on Control Panel.

Tip: In a hurry? Type system in the search box after clicking Start. Choose System under the Control Panel heading in the list of results and then skip to Step 4.


Click on the System and Security link.

Note: If you're viewing the Small icons or Large icons view of Control Panel, you won't see this link. Simply double-click on the System icon and proceed to Step 4.


Click on the System link.


In the task pane on the left, click the Advanced system settings link.


Locate the Startup and Recovery section near the bottom of the window and click on the Settings button.


In the Startup and Recovery window, locate and uncheck the check box next to Automatically restart.


Click OK in the Startup and Recovery window.


Click OK in the System Properties window.


You can now close the System window.


From now on, when a problem causes a BSOD or another major error that halts the system, Windows 7 will not force a reboot. You'll have to reboot manually when an error appears.




From here you will now play the waiting game, when the BSOD happens again it will stay on your screen.
On this screen you will notice some or many 0x**** codes
These are your stop codes.
Make a note of atleast 5 of the codes.

Post results on here and watch the resolution appear like magic
m
0
l
a b $ Windows 7
January 5, 2012 2:56:36 PM

Stop error bsod's during windows install can be caused by something as simple as incorrect ram voltage.
m
0
l
January 6, 2012 1:38:47 PM

ok guys thanx i will post it as soon as i get them :D 
m
0
l
January 6, 2012 1:48:31 PM

Found one!! They are like this rite?
0x0000001e(0xffffffffc0000005, 0xfffff8000329e137, 0x0000000000000000, 0xffffffffffffffff)

m
0
l
January 6, 2012 11:10:56 PM

Here is the next 1:

0x0000004a (0x0000000074f32e09, 0x0000000000000002, 0x0000000000000000, 0xfffff88006bd3ca0)
m
0
l
a b $ Windows 7
January 6, 2012 11:13:47 PM

[quoteFound one!! They are like this rite?
0x0000001e(0xffffffffc0000005, 0xfffff8000329e137, 0x0000000000000000, 0xffffffffffffffff)
][/quote]

This error is caused by a faulty driver, Have you looked in the resource and performance monitor, located in control panel\all control panel items\performance information and tools\advanced tools\generate system health report ?
m
0
l
a b $ Windows 7
January 6, 2012 11:23:35 PM

Quote:
0x0000004a (0x0000000074f32e09, 0x0000000000000002, 0x0000000000000000, 0xfffff88006bd3ca0)


This error occurs because of system file damage, try running the SFC /scannow (as administrator) command to try and fix this. The files have been corupted either because of faulty memory or due to a virus.
m
0
l
January 7, 2012 2:16:22 AM

pjmelect said:
[quoteFound one!! They are like this rite?
0x0000001e(0xffffffffc0000005, 0xfffff8000329e137, 0x0000000000000000, 0xffffffffffffffff)
]

This error is caused by a faulty driver, Have you looked in the resource and performance monitor, located in control panel\all control panel items\performance information and tools\advanced tools\generate system health report ?
[/quote]

Hmm I looked into it. Didnt get what that was.
m
0
l
January 9, 2012 1:31:59 PM

Still having BSODs:

0x0000000a (0x00000000037c3000, 0x0000000000000002, 0x0000000000000000, 0xfffff800032e92f8).

0x0000004a (0x0000000074d32e09, 0x0000000000000002, 0x0000000000000000, 0xfffff880081cdca0)

0x0000001e (0xffffffffc0000005, 0xfffff800032bef00, 0x0000000000000000, 0xffffffffffffffff).

0x00000050 (0xfffff12009b12d80, 0x0000000000000001, 0xfffff880012df5d7, 0x0000000000000007).

Please help me!!!
m
0
l
a b $ Windows 7
January 9, 2012 2:36:30 PM

0x0000000a = IRQL_NOT_LESS_OR_EQUAL

This one ALMOST CERTIANLY points to bad memory.

0x0000004a = IRQL_GT_ZERO_AT_SYSTEM_SERVICE

This one ALMOST CERTIANLY points to bad memory.

0x0000001e = KMODE_EXCEPTION_NOT_HANDLED

This one means a system level service died, which ALMOST CERTIANLY points to bad memory.

0x00000050 = PAGE_FAULT_IN_NONPAGED_AREA

This one ALMOST CERTIANLY points to bad memory.


So in short:
Two IRQL BSOD's
One Paging BSOD
One Kernal mode exception

Bad RAM. Even though you said memtest is passing, I'm still calling it bad RAM. Run with one stick at a time, and if you BSOD, run with a different one.
m
0
l
!