Fifth bluescreen today.. fifth bluescreen since reformat!

[iFargle]

So... Here's a brief summary:

Installed Bioshock 2, Installed the new Steam UI, installed ZDSoft Screen Recorder, StarCraft II Beta, and.... the Supreme Commander II demo.

All of these (with the exception of StarCraft II and the Steam UI, have been uninstalled)

I think a majority of them were during StarCraft II. I specifically remember getting on while uninstalling my Toshiba bluetooth drivers before restarting into safe mode and uninstalling everything listed above there

After getting these BSoD's, I restarted in safe mode and uninstalled evrything and ran a CCleaner for everything

Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Here is the "WERDAA5.tmp.version.txt"

Windows NT Version 6.0 Build: 6002 Service Pack 2
Product (0x1): Windows Vista (TM) Ultimate
Edition: Ultimate
BuildString: 6002.18160.amd64fre.vistasp2_gdr.091208-0542
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033

Let me know if you need any other files / information, I'll get them to you as fast as possible. Thank you for any help! I'm in need here

EDIT: I attached the .dmp file associated with this BSoD in a .zip folder, hope that's alright.

EDIT #2: Just before the BSoD's began happening, I was installing an update for StarCraft II (it's first major update). It failed multiple times, saying some file couldn't be opened. This waas when I was opening the .exe through a shortcut on Steam. When I opened the .exe directly, it worked just fine, so I thought nothing of it. Could this be a problem? It has been happening since StarCraft II updated. Maybe that .dmp file will tell some of you more than it tells me.. I dont even know how to open it

 

[KSoD]

Okay the info provided doesnt give us any info. Check the sticky thread about Stop Errors. It will provide you with insite on what info we need. Check my signature for the windbg tutorial and try that as well. Giving that info will help us better provide you with information.

 

[iFargle]

Here's the WinDbg text:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini022510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02048000 PsLoadedModuleList = 0xfffff800`0220cdd0
Debug session time: Thu Feb 25 20:15:37.697 2010 (GMT-8)
System Uptime: 0 days 0:12:16.494
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002435930, fffffa600a04f030, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+3ed930 )

Followup: MachineOwner
---------

I'll get that stop code in a minute, I gotta get a blue screen

EDIT: I tried to get a BSoD but it didn't work.. I'm sure everything's the same, except I didn't play an online game.. I'll try that again tomorrow, It's late here

 

[iFargle]

just got one. Here's some more info:

BCCode: 50
BCP1: FFFFF7FF92E35F08
BCP2: 0000000000000000
BCP3: FFFFF8000252910B
BCP4: 0000000000000005
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

0x00000050 0xFFFFF7FF923E35F08 0X0000000000000000 0XFFFFF8000252910B 0X0000000000000005

 

[Hefemeister]

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

run memtest
Memtest86+ - Advanced Memory Diagnostic Tool

 

[iFargle]

Does this mean a memory module is bad?? oh that's not good How long should I run it for?

 

[Hefemeister]

Not necessarily but it is the most probable cause.

At least one hour with all sticks. If you get errors start running it with only single sticks installed to determine which one is bad.

 

[iFargle]

I let it run all night. Seven passes, zero errors with all sticks in

 

[Hefemeister]

^^Good and Bad

Any overclocking? If so return it to default for now.

run a hd diagnostic on your hd.

If you have a different gpu try running that for a bit.

Do these in steps to see if one of them clears up your issues.

 

[iFargle]

Yep, I have it OC'd

Where would I get this HDD diagnostic tool?

And no extra GPU, so I can't try that. I hope it's not the GPU.. Oh man