Release List Reviews Shop Join News DVD Giveaways Video Games Advertise
DVD Reviews | Theatrical Reviews | Adult DVD Reviews | Video Game Reviews | Price Search Buy Stuff Here
DVD Talk
DVD Reviews DVD Talk Headlines HD Reviews


Add to My Yahoo! - RSS 2.0 - RSS 2.0 - DVD Talk Podcast RSS -


Go Back   DVD Talk Forum > General Discussions > Tech Talk

Tech Talk Discuss PC Hardware, Software, Internet and Other Technology

Reply
 
Thread Tools
Old 01-14-08, 05:37 PM   #1
ravan
DVD Talk Limited Edition
 
Join Date: Nov 1999
Location: In the ATL
Posts: 6,740
BSOD in vista.. lets figure out why..

I just put together a nice little machine with the following specs

- Raptor 10gn 150 gb sata drive (plus a bunch of other sata drives for storage)
- 4x2 gb sli ready OCZ OCZ2N800SR4GK 4GB PC2-6400 (8 gb total)
- Intel Quad Core C2Q Q6600 2.40G 775 8M R
- DFI LANPARTY UT NF680i LT SLI-T2R Core 2 Quad/ nForce 680i LT SLI/ FSB1333/ A&2GbE/ ATX motherboard
- A 8800 GT nvidia card (forget the exact model)
- Linksys Wireless-N PCI Adapter

I'm not writing specs to brag (not even sure its braggable), but because i get BSOD's pretty often. I'm talking like 2-3 per night.

I *think* they happen when a lot of activity is ongoing, maybe with the harddisks or network, but i'm not sure obviously.

With all components being new, i'm a bit at a loss on how to start figuring this out. I have a good antec PSU, so hoping thats not it at least...

Its a clean vista ultimate 64 bit install (100% legal version duh.

Any ideas? I get the dmp file but never seen them used for anything useful nor do i have any idea on how to attack it.
  Reply With Quote
Old 01-14-08, 06:48 PM   #2
fumanstan
DVD Talk Hero
 
Join Date: Oct 2002
Location: Rancho Santa Margarita, CA
Posts: 38,543
What do the blue screens say? I don't recall if Automatic Restart is enabled in Vista like it is in XP, but you might want to disable that in your system properties and see if you can catch the error message on the blue screen if it's just rebooting at the moment.

My first assumption would be RAM though.... running some memory tests would be an easy one.
__________________
3x Sheep Champion

VG Round 1b | VG Round 7 | NFL
  Reply With Quote
Old 01-14-08, 07:01 PM   #3
ravan
DVD Talk Limited Edition
 
Join Date: Nov 1999
Location: In the ATL
Posts: 6,740
RAM is a good place to start.

Any recommended memory test programs that will support vista 64 bit?

I vaguely recall the screen saying something like 'Illegal Service' or something, which didnt immediately make sense to me. I'll try and disable automagic restart (its enabled by default in vista as well)
  Reply With Quote
Old 01-14-08, 08:14 PM   #4
ravan
DVD Talk Limited Edition
 
Join Date: Nov 1999
Location: In the ATL
Posts: 6,740
I ran the built in memory tool in vista with no issues. Check that one off the list I guess..
  Reply With Quote
Old 01-14-08, 08:22 PM   #5
ravan
DVD Talk Limited Edition
 
Join Date: Nov 1999
Location: In the ATL
Posts: 6,740
Ok i'm trying to look at the minidump file, but getting out of my comfort zone fast..

I did whats listed here http://www.memecode.com/docs/minidump.php but i think some symbols thing is missing.. last line says blame ntoskrnl which is not very helpful...

C:\Program Files\Debugging Tools for Windows 64-bit>kd -z \windows\Minidump\
011408-02.dmp

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


Loading Dump File [C:\windows\Minidump\Mini011408-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 ntoskrn
e
Windows Vista Kernel Version 6000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70
Debug session time: Mon Jan 14 03:52:35.626 2008 (GMT-5)
System Uptime: 0 days 0:47:05.779
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 ntoskrn
e
Loading Kernel Symbols
............................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
......
****************************************************************************
*
* Bugcheck Analysis
*
****************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80001e8eed5, fffff98014856fb0, 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+28eed5 )

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

3: kd>
  Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


All times are GMT -5. The time now is 04:15 PM.

Rules - DVD Talk - Archive - Privacy Statement - Top

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0
Copyright 2011 DVDTalk.com All Rights Reserved. Privacy Policy and Terms of Use.