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 After scanning with Nod32.


  • Please log in to reply
No replies to this topic

#1 ExTaCy1337

ExTaCy1337

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:56 AM

Posted 19 March 2012 - 08:57 AM

Hello guys, nice forum you've got here :)
I have a little problem , I searched google and found this forum after getting a BSOD while using my pc (Browser (Firefox with like 10 Tabs LOL :P, email and some programs, also NOD32 was scanning for viruses, not any games or something [I am saying those which might identify a ram error]) and I got the sound like bzzzzzzzzzzzzz :P ahahaah, and the screen become like the monitor got a punch and broke :>.
So here is my dmp file ...



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


Loading Dump File [C:\Users\ExTaCy1337\Desktop\031912-46234-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x83053000 PsLoadedModuleList = 0x8319c4d0
Debug session time: Mon Mar 19 15:25:08.338 2012 (UTC + 2:00)
System Uptime: 0 days 1:11:21.010
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 801df000, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!ExMapHandleToPointer+5 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801df000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 832af75d to 83293fa6

STACK_TEXT:
be011000 832af75d 000014a0 87b38510 00000000 nt!ExMapHandleToPointer+0x5
be011024 868c9289 000014a0 be01106c 87b38510 nt!PsLookupThreadByThreadId+0x29
WARNING: Frame IP not in any known module. Following frames may be wrong.
be011028 00000000 be01106c 87b38510 00000000 0x868c9289


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExMapHandleToPointer+5
83293fa6 51 push ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExMapHandleToPointer+5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79850

FAILURE_BUCKET_ID: 0x7f_8_nt!ExMapHandleToPointer+5

BUCKET_ID: 0x7f_8_nt!ExMapHandleToPointer+5

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

Edited by ExTaCy1337, 19 March 2012 - 09:08 AM.


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users