Windows 7 consistent BSOD

[ThePhoenixLives]

Hi i just purchased a brand new computer from another website, a gaming rig, anyways when i bought it the hardrive was preformatted there was no OS but i installed Windows 7 professional 64 bit myself. anyways after doing this, i receive a blue screen of death everyday a couple of times a day, i've only had this system for about a week, and im very worried. I dont believe its a problem with the ram as i ran memtest and i passed it... I have all updated drivers for my asus motherboard and my nvidia graphics card... here are my specs if needed. Im just wondering what i should do?

AMD Athlon II (TM) X4 635 processor
AsusTek M4a785-M motherboard
Corsair DDR-2 dual 1 GB memory (2GB total)- located in slot 3 and 4
NVIDIA GeForce GT 220 1GB graphics card


anyways quick help would be appreciated

[Craig90day]

You will have to be more specific, what exact blue screen are you getting, you can try to google the error code and see if anyone has had a similar problem.

What are you doing when you bsod? Does it happen during boot, or when inside the OS?

In all honestly it seems that you are describing a hardware problem.

[ThePhoenixLives]

I dont get enough time to look at the BSOD to see which type, but i do believe a memory dump only because ive seen it say dumping memory

also it happens inside the os at random intervals, id be downloading something the computer isnt even working hard and it will give me a bsod, or itll just be sitting there at random intervals and just give me one. i wish i could get the error code ive been trying to download the debugging tool to use dumpchk.exe but for some reason its not working -______-

[jazz836062]

Event viewer can give you that information. After the machine bluescreens reboot and open event viewer (start, type "Event Viewer"). In the main pane expand "Error" and find which ones occurred in the last hour. Post back with what you find and we can help, maybe.

[ThePhoenixLives]

alright ill definitely let you guys know, how do i get to event viewer is there a certain executable i just type in?

[Miz]

As jazz posted, click the Start button and in the box at the bottom of the Start Menu, directly above the Start button, type the words "Event Viewer" (without the quotes).

A shortcut to Event Viewer should then appear at the top of the left-hand pane of the Start Menu. Click on it to open Event Viewer.

[ThePhoenixLives]

here i got a printscreen of "details" for you guys, im not sure if this is the information you needed, but i went to event viewer --> critical ----\> and this is the details of when my last bsod occured


please help asap!!!

[ThePhoenixLives]

here is all the error info in text
Log Name: SystemSource: EventLogDate: 8/25/2010 1:02:54 AMEvent ID: 6008Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: Adrian-PCDescription:The previous system shutdown at 12:59:47 AM on ‎8/‎25/‎2010 was unexpected.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="EventLog" /><EventID Qualifiers="32768">6008</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2010-08-25T05:02:54.000000000Z" /><EventRecordID>7185</EventRecordID><Channel>System</Channel><Computer>Adrian-PC</Computer><Security /></System><EventData><Data>12:59:47 AM</Data><Data>‎8/‎25/‎2010</Data><Data></Data><Data></Data><Data>17775</Data><Data></Data><Data></Data><Binary>DA0708000300190000003B002F005902DA070 8000300190004003B002F005902600900003C0000000100000 06009000000000000B00400000100000000000000</Binary></EventData></Event>

[ThePhoenixLives]

this just happened again literally a minute ago, this is the information i got with it. Btw how can i read mini dump files for some reason when i try to download the windows sdk its not letting me something is going wrong, cause i know i need dumpchk.exe


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 0000000000065250
BCP3: 0000000000000002
BCP4: 0000000000007BD9
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082510-25303-01.dmp
C:\Users\Adrian\AppData\Local\Temp\WER-44460-0.sysdata.xml

[ThePhoenixLives]

nevermind i think i got dumpcheck to work with windows 7 it was windbg.exe but i got this when i booted the dump file all these symbol errors and what not but hopefully this gives you guys enough information, help would be much appreciated cause im sick of getting these blue screens...

Loading Dump File [C:\Users\Adrian\Desktop\082510-25303-01.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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image 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 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03050e50
Debug session time: Wed Aug 25 02:35:49.595 2010 (UTC - 4:00)
System Uptime: 0 days 1:33:22.155
************************************************** *******************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image 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 4E, {99, 65250, 2, 7bd9}

***** 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 ***
*** ***
************************************************** ***********************
Probably caused by : ntoskrnl.exe ( nt+70740 )

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

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000065250, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000007bd9, 0

Debugging Details:
------------------

***** 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 ***
*** ***
************************************************** ***********************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002e13000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002f1338c to fffff80002e83740

STACK_TEXT:
fffff880`066b9438 fffff800`02f1338c : 00000000`0000004e 00000000`00000099 00000000`00065250 00000000`00000002 : nt+0x70740
fffff880`066b9440 00000000`0000004e : 00000000`00000099 00000000`00065250 00000000`00000002 00000000`00007bd9 : nt+0x10038c
fffff880`066b9448 00000000`00000099 : 00000000`00065250 00000000`00000002 00000000`00007bd9 fffffa80`010fadf0 : 0x4e
fffff880`066b9450 00000000`00065250 : 00000000`00000002 00000000`00007bd9 fffffa80`010fadf0 00000000`00003e58 : 0x99
fffff880`066b9458 00000000`00000002 : 00000000`00007bd9 fffffa80`010fadf0 00000000`00003e58 fffff800`02e1c37c : 0x65250
fffff880`066b9460 00000000`00007bd9 : fffffa80`010fadf0 00000000`00003e58 fffff800`02e1c37c e5800000`65250843 : 0x2
fffff880`066b9468 fffffa80`010fadf0 : 00000000`00003e58 fffff800`02e1c37c e5800000`65250843 fffffa80`012f6f00 : 0x7bd9
fffff880`066b9470 00000000`00003e58 : fffff800`02e1c37c e5800000`65250843 fffffa80`012f6f00 00000000`00000000 : 0xfffffa80`010fadf0
fffff880`066b9478 fffff800`02e1c37c : e5800000`65250843 fffffa80`012f6f00 00000000`00000000 00000000`00000000 : 0x3e58
fffff880`066b9480 e5800000`65250843 : fffffa80`012f6f00 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x937c
fffff880`066b9488 fffffa80`012f6f00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xe5800000`65250843
fffff880`066b9490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03274840 : 0xfffffa80`012f6f00


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+70740
fffff800`02e83740 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+70740

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

[ThePhoenixLives]

hey guys i also found out that the error type is 0x0000003b, and there is a bunch of sub errors im guessing in the parentheses after it?

[ThePhoenixLives]

i just received a different type of bsod too....

[lcsmith39]

You know, I just read your first post and I noted that you said you had the ram installed in slots 3 and 4. It may not make any difference at all, but just for the sake of it, I think that you should install the ram in the first to slots. Your motherboard might be a little finicky about the location of the ram. It may not make any difference but it will eliminate that as a possible problem.

[AnnMarie]

Hi ThePhoenixLives. You are not using the correct symbols therefore the Windbg results are not reliable.

Try lcsmith39's suggestion but if the problem persists, I am prepared to analyse the dumps for you but first, have you installed a USB Camera or Webcam? If so, disconnect it, uninstall the software and reboot.

Do you still get BSOD's?

[ThePhoenixLives]

i do have a webcam installed even though im not using it, the thing is, yeah maybe that would get rid of 1 bsod, but i'm getting MULTIPLE different ones thats why im so worried =/ also how do i change my symbols for windbg?
also ann marie can i email you my dumpchecks or something, its going to be like 3/4 dumpchecks only because the last 3 critical errors i received were all different bsods