BSOD minutes into boot

UndiluteD said:

I just built a brand new sytem, minutes into loging in the sytem crashes displaying a BSOD with Memory_management as the reason.

Multiupload.com - upload your files to multiple file hosting sites! (link to Minidump File)

I have run Memtest and windows memory test and both came back with no errors.

System: i7 930
AMD HD 5870
6gb cosair ram ddr3 1600
Asus P6t SE Motherboard
Windows 7 64 bit

Thanks any info would be great been driving me mad as i cant do anything really on the PC. Also tempretures seem to be in normal ranges. roughly 40 degress or under for most things.

\

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Code:

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


Loading Dump File [C:\Users\K\Desktop\040410-21652-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/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 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16384.amd64fre.win7_rtm.090710-1945
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Sat Apr  3 19:33:27.885 2010 (GMT-4)
System Uptime: 0 days 0:02:02.900
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 1A, {41790, fffffa8003e6b9e0, ffff, 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+71f00 )

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

Well its a second install of windows 7 on a seperate HD as i recieved the errors on the first fresh install. Also ive used the version i have before with No problems at all.

Is the error caused by not being able to read symbols or is a result of the problem and not actually the cause.

Also keep getting loads of errors related to modules? Like steam failing to load due to platform/module errors ect and firefox ocasionally

Follow zigzag3143 good advice.

UndiluteD said:

Well its a second install of windows 7 on a seperate HD as i recieved the errors on the first fresh install. Also ive used the version i have before with No problems at all.

Is the error caused by not being able to read symbols or is a result of the problem and not actually the cause.

Nope the cause is on your machine the symbols on mine. Just makes it impossible to help with your problem.

Ken

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Well I'm downloading Win 7 off Digital River as its pretty much untouched ran SFC.exe but it crashed near the end!? Also attempted another installation of win 7 but blue screened towards the end and corrupted installation. So gonna reburn my copy i have and see if was a corrupt copy i made.

Oh and ive been using "Microsoft.Windows.7.Ultimate.x64.November.2009.OEM.DVD-UP2DATE" if it makes a difference but it seems to of worked fine for me in the past

Will keep you updated with progress

UndiluteD said:

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Well I'm downloading Win 7 off Digital River as its pretty much untouched ran SFC.exe but it crashed near the end!? Also attempted another installation of win 7 but blue screened towards the end and corrupted installation. So gonna reburn my copy i have and see if was a corrupt copy i made.

Oh and ive been using "Microsoft.Windows.7.Ultimate.x64.November.2009.OEM.DVD-UP2DATE" if it makes a difference but it seems to of worked fine for me in the past

Will keep you updated with progress

That version string is unusual. I dont think I have ever seen that from a MS product. Usually it doesnt say "DVD-UP2DATE". Is there a product code on it?

Ken

zigzag3143 said:

UndiluteD said:

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Well I'm downloading Win 7 off Digital River as its pretty much untouched ran SFC.exe but it crashed near the end!? Also attempted another installation of win 7 but blue screened towards the end and corrupted installation. So gonna reburn my copy i have and see if was a corrupt copy i made.

Oh and ive been using "Microsoft.Windows.7.Ultimate.x64.November.2009.OEM.DVD-UP2DATE" if it makes a difference but it seems to of worked fine for me in the past

Will keep you updated with progress

That version string is unusual. I dont think I have ever seen that from a MS product. Usually it doesnt say "DVD-UP2DATE". Is there a product code on it?

Ken

DVD-UP2DATE is the group that released it onto the internet or ripped it. basically the version im using is the nov oem. which dosent require activation.

Also it keeps BSOD while installing win 7 and ive now got a corrupt install. So im assuming its not win 7 related issue. Ive tried 2 hard drives and getting the same result. Dont think CPU is over heating as the max ive seen it is 45 degrees any other diagnostic tools i can run outside of windows.

Also just about to rip the new version i downloaded but i dont think the error is win 7 related prob harware so cant see it making much diff but lets hope it produces a valid minidump u guys can take a look at.

UndiluteD said:

zigzag3143 said:

UndiluteD said:

Well I'm downloading Win 7 off Digital River as its pretty much untouched ran SFC.exe but it crashed near the end!? Also attempted another installation of win 7 but blue screened towards the end and corrupted installation. So gonna reburn my copy i have and see if was a corrupt copy i made.

Oh and ive been using "Microsoft.Windows.7.Ultimate.x64.November.2009.OEM.DVD-UP2DATE" if it makes a difference but it seems to of worked fine for me in the past

Will keep you updated with progress

That version string is unusual. I dont think I have ever seen that from a MS product. Usually it doesnt say "DVD-UP2DATE". Is there a product code on it?

Ken

DVD-UP2DATE is the group that released it onto the internet or ripped it. basically the version im using is the nov oem. which dosent require activation.

Also it keeps BSOD while installing win 7 and ive now got a corrupt install. So im assuming its not win 7 related issue. Ive tried 2 hard drives and getting the same result. Dont think CPU is over heating as the max ive seen it is 45 degrees any other diagnostic tools i can run outside of windows.

Also just about to rip the new version i downloaded but i dont think the error is win 7 related prob harware so cant see it making much diff but lets hope it produces a valid minidump u guys can take a look at.

You do realize that we can only support legit MS builds for we have no way of knowing what changes the "DVD-UPDATE" guys did to it.

That is especially true since they obviously did something to get around the "activation".

My advise: Download a stock image and try that


Ken