bleuscreen problem

Lars

Member
i have a problem sometimes out of nowere i get the bluescreen and my computer restarts it is very annoying it happened twice when i tryd to scan my computer whit avira, so it looks like i cannot compleet my scan. it is happening qwuit often. this is the message i get after it restarts(srry some things are in dutch):
------------------------------------------------------------
Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.0.6001.2.1.0.768.3
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 77
BCP1: 00000001
BCP2: 00000000
BCP3: 00000000
BCP4: AAC07B78
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\Mini070811-01.dmp
C:\Users\lars\AppData\Local\Temp\WER-80168-0.sysdata.xml
C:\Users\lars\AppData\Local\Temp\WER735B.tmp.version.txt

Lees onze privacyverklaring:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0413
----------------------------------------------------------
does anyone know what i can do and how to fix this? any help welcome and thanks in advance
 

My Computer

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
isnt this the iformation u need?:

Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.0.6001.2.1.0.768.3
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 77
BCP1: 00000001
BCP2: 00000000
BCP3: 00000000
BCP4: AAC07B78
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\Mini070811-01.dmp
C:\Users\lars\AppData\Local\Temp\WER-80168-0.sysdata.xml
C:\Users\lars\AppData\Local\Temp\WER735B.tmp.version.txt

Lees onze privacyverklaring:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0413
 

My Computer

Sorry it is not, download the information from your computer as directed.
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Stop 0000000008E

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

Code:
 icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2 (1).zip\Windows_NT6_BSOD_jcgriff2\Mini070811-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18538.x86fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0x82034000 PsLoadedModuleList = 0x82141930
Debug session time: Fri Jul  8 07:46:49.762 2011 (GMT-4)
System Uptime: 0 days 1:05:52.945
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
...
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c002001c, The exception code that was not handled
Arg2: 8a32086c, The address that the exception occurred at
Arg3: aaf3f2e8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc002001c - The remote procedure call failed and did not execute.
FAULTING_IP: 
msrpc!RpcpRaiseException+e
8a32086c cc              int     3
TRAP_FRAME:  aaf3f2e8 -- (.trap 0xffffffffaaf3f2e8)
ESP EDITED! New esp=aaf3f698
ErrCode = 00000000
eax=c002001c ebx=00000001 ecx=a8cc4978 edx=84205054 esi=aaf3f708 edi=aaf3f6dc
eip=8a32086c esp=aaf3f35c ebp=aaf3f698 iopl=0         nv up ei ng nz na po nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000282
msrpc!RpcpRaiseException+0xe:
8a32086c cc              int     3
Resetting default scope
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 8a32087f to 8a32086c
STACK_TEXT:  
aaf3f698 8a32087f c002001c aaf3f6b8 8a32fc8a msrpc!RpcpRaiseException+0xe
aaf3f6a4 8a32fc8a c002001c 00000000 a8faab00 msrpc!RpcRaiseException+0xd
aaf3f6b8 8a337cf5 aaf3f708 ad6ed070 8a330bd2 msrpc!NdrSendReceive+0x21
aaf3f6c4 8a330bd2 11b31cea 87489df8 00000000 msrpc!NdrpSendReceive+0x9
aaf3faa4 8a4ec0f3 8a4f8058 8a4f43c8 aaf3fac4 msrpc!NdrClientCall2+0xfe
aaf3fabc 8a4fc51a a8faab00 912654c0 00000000 fwpkclnt!FwppProxyTransactionBegin+0x19
aaf3fad4 aa1b62c2 8778cf28 00000000 87489df8 fwpkclnt!FwpmTransactionBegin0+0x50
aaf3fb0c aa1b734b 00000000 aa1b318e 00000000 mpsdrv!MpsGetFwpAuthData+0x1b02
aaf3fb14 aa1b318e 00000000 aa1b1922 875c4318 mpsdrv!MpsDeinitializeFwp+0x3b
aaf3fb1c aa1b1922 875c4318 87489df8 87489e08 mpsdrv!_allmul+0x100
aaf3fb34 aa1b1b9c 875c4318 87489df8 875c4318 mpsdrv!MpsDispatchClose+0x42
aaf3fb48 8207a1f1 875c4318 87489df8 874cfdb8 mpsdrv!MpsIoLayerDispatchIrp+0x5c
aaf3fb60 822293a8 00000000 00000000 874cfda0 nt!IofCallDriver+0x63
aaf3fba4 82224d7b 874cfdb8 82008110 874cfda0 nt!IopDeleteFile+0x178
aaf3fbc0 820a0db2 874cfdb8 00000000 875cf380 nt!ObpRemoveObjectRoutine+0x13d
aaf3fbe8 822254df a8f6d418 875cf380 a8f6d418 nt!ObfDereferenceObject+0xa1
aaf3fc28 8224db89 a8cc7588 a8f6d418 875b5948 nt!ObpCloseHandleTableEntry+0x24e
aaf3fc58 8224d4fc a8cc7588 aaf3fc6c 875b5948 nt!ExSweepHandleTable+0x5f
aaf3fc78 82240631 638bb464 877a99b8 c000001d nt!ObKillProcess+0x54
aaf3fcdc 821f3fbf c000001d 875cf380 875cf301 nt!PspExitThread+0x5b6
aaf3fcf4 820ae2f8 877a99b8 aaf3fd20 aaf3fd2c nt!PsExitSpecialApc+0x22
aaf3fd4c 8208ba46 00000001 00000000 aaf3fd64 nt!KiDeliverApc+0x1dc
aaf3fd4c 779d96f4 00000001 00000000 aaf3fd64 nt!KiServiceExit+0x56
WARNING: Frame IP not in any known module. Following frames may be wrong.
000afa44 00000000 00000000 00000000 00000000 0x779d96f4
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
msrpc!RpcpRaiseException+e
8a32086c cc              int     3
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  msrpc!RpcpRaiseException+e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: msrpc
IMAGE_NAME:  msrpc.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  47918f1f
FAILURE_BUCKET_ID:  0x8E_msrpc!RpcpRaiseException+e
BUCKET_ID:  0x8E_msrpc!RpcpRaiseException+e
Followup: MachineOwner

The most likely cause of this problem is a driver, but there are other possilbiites. I would like to rule out those possibilites, before suggesting a driver test.
Please
Update to latest SP, you still have SP!
Make an anti virus scan and and download and make a full and updated scan with malwarebytes.
Take a memory test. Run for 8 passes then test each stick for 6 passes.
http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/
Be sure that your BIOS is up to date.

There were three reports, two agreed, as above, the third had a different cause. Memory
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\Mini070811-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18538.x86fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0x8200e000 PsLoadedModuleList = 0x8211b930
Debug session time: Fri Jul  8 06:40:06.787 2011 (GMT-4)
System Uptime: 0 days 18:31:02.389
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {1, 0, 0, aac07b78}
Probably caused by : memory_corruption ( nt!MiInPageSingleKernelStack+1f4 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000000, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: aac07b78, address of signature on kernel stack
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR:  0x77_1
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 82042ab8 to 820c97af
STACK_TEXT:  
80784cc4 82042ab8 00000077 00000001 00000000 nt!KeBugCheckEx+0x1e
80784d38 82042840 8810f030 80784d58 00000000 nt!MiInPageSingleKernelStack+0x1f4
80784d6c 82049354 8810f0a0 00000000 80784dc0 nt!KiInSwapKernelStacks+0x43
80784d7c 821b66d9 00000000 4df71673 00000000 nt!KeSwapProcessOrStack+0x83
80784dc0 8209d716 820492d1 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiInPageSingleKernelStack+1f4
82042ab8 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiInPageSingleKernelStack+1f4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb715d8
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0x77_1_nt!MiInPageSingleKernelStack+1f4
BUCKET_ID:  0x77_1_nt!MiInPageSingleKernelStack+1f4
Followup: MachineOwner
---------
 
Last edited:

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT

My Computer

System One

  • Manufacturer/Model
    Lenovo Thinkpad T400
    CPU
    Intel Mobile Core 2 Duo P8700 @ 2.53GHz
    Motherboard
    LENOVO 64734VM
    Memory
    2.00GB Single-Channel DDR3 @ 531MHz
    Graphics Card(s)
    Intel Mobile Intel 4 Series Express Chipset Family
    Sound Card
    Conexant 20561 SmartAudio HD
    Monitor(s) Displays
    15 inch
    Screen Resolution
    1280 x 800
    Hard Drives
    1x 180GB Intel 530 series SSD
    1 x 120GB Hitachi 5400rmp
    1 x 650GB Western Digital Elements 5400rpm
    1x 1Tb Western Digital Elements 5400rpm
    Internet Speed
    Medium for New Zealand
    Other Info
    Weakest part of my computer is the graphics chipset.
    Only ever used a laptop.
    Also use USB Freeview TV Card
    Lenovo Docking Station
    External Speakers
    Other bits a pieces as needed
Ok the reports are now done. Be sure to ask any questions that you may have. Please note the two different reports. I am going with 8E, but cannot ignore the other.
First thing, update to most current SP
Then take the virus and malware test. Malware can be the cause of the problem seen in the first report.
Then make the SFC as mentioned above,
Then take the memory test as suggested by the second report.
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Back
Top