10 BSOD's HELP

ajayhp · 04 Apr 2010

HP Compaq nx6325
ATI radeon Xpress 256mb
2.12gb Ram
80GB HDD
AMD turion 64x2 1.6GHZ

some of these BSOD's happened when i switched on the computer from standbuy mode, the screen wouldn't disaply the BSOD properly, and it would restart automatically

On Sun 04/04/2010 05:24:29 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xA3678870, 0xA3678450, 0x82A75759)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\040410-37171-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 03/04/2010 12:03:28 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x82B7004D, 0x8AE2B1B4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\040310-17343-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Wed 31/03/2010 06:30:13 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xFC (0x9659C21F, 0x2BB5A121, 0x970F05E0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Dump file: C:\Windows\Minidump\033110-18671-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Tue 30/03/2010 09:56:21 your computer crashed
This was likely caused by the following module: symevent.sys
Bugcheck code: 0x1A (0x41790, 0xC08027A6, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\033010-18140-01.dmp
file path: C:\Windows\system32\drivers\symevent.sys
product: SYMEVENT
company: Symantec Corporation
description: Symantec Event Library

On Mon 29/03/2010 09:43:07 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x4E (0x99, 0x97061, 0x0, 0x86E448D0)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\032910-58531-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 27/03/2010 23:30:33 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x50 (0xB93A3741, 0x1, 0x82B59067, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\032710-19718-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Wed 24/03/2010 19:21:28 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000006, 0x82CBFEF6, 0xB18D6B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032410-18265-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Tue 23/03/2010 16:45:56 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\032310-25937-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Mon 22/03/2010 19:23:36 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x926443F7, 0x9AE4BB50, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032210-27968-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 11/03/2010 07:35:50 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x8296A46A, 0x8AC5FB48, 0x8AC5F720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\031110-26281-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

I used a program called WHOCRAHSED, great utility to see what crashed

**Capt.Jack Sparrow** · 04 Apr 2010

ajayhp said:

HP Compaq nx6325
ATI radeon Xpress 256mb
2.12gb Ram
80GB HDD
AMD turion 64x2 1.6GHZ

some of these BSOD's happened when i switched on the computer from standbuy mode, the screen wouldn't disaply the BSOD properly, and it would restart automatically

Hello Ajay Welcome to SF,

We need the Dump files to analysis it to know what exactly the problem is otherwise it kinda vague. Please post us the dump files we will be more happy to help you out !!

https://www.sevenforums.com/crash-loc...d-problem.html

- Captain

ajayhp · 04 Apr 2010

Minidump file is here:

**Capt.Jack Sparrow** · 04 Apr 2010

ajayhp said:

Minidump file is here:

Hello,

I ran your Dump files. 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\SHYAMS~1\AppData\Local\Temp\Rar$DI04.707\031110-26281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows\System32
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20510.x86fre.win7_ldr.090819-1503
Machine Name:
Kernel base = 0x8284b000 PsLoadedModuleList = 0x82993810
Debug session time: Thu Mar 11 13:04:43.768 2010 (GMT+6)
System Uptime: 0 days 0:00:38.956
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8296a46a, 8ac5fb48, 8ac5f720}

***** 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 : ntkrnlpa.exe ( nt+11f46a )

Followup: MachineOwner

- Captain