In A Very Big BSOD Mess.

Hey guys, heres the situation, i was on youtube watching videos and them bam, my Laptop (Advent 6555) cut out .

On it i run Vista 32 Bit Home Premium
and W7 64bit Build 7100

I believe the BSOD for that was
msrpc.sys (an important sys file to do with kernels)

And for the last 4 hours its been constantly blue screening, i have managed to achive minimum access to windows vista (not 7).

I would appreciate any help as im feeling pretty beat right now .

 

Is it always the same bluescreen? Is it on boot, or after a little bit of time?
Sounds like a stick of RAM just had a whole bunch of blocks fail, or possibly a failing drive.
Since you're dual booting and both OSes are affected, we can rule out software (though it's possible but unlikely malware caused this).

Do you have the problem going into safe mode?
Are these BSODs logged in event viewer?

If you need any clarifications or directions on my questions, just ask.

 

Have you looked at the minidump files, debugging, if not there's a guide here:

http://forums.majorgeeks.com/showthread.php?t=35246

If you can't do it, try and upload the minidump files located:

C:>windows>minidump>*******.dmp

 

Hey, thanks for the fast responses, basically the blue screens change depending on my actions (as i have f8 for both menu's, i can specifically run different things)

I have to be careful though, some folders can just make the lappy blue screen, i will attempt to retrieve as many of the dumps as i can.

Safe mode is non accesible, however the service restore directory? or something like that allows some safe mode operation.

Cheers
cata

 

What's the code on those bluescreens?
0x00000000 <-- Looks kind of like that.

Before trying to look at the minidumps, why don't we test out your hardware?

Memory
Video Memory (Burn ISO in the archive to a CD, boot from it - don't bother with the in Windows test)
Hard drive can be found from your drive manufacturer's website.

 

Toshiba dont have any i dont think, i will quickly give you the bsods and i cannot download memory test

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini051609-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 1a
BCP1: 00004000
BCP2: 871DA900
BCP3: 00000080
BCP4: 0023FAC3
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini051609-05.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: a
BCP1: 00000008
BCP2: 0000001B
BCP3: 00000000
BCP4: 8247F86E
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Description
The results of running the Windows Memory Diagnostics Tool were submitted to Microsoft for analysis and product improvement

Problem signature
Problem Event Name: MemDiagV1
Range of memory size: 3072
Launch type: BootManager
Schedule type: Immediate
Completion type: Pass
Test type: Standard
Failed tests: 0
Range of number of bad pages: 0
Test duration in seconds: 840
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057

Files that help describe the problem
MemDiag.bin

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Will try and find memtest.

 

You don't have another PC to download the ISOs and burn them on?

 

I mean i couldn't find memtest iso hehe, but got it now, pre compiled

Burning memtest as we speak

 

Over 1800000 errors and counting.

Somehow it managed to drift off into 4300mb of ram?

This is unbelievable

 

Looks like you've got two stop error codes there, the first one, identified as BCCode: 1a, which is equivalent to stop code 0x0000001a, and BCCode: a, which is equivalent to stop code 0x0000000a.

A basic description of stop code 0x1A is here. There is an MSDN article on this stop error here. I didn't find a specific KB article for stop code 0x0000001a; however, there are a number of hits that come up on a search of the Microsoft support website for that stop code, as seen here - all of them appear to be related to RAM and memory management.

A basic description of stop code 0x0A is here, and the MSDN article the first webpage refers to. FWIW, this error is generally related to a driver problem.

There is also a Microsoft knowledgebase "KB" article that gives general advice for troubleshooting 0x0A stop errors in XP, KB314063 - I realize you're not running XP; however, for such a fundamental error, the guidance under XP is likely to be either directly applicable to _Vista, or a very, very good guide to what the source of the problem is under _Vista.


It does sound as if you have a bad RAM module that is triggering both memory management stop errors and, if it corrupted some of the code for one of your drivers, it could also be triggering the driver-related 0x0000000a stop-code. The errors you reported in your last post directly above would seem to support this, as well.

 

Now test the memory modules separately. Also test one in one slot, one in the other to rule out the possibility of a bad slot.
If one passes and one fails, you know it was a bad module/slot.
If both slots/stick fail, then you either got really unlucky and both modules went bad at the same time, or your motherboard is bad.


Also the reason I wanted to test out hardware first was there is no point in analyzing a minidump or the error codes if it's being caused by bad memory, bad memory can cause any BSOD under the sun... and believe me, I've seen some weird ones.
The described problem sounded like memory to me from the start, which is why I pushed it so much.
No need to speculate on if there is a memory issue from this point on, now it's all about figuring out what's the problem. Bad module? Improperly seated memory? Chipset issue? And so on.

 

Thanks for your help Shyster and hep, will look into it

Cata