Jump to content

BSoD problems :'(


Sars!

Recommended Posts

Hey there,

I feel like smashing my computer... xD

So, well, not difficult. I get a BSoD!

This is teh error message (I get others too, but this one is most frequent):

0x7F (0x0D, 0x00, 0x00, 0x00)

I'm really out of ideas. Here's what I tried already:

-Upgraded windows XP to windows Vista Ultimate

-Put this inside my case:

ventilator.jpg

-Reinstall graphic drivers, audio drivers, directx

-Unscrew my processor and graphic card (took out everything and put everything back in)

-Virus-scans

Now, I don't get this BSoD while playing games (sometimes I do, but mostly my games work perfect) and I don't get it while in Safe Mode.

Here's my system specs:

P5GDC Deluxe Asus (MoBo)

Intel P4 HT540 3.2 Ghz

Geforce 7900 GT Sonic 512 mb (palit)

2 x 1GB ramm (I don't know, but I think it's corsair)

200 gb hard disk S-ATA

460 Watt tagan powersupply

X-FI extremegamer Soundcard

There's a bootlog as attachment.

I hope anyone could help :)

Grtz,

Sars!

EDIT:

And this is just strange:

untitledap4.png

ntbtlog.rar

Edited by Sars!
Link to comment
Share on other sites


Regarding your first issue, I'd say it's due to bad RAM. Have you tried to run a memtest86 on it? As for the second issue, you see 2 processors because it is running in hyperthreading (1 physical processor and a "virtual" one).

Link to comment
Share on other sites

Well, I think perhaps a dump is in order here. The 0x0D parameter in the 0x7F bugcheck means that the OS hit an exception not covered by some other exception handler, which means that it was likely a protection fault that pertains to access violations for applications or drivers that caused the issue. While it's still possible that it's hardware, the fact that it was a 0x0D means it's at least more likely to be poorly written driver software than an actual hardware fault. What's running on that box, btw? :)

Link to comment
Share on other sites

I'm pretty sure it's not the memory because I just put new in it. Before it had 2 x 512 twinmos, and it gave the same bsod. I also thought it was the memory, that's why I bought new :)

I'll do the dump thing though.

Thanx for the replys already,

Sars!

EDIT:

Could it be possible that my computer already automaticaly created a dump? Because when I get the BSoD, in the bottom, a loading thing comes, with 'writing memory dump' or something like that.

Ow, I can't put it as an attachment because its over 200 MB :o

I think I'll just make a new one, 'cus that's strange, isn't it?

Grtz,

Sars!

EDIT:

Ok, I didn't realize I needed to open the MEMORY.dmp with the debugging tools xD

Anyways, this is what I got:

Microsoft ® Windows Debugger Version 6.7.0005.0

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;c:\websymbols

Executable search path is:

Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6000.16386.x86fre.vista_rtm.061101-2205

Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ab0

Debug session time: Wed Jun 27 09:32:03.156 2007 (GMT+2)

System Uptime: 0 days 0:05:57.778

Loading Kernel Symbols

....................................................................................................

.................................................................................

Loading User Symbols

Loading unloaded module list

.........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {d, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

Followup: MachineOwner

---------

And this is a bit completer one:

UNEXPECTED_KERNEL_MODE_TRAP (7f)

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: 0000000d, EXCEPTION_GP_FAULT

Arg2: 00000000

Arg3: 00000000

Arg4: 00000000

Debugging Details:

------------------

BUGCHECK_STR: 0x7f_d

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 8

LAST_CONTROL_TRANSFER: from 81c6b720 to 81c49c47

STACK_TEXT:

81ce9aec 81c6b720 badb0d00 84d1f00c 8551ce00 nt!KiSystemFatalException+0xf

81ce9b60 81c6bc97 00000020 00000010 81c86c1a nt!EtwpGetPerfCounter+0x2

81ce9b90 81c6bf2a 00000020 81ce9bb8 81ce9bd8 nt!EtwpReserveTraceBuffer+0xce

81ce9be4 81c731e3 81ce9c10 00000000 00000002 nt!EtwpLogKernelEvent+0x1b1

81ce9c30 81c74f2b 00000f43 20004000 00000008 nt!EtwTraceTimedEvent+0xa5

81ce9c5c 81c370e5 8268ce30 00009200 4cdbf4ee nt!PerfInfoLogInterrupt+0x43

81ce9c94 81c36fc9 81ce9c02 00000092 81ce9d50 nt!KiChainedDispatch2ndLvl+0xd9

81ce9c94 8b5fc41e 81ce9c02 00000092 81ce9d50 nt!KiChainedDispatch+0x29

81ce9d14 8b5fd1af 81cee610 8679b5a4 81c9f3a3 intelppm!C1Halt+0x4

81ce9d20 81c9f3a3 84ca32d8 81cefac0 81cec700 intelppm!C1Idle+0x25

81ce9d50 81c37a82 00000000 0000000e 00000000 nt!PopIdleDefaultHandler+0x239

81ce9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!KiSystemFatalException+f

81c49c47 c3 ret

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiSystemFatalException+f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ad6c

FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f

BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f

Followup: MachineOwner

---------

And this is what Bill says:

NOTE: The Ntkrnlmp.exe file is used only on computers with multiple processors.

Seems I was right with the two processors showing up after all?

Grtz,

Sars!

Edited by Sars!
Link to comment
Share on other sites

Little bump (cause I editted my previous post 3 times, and didn't have a reply since original message)

Grtz,

Sars!

EDIT:

Disabled HyperThreading, did nothing. Ow, and I guess it's normal that there aren't anymore BSoD's, but the computer just restarts?

EDIT:

wooow, I'm 50 minutes (not safemode) on my comp now and it didn't give a bsod. Maybe it's fixed. Not sure yet though

Edited by Sars!
Link to comment
Share on other sites

Well, maybe.

You crashed after doing an EtwpGetPerfCounter from the kernel (nt!), and the next call should/would have been hal!HalGetInterruptTargetInformation - this would have been a call to the processor through the driver it uses - as such, it is possible that it's a problem with the processor hardware, but it's more likely a problem with the intelppm driver from the Intel Chipset software. I can only see what you show in the dump and what I know to be happening with the perf counters in that stack from experience, but that'd be my educated guess from your basic output.

Link to comment
Share on other sites

Yeh, but I don't really think that 'drivers' exist for a processor xD

And if you mean these:

http://www.intel.com/support/chipsets/inf/

I already tried 'em :)

Grtz,

Sars!

ps: It went smooth in normal mode yesterday for about an hour, then it freezed. After reboot, it gave bsod's again.

EDIT:

This is what CPU says (look to the right):

6cpu6at.png

I would like to downclock my cpu, but HOW?

Grtz,

Sars!

Edited by Sars!
Link to comment
Share on other sites

That's pretty warm for even an Intel CPU - perhaps you can get into the BIOS and reduce the clock speed, but you'd have to check the motherboard manual, as they're all different about that sort of thing.

If you leave the system off for a few hours and turn it back on, does it run without crashing for awhile, and does the temp keep going up?

Link to comment
Share on other sites

Well, it's pretty strange.

I changed the position of my fans and now the temp gets maxed at 65 °C. I'm not sure though, but I get a lot of different BSoD's now too.

I hope anyone can still help, though, I think my computer is at his end.

Grtz,

Sars!

Link to comment
Share on other sites

Regarding your first issue, I'd say it's due to bad RAM. Have you tried to run a memtest86 on it? As for the second issue, you see 2 processors because it is running in hyperthreading (1 physical processor and a "virtual" one).

May be a bad processor or the Vcore isn't set properly.

The STOP: 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP BSOD has been documented by a motherboard manufacturer's web site to be caused by Vcore issues. You may be required to flash the BIOS for the problem to be solved.

Edited by RJARRRPCGP
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...