Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on win 7


  • Please log in to reply
7 replies to this topic

#1 SP!Micky

SP!Micky

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 19 February 2011 - 06:09 PM

HI Guys I've been co-opted to help a friend with their computer which has been blue screening for a while on and off. but now it will only run for 5 minutes or so before it crashes.
I have some limited experience, but not enough to fix this.
I have tried system restore last known good configuration, managed to do a full scan with norton 360, no use.
I cannot run backup. cannot run windows update, neither want to know.I have tried to reinstal windows 7 upgrade to do repair, but get the message not enough memory even though this machine has 1Tb disk and about 800 Mb free !
I managed to save a minidump file to a usb stick and tried to debug, but don't mind admitting that I am over my head.
Here are the reults of one of the dmp files (hopefully!!!)

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Minidump\021811-97953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82c41000 PsLoadedModuleList = 0x82d89810
Debug session time: Fri Feb 18 17:19:55.535 2011 (UTC + 0:00)
System Uptime: 0 days 0:03:23.940
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82cfc3e1, 8d387a60, 8d387640}

Probably caused by : ntkrpamp.exe ( nt!RtlImageNtHeaderEx+4a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82cfc3e1, The address that the exception occurred at
Arg3: 8d387a60, Exception Record Address
Arg4: 8d387640, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

EXCEPTION_RECORD: 8d387a60 -- (.exr 0xffffffff8d387a60)
ExceptionAddress: 82cfc3e1 (nt!RtlImageNtHeaderEx+0x0000004a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 7ffa0000
Attempt to read from address 7ffa0000

CONTEXT: 8d387640 -- (.cxr 0xffffffff8d387640)
eax=00005a4d ebx=85868efc ecx=00000000 edx=7ffa0000 esi=00000000 edi=8d387b3c
eip=82cfc3e1 esp=8d387b28 ebp=8d387b28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlImageNtHeaderEx+0x4a:
82cfc3e1 663902 cmp word ptr [edx],ax ds:0023:7ffa0000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 7ffa0000

READ_ADDRESS: GetPointerFromAddress: unable to read from 82da9718
Unable to read MiSystemVaType memory at 82d89160
7ffa0000

FOLLOWUP_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 82d00484 to 82cfc3e1

STACK_TEXT:
8d387b28 82d00484 00000000 00000000 85868cc0 nt!RtlImageNtHeaderEx+0x4a
8d387b5c 82c58c95 857e5cf2 00000000 00000004 nt!RtlImageNtHeader+0x1a
8d387c18 82c0fba9 85868cc0 00000000 8d387c60 nt!EtwpCCSwapTrace+0x433
8d387d00 82caf03b 800026b0 00000000 857c2020 hal!KfLowerIrql+0x61
8d387d50 82e4f9df 00000001 a0b13ddb 00000000 nt!ExpWorkerThread+0x10d
8d387d90 82d011d9 82caef2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!RtlImageNtHeaderEx+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cc78ed4

STACK_COMMAND: .cxr 0xffffffff8d387640 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82cfc3e1, The address that the exception occurred at
Arg3: 8d387a60, Exception Record Address
Arg4: 8d387640, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

EXCEPTION_RECORD: 8d387a60 -- (.exr 0xffffffff8d387a60)
ExceptionAddress: 82cfc3e1 (nt!RtlImageNtHeaderEx+0x0000004a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 7ffa0000
Attempt to read from address 7ffa0000

CONTEXT: 8d387640 -- (.cxr 0xffffffff8d387640)
eax=00005a4d ebx=85868efc ecx=00000000 edx=7ffa0000 esi=00000000 edi=8d387b3c
eip=82cfc3e1 esp=8d387b28 ebp=8d387b28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlImageNtHeaderEx+0x4a:
82cfc3e1 663902 cmp word ptr [edx],ax ds:0023:7ffa0000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 7ffa0000

READ_ADDRESS: GetPointerFromAddress: unable to read from 82da9718
Unable to read MiSystemVaType memory at 82d89160
7ffa0000

FOLLOWUP_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 82d00484 to 82cfc3e1

STACK_TEXT:
8d387b28 82d00484 00000000 00000000 85868cc0 nt!RtlImageNtHeaderEx+0x4a
8d387b5c 82c58c95 857e5cf2 00000000 00000004 nt!RtlImageNtHeader+0x1a
8d387c18 82c0fba9 85868cc0 00000000 8d387c60 nt!EtwpCCSwapTrace+0x433
8d387d00 82caf03b 800026b0 00000000 857c2020 hal!KfLowerIrql+0x61
8d387d50 82e4f9df 00000001 a0b13ddb 00000000 nt!ExpWorkerThread+0x10d
8d387d90 82d011d9 82caef2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!RtlImageNtHeaderEx+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cc78ed4

STACK_COMMAND: .cxr 0xffffffff8d387640 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82cfc3e1, The address that the exception occurred at
Arg3: 8d387a60, Exception Record Address
Arg4: 8d387640, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

EXCEPTION_RECORD: 8d387a60 -- (.exr 0xffffffff8d387a60)
ExceptionAddress: 82cfc3e1 (nt!RtlImageNtHeaderEx+0x0000004a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 7ffa0000
Attempt to read from address 7ffa0000

CONTEXT: 8d387640 -- (.cxr 0xffffffff8d387640)
eax=00005a4d ebx=85868efc ecx=00000000 edx=7ffa0000 esi=00000000 edi=8d387b3c
eip=82cfc3e1 esp=8d387b28 ebp=8d387b28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlImageNtHeaderEx+0x4a:
82cfc3e1 663902 cmp word ptr [edx],ax ds:0023:7ffa0000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 7ffa0000

READ_ADDRESS: GetPointerFromAddress: unable to read from 82da9718
Unable to read MiSystemVaType memory at 82d89160
7ffa0000

FOLLOWUP_IP:
nt!RtlImageNtHeaderEx+4a
82cfc3e1 663902 cmp word ptr [edx],ax

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 82d00484 to 82cfc3e1

STACK_TEXT:
8d387b28 82d00484 00000000 00000000 85868cc0 nt!RtlImageNtHeaderEx+0x4a
8d387b5c 82c58c95 857e5cf2 00000000 00000004 nt!RtlImageNtHeader+0x1a
8d387c18 82c0fba9 85868cc0 00000000 8d387c60 nt!EtwpCCSwapTrace+0x433
8d387d00 82caf03b 800026b0 00000000 857c2020 hal!KfLowerIrql+0x61
8d387d50 82e4f9df 00000001 a0b13ddb 00000000 nt!ExpWorkerThread+0x10d
8d387d90 82d011d9 82caef2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!RtlImageNtHeaderEx+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cc78ed4

STACK_COMMAND: .cxr 0xffffffff8d387640 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a

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

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:21 AM

Posted 19 February 2011 - 06:32 PM

I cannot run backup. cannot run windows update, neither want to know.I have tried to reinstal windows 7 upgrade to do repair, but get the message not enough memory even though this machine has 1Tb disk and about 800 Mb free !

---------

That's disk space. Memory refers to ram.

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 SP!Micky

SP!Micky
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 20 February 2011 - 04:07 AM

Ok, I'll try that but I doubt it will stay running long enough to do this.
This was some other dumps I managed to email to myself if it helps.I also have plenty of ram for win 7 to instal, but it says not, I have tried reseating the ram also tried to run combifix, but it crashes at the end of the first blue bar

Process File : svchost.exe
Event Name : Stopped working
Event Time : 17/02/2011 10:11:24
User Name : All Users
Exception Code : 0xc0000005
Exception Offset : 0xc2940f08
Fault Module Name : StackHash_a7aa
Fault Module Version: 0.0.0.0
Process Path : C:\Windows\system32\svchost.exe
Report File Size : 27,954
Report File Path : C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\AppCrash_svchost.exe_b5b0ae4cf3e6f6462ad07d722dbcc6c3acbfe_0c4b7953
\Report.wer
==================================================




==================================================
Process File : svchost.exe
Event Name : Stopped working
Event Time : 18/11/2010 14:13:47
User Name : All Users
Exception Code : 0xc0000005
Exception Offset : 0x00019207
Fault Module Name : USER32.dll
Fault Module Version: 6.1.7600.16385
Process Path : C:\Windows\system32\svchost.exe
Report File Size : 12,228
Report File Path : C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\AppCrash_svchost.exe_Even_d6ea98964f991b5aed1315f7293c81fc547b25b1_19e204f7\Report.wer
==================================================

==================================================
Process File : regsvr32.exe
Event Name : Stopped working
Event Time : 12/02/2011 23:51:33
User Name : lynne
Exception Code : 0xc0000005
Exception Offset : 0x0001d33d
Fault Module Name : msvcrt.dll
Fault Module Version: 7.0.7600.16385
Process Path : C:\Windows\system32\regsvr32.exe
Report File Size : 10,604
Report File Path : C:\Users\lynne\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_regsvr32.exe_cf37e599

#4 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:21 AM

Posted 20 February 2011 - 08:41 AM

If you think the ram may be the problem you can check it. To check the ram, download memtest (http://www.memtest.org/). Burn it to a cd, make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#5 SP!Micky

SP!Micky
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 20 February 2011 - 02:31 PM

Hi again,
No I don't think it is the ram, tried it in my machine, seems fine, got a horrible feeling could be an infection, but haven't enough timne to run combofix before shutdown, any ideas ??????????????????????????????////

#6 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:21 AM

Posted 20 February 2011 - 02:32 PM

Post in the Am I Infected forum on this site

#7 caperjac

caperjac

  • Members
  • 1,649 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NS. CAN
  • Local time:12:21 PM

Posted 20 February 2011 - 03:20 PM

hi, might i suggest turning on the hidden win7 admin acct and see if you can run virus/trojan scan from it .follow one of the howto's in this link
http://www.sevenforums.com/tutorials/507-built-administrator-account-enable-disable.html

i also suggest running malwarebytes first ,and only run combofix under the guidance of one of the pro's at am i infected section .save malwarebytes logs for them to look at ,

http://download.cnet.com/Malwarebytes-Anti-Malware/3000-8022_4-10804572.html?part=dl-10804572&subj=dl&tag=button

Edited by caperjac, 20 February 2011 - 03:21 PM.

My answers are my opinion only,usually


#8 SP!Micky

SP!Micky
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:21 AM

Posted 21 February 2011 - 03:32 PM

Hi, as adviswd I managed to run blue screen viewer, here is the result, hope this helps !!!!!!!!!!!!!!!!!!!!!!

==================================================
Dump File : 022011-91853-01.dmp
Crash Time : 20/02/2011 21:45:33
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82e494a0
Parameter 3 : 0x8d39b774
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+23e4a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022011-91853-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 140,064
==================================================

==================================================
Dump File : 022011-76549-01.dmp
Crash Time : 20/02/2011 20:38:46
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82e424a0
Parameter 3 : 0x8d197774
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+23e4a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022011-76549-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 147,472
==================================================

==================================================
Dump File : 021711-149994-01.dmp
Crash Time : 17/02/2011 22:53:12
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82e534a0
Parameter 3 : 0x8ca4f774
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+23e4a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021711-149994-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 144,232
==================================================

==================================================
Dump File : 021711-69685-01.dmp
Crash Time : 17/02/2011 22:03:31
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82d043e1
Parameter 3 : 0x8d39ba60
Parameter 4 : 0x8d39b640
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+bb3e1
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021711-69685-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 144,232
==================================================

==================================================
Dump File : 021711-107952-01.dmp
Crash Time : 17/02/2011 21:56:06
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82d0f3e1
Parameter 3 : 0x8d58fa60
Parameter 4 : 0x8d58f640
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+bb3e1
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021711-107952-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 144,232
==================================================

==================================================
Dump File : 021711-120042-01.dmp
Crash Time : 17/02/2011 21:49:48
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x000000a0
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82c8186c
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4681b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021711-120042-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 144,232
==================================================

==================================================
Dump File : 021511-52119-01.dmp
Crash Time : 15/02/2011 12:59:55
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82e584a0
Parameter 3 : 0x8d5cb774
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+23e4a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021511-52119-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 144,232
==================================================

==================================================
Dump File : 091610-33087-01.dmp
Crash Time : 16/09/2010 18:30:51
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0x00000020
Parameter 2 : 0xc000009d
Parameter 3 : 0x87f347c4
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+832f4
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\091610-33087-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 150,408
==================================================

==================================================
Dump File : 091310-35271-01.dmp
Crash Time : 13/09/2010 14:07:09
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc07f44c0
Parameter 2 : 0xc000009d
Parameter 3 : 0x38fdc8c0
Parameter 4 : 0xfe898320
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+dcd10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\091310-35271-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 150,408
==================================================

==================================================
Dump File : 091210-56019-01.dmp
Crash Time : 12/09/2010 11:15:53
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0x00000020
Parameter 2 : 0xc000009d
Parameter 3 : 0x87ddf044
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+832f4
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\091210-56019-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 150,408
==================================================




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users