PDA

View Full Version : Bluescreen on shutdown



Timbo
26-08-2010, 10:39 PM
I upgraded a PC running on XP to Win7 because XP wouldn't boot despite being reinstalled.

Now that Win 7 is installed and booting up fine, its now blue screening on shutdown. :S

Here is a pic of the blue screen:
http://img64.imageshack.us/img64/4109/dscn2680l.jpg

And when you start the PC up again, a message pops up saying you had a crash; here is what you get when you click on more details.



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

Additional information about the problem:
BCCode: 50
BCP1: FFFFFFFFFFFFFFD0
BCP2: 0000000000000001
BCP3: FFFFF800028DB83A
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082610-12776-01.dmp
C:\Users\Fung family\AppData\Local\Temp\WER-21294-0.sysdata.xml

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

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


Does anyone know whats causing this?


P.S. This computer is different from the overheating one in my other post.

Speedy Gonzales
26-08-2010, 10:53 PM
You should really do a clean install. Its probably because XP had probs thats its crashing now. Was it 32 bit XP and Win7 32 bit??

If you can still get into windows, get this

http://www.nirsoft.net/utils/blue_screen_view.html

Install it then see what the BSOD says, and tell us / what files are higlighted in pink. Or copy and paste what it shows in here

wainuitech
26-08-2010, 10:57 PM
Try doing a memory Test, it may be faulty. Faulty memory has been the main cause I usually see for that Error.

Have a read of this page (http://msdn.microsoft.com/en-us/library/ff559023(v=VS.85).aspx) - it explains the problems and possible causes / Fixes.

WarNox
27-08-2010, 09:11 AM
Whenever there is a blue screen a dump file is created in C:\windows\minidump. You can read this file using WinDbg, all the info you need is here:

http://support.microsoft.com/kb/315263

usually just a driver error, could be the memory too as somene else said.

Timbo
27-08-2010, 07:30 PM
You should really do a clean install. Its probably because XP had probs thats its crashing now. Was it 32 bit XP and Win7 32 bit??

If you can still get into windows, get this

http://www.nirsoft.net/utils/blue_screen_view.html

Install it then see what the BSOD says, and tell us / what files are higlighted in pink. Or copy and paste what it shows in here

I think it was a 32bit XP and its now a 64bit 7. I formatted the drive before doing a fresh install.

Here is what I got from the BSOD viewer:
http://img801.imageshack.us/img801/2725/timbo.png
http://img839.imageshack.us/img839/1425/timbo2.png
http://img825.imageshack.us/img825/88/timbo1.png

The error reports looks to be the same, but after I did a memory test with memtest86 it I got the two different error reports at the top. The memory test found no errors:(

Speedy Gonzales
27-08-2010, 07:39 PM
Looks like the audio drivers are the cause of one crash. Start from scratch again. Delete all partitions / create them again. Then reinstall Win7, if this is the only version of windows you're going to install

Timbo
27-08-2010, 09:18 PM
Looks like the audio drivers are the cause of one crash. Start from scratch again. Delete all partitions / create them again. Then reinstall Win7, if this is the only version of windows you're going to install

Aye? Can't I just reinstall or try different the sound drivers? I only plan to run Windows 7.

Speedy Gonzales
27-08-2010, 09:25 PM
Well uninstall the soundcard drivers. Dont install any driver / dont guess. If you know what the brand/model of the mobo is. Go to the site then download the drivers / install them. And MAKE SURE they're 64 bit drivers. Dont try and install 32 bit drivers. They wont work. Dont install any of the drivers you installed in XP they wont work. Since they're 32 bit, and you installed 64 bit

Agent_24
27-08-2010, 11:52 PM
What was the original issue with XP?

Timbo
28-08-2010, 11:42 AM
What was the original issue with XP?

Nope, issue with XP is that after the XP loading screen on startup, the screen will go blank "no signal" then restart again. I couldn't fix this by reformatting and reinstalling XP.

Agent_24
28-08-2010, 02:05 PM
Nope, issue with XP is that after the XP loading screen on startup, the screen will go blank "no signal" then restart again. I couldn't fix this by reformatting and reinstalling XP.

Sounds like XP was crashing with a BSOD error but you just couldn't see it for whatever reason (it happens sometimes) and was restarting automatically.

The fact that both XP and Win7 don't work properly on the same machine suggests that the issue is a hardware one.

wainuitech
28-08-2010, 02:05 PM
Nope, issue with XP is that after the XP loading screen on startup, the screen will go blank "no signal" then restart again. I couldn't fix this by reformatting and reinstalling XP. That sounds a lot like a hardware problem.

Simply put, the Monitor is saying its not receiving a signal from the Motherboard/graphic Card. Even with the PC turned off the monitor can still detect the PC (or should).

Timbo
30-08-2010, 04:57 PM
Looks like the audio drivers are the cause of one crash. Start from scratch again. Delete all partitions / create them again. Then reinstall Win7, if this is the only version of windows you're going to install

Yay, Its fixed!

Turns out to be the 56k modem. I went to device manager to diable the sound to test and I noticed that the 56k modem is highlighted with a error; I disabled that and the sound and my PC shut down without a BSOD. Then I tried again with only the modem disabled and now everything is sweet!

Speedy Gonzales
30-08-2010, 05:01 PM
Sounds like the drivers (for the modem), maybe 32 bit why it crashed (if you're using 64 bit). And why its fine, if you disable it. You may as well remove it, if there are no drivers

albertrong
31-08-2010, 10:15 PM
There are many reasons that will lead to your computer has blue screen:
1. The virtual memory was not enough and lead to a mistake.
2. The CPU usage was enough.
3. Memory Bank was broken will cause the wrong operation.
4. The Free Space of Disk is not enough
5. System Hardware conflicted.

So, you could do some measures to avoid the blue screen.
1. Download good optimizer software to save more space of your computer and memory.
2. Clean up the Registry Errors.
3. From the Control Panel, click the System button, check the Device Manager, if there is a yellow exclamation mark, you could reinstall it.

If the computer has blue screen, maybe it will lead to the System crash and lost information. So you should back up the system before it occurs.

Perfect Optimizer could solve the two upper troubles and it could back the system.

Timbo
01-09-2010, 07:55 PM
Sounds like the drivers (for the modem), maybe 32 bit why it crashed (if you're using 64 bit). And why its fine, if you disable it. You may as well remove it, if there are no drivers
The thing was there was actually drivers for it in Windows update. I choose not to do the Windows update until I resolved the BSOD issue(incase I had to reinstall Windows). But the thing is it probably would of fixed itself if I went through with the Windows update.:punk

Speedy Gonzales
01-09-2010, 07:59 PM
BUT, are the drivers for the modem 64 bit in windowsupdate?

If youre using 64 bit?

Timbo
01-09-2010, 08:59 PM
I didn't look at it that close, I assume MS is smart enough to filter out 32 bit drivers. Yip I'm running 64 bit

Agent_24
01-09-2010, 09:13 PM
The thing was there was actually drivers for it in Windows update. I choose not to do the Windows update until I resolved the BSOD issue(incase I had to reinstall Windows). But the thing is it probably would of fixed itself if I went through with the Windows update.:punk

I doubt it, Windows update has burnt me, my friends and other people on the forum several times well when it comes to updating drivers.

Only had it actually work properly ONCE with a webcam I was installing on Windows 7.

Then funny thing, I reinstalled Windows 7 about 3 months later, and it advised me to install a completely different driver for the same webcam that didn't even work at all!

wainuitech
01-09-2010, 10:26 PM
Modem the cause - not at all surprised. 56K Modems can give a load of trouble.

Mind you to be fair to every one here trying to help - its very awkward when it was never mentioned a 56K modem was installed. ;)