Jump to content
N-Europe

Serious BSOD, pissing me off.

dabookerman

By dabookerman
in General Chit Chat

 Share

Recommended Posts

dabookerman Newbie

dabookerman

Posted
Posted

Before i used to get ati related BSOD, but they seem to be gone now.

Now im getting new BSODs:

 

heres the dump i got today:

 

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

Executable search path is:

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp1_rtm.050324-1447

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0

Debug session time: Wed Aug 16 15:27:20.796 2006 (GMT+1)

System Uptime: 0 days 4:27:07.759

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

.......

*** WARNING: Unable to verify checksum for hal.dll

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 9C, {4, fffff80000123bc0, b2000000, 70f0f}

 

Unable to load image AmdK8.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for AmdK8.sys

*** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

Probably caused by : AmdK8.sys ( AmdK8+4081 )

 

 

 

a few days ago i got this BSOD:

 

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

Executable search path is:

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp1_rtm.050324-1447

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0

Debug session time: Tue Aug 15 12:52:02.984 2006 (GMT+1)

System Uptime: 0 days 1:36:08.937

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

......

*** WARNING: Unable to verify checksum for hal.dll

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 9C, {4, fffff80000123bc0, b2000000, 70f0f}

 

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+77 )

 

Followup: MachineOwner

 

 

 

 

Ive done the Windows Memory Diagnostics Tool test, and there were no errors. So i dont know what to do now, this is starting to happen more and more frequently at the most random times.

Edit/Delete Message

Ollie Newbie

Ollie

Posted
Posted

Booker, could I ask you for some more info please. What OS are you running? Have you made any hardware/software changes lately (or since this started happening) also some basic system specs such as CPU/RAM types/speeds/sizes etc.

 

EDIT - Done some research, so you are running XP X64 edition then? Found this on another forum:

 

Kept getting:

 

File AMD64\ntkrnlmp.exe could not be loaded...

 

Setting BIOS to 'Default Settings' or 'Optimal Settings' fixed the problem for me.

 

[After I updated the MB bios, XP stopped loading. Required a repair-install of XP 64-bit. Trying to load XP install CD I kept getting 'File AMD64\ntkrnlmp.exe could not be loaded...'. Resetting bios settings fixed the problem for me.]

 

So you should make sure you have the latest version of your motherboard bios, and try setting your bios to use default or optimal settings?

 

EDIT 2 - Having said that, after a bit more research, could you provide me some information from your event log please? To get it, go to control panel, double click admin tools, open 'Event Viewer' click the 'System' view on the left, when your system BSOD's it creates a system event 1001 or 1003, can you provide the latest 5-10 of these? If you double click on it it will give you the details of the event, you can then copy these to the clip board:

 

copytoclipboard.gif

dabookerman Newbie

dabookerman

Posted
  • Author
Posted

Hey man, thanks for the help so far, heres the system events:

 

Event Type: Information

Event Source: Save Dump

Event Category: None

Event ID: 1001

Date: 16/08/2006

Time: 18:41:41

User: N/A

Computer: ADAM-STF9E4BNJE

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000004, 0xfffff80000123bc0, 0x00000000b2000000, 0x0000000000070f0f). A dump was saved in: C:\WINDOWS\Minidump\Mini081606-02.dmp.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Event Type: Information

Event Source: Save Dump

Event Category: None

Event ID: 1001

Date: 16/08/2006

Time: 15:28:35

User: N/A

Computer: ADAM-STF9E4BNJE

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000004, 0xfffff80000123bc0, 0x00000000b2000000, 0x0000000000070f0f). A dump was saved in: C:\WINDOWS\Minidump\Mini081606-01.dmp.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

This was the previous error i used to get, i dont get them anymore, they were ATI related

 

Event Type: Error

Event Source: System Error

Event Category: (102)

Event ID: 1003

Date: 25/07/2006

Time: 21:50:25

User: N/A

Computer: ADAM-STF9E4BNJE

Description:

Error code 000000000000009c, parameter1 0000000000000004, parameter2 fffff80000123bc0, parameter3 00000000b2000000, parameter4 0000000000070f0f.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 53 79 73 74 65 6d 20 45 System E

0008: 72 72 6f 72 20 20 45 72 rror Er

0010: 72 6f 72 20 63 6f 64 65 ror code

0018: 20 30 30 30 30 30 30 30 0000000

0020: 30 30 30 30 30 30 30 39 00000009

0028: 63 20 20 50 61 72 61 6d c Param

0030: 65 74 65 72 73 20 30 30 eters 00

0038: 30 30 30 30 30 30 30 30 00000000

0040: 30 30 30 30 30 34 2c 20 000004,

0048: 66 66 66 66 66 38 30 30 fffff800

0050: 30 30 31 32 33 62 63 30 00123bc0

0058: 2c 20 30 30 30 30 30 30 , 000000

0060: 30 30 62 32 30 30 30 30 00b20000

0068: 30 30 2c 20 30 30 30 30 00, 0000

0070: 30 30 30 30 30 30 30 37 00000007

0078: 30 66 30 66 0f0f

 

 

 

 

 

i also updated the Bios, and i will check the settings of the mobo, cheers

 

 

 

EDIT: OK, so i updated the bios, the pc crashes twice upon start up, now its working fine now, but god knows when it will crash next, heres the crash dump:

 

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini081706-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

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

Executable search path is:

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp1_rtm.050324-1447

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0

Debug session time: Thu Aug 17 12:47:20.265 2006 (GMT+1)

System Uptime: 0 days 0:00:37.234

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

.

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck D1, {81, 2, 0, fffffadfe7d141f8}

 

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+207 )

 

Followup: MachineOwner

---------

 

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000081, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffffadfe7d141f8, address which referenced memory

 

Debugging Details:

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

 

 

READ_ADDRESS: 0000000000000081

 

CURRENT_IRQL: 2

 

FAULTING_IP:

+fffffadfe7d141f8

fffffadf`e7d141f8 0000 add [rax],al

 

CUSTOMER_CRASH_COUNT: 2

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

LAST_CONTROL_TRANSFER: from fffff8000104fef4 to fffff800010501d0

 

STACK_TEXT:

fffffadf`e4c2b9f8 fffff800`0104fef4 : 00000000`0000000a 00000000`00000081 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffffadf`e4c2ba00 fffff800`0104ef07 : 00000000`0000003d fffffadf`e307cb2b fffffadf`e798b000 fffffadf`e7213000 : nt!KiBugCheckDispatch+0x74

fffffadf`e4c2bb80 fffffadf`e7d141f8 : fffff800`010530d4 00000000`00000000 00000000`00000000 fffffadf`e4337820 : nt!KiPageFault+0x207

fffffadf`e4c2bd18 fffff800`010530d4 : 00000000`00000000 00000000`00000000 fffffadf`e4337820 fffffadf`e7c34488 : 0xfffffadf`e7d141f8

fffffadf`e4c2bd20 fffff800`01071950 : fffffadf`e486b180 fffffadf`e486b180 00000000`00000000 fffffadf`e4873680 : nt!KiRetireDpcList+0x14b

fffffadf`e4c2bdb0 fffff800`013fc1d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x50

fffffadf`e4c2bde0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!KiPageFault+207

fffff800`0104ef07 488d05f22f0000 lea rax,[nt!ExpInterlockedPopEntrySListResume (fffff80001051f00)]

 

FAULTING_SOURCE_CODE:

 

 

SYMBOL_STACK_INDEX: 2

 

FOLLOWUP_NAME: MachineOwner

 

SYMBOL_NAME: nt!KiPageFault+207

 

MODULE_NAME: nt

 

IMAGE_NAME: ntkrnlmp.exe

 

DEBUG_FLR_IMAGE_TIMESTAMP: 42436123

 

FAILURE_BUCKET_ID: X64_0xD1_nt!KiPageFault+207

 

BUCKET_ID: X64_0xD1_nt!KiPageFault+207

 

Followup: MachineOwner

---------

 

 

Also, i think i should give my specs:

 

Mobo: Asus A8R MVP

CPU: AMD X2 4400+

1GIG Ram crucial pc3200

Ollie Newbie

Ollie

Posted
Posted

Ok, leave it with me, I'll churn through that lot and get back to you as soon as I can. Just building my new PC right now, exciting!

Bogbas Newbie

Bogbas

Posted
Posted

I think that you either have a faulty piece of hardware, or your windows installation is corrupt. This just started a while ago? Or has it been happening since you got your pc? I'd recommend format/reinstall.

 

And why 64bit windows? What I've heard it sucks mostly...

Guest Jordan

Guest Jordan

Posted
Posted

x64 is pretty good i find.

Infact, the most BSOD's occur in x64 because people don't use propper drivers or offically signed ones.

dabookerman Newbie

dabookerman

Posted
  • Author
Posted
I think that you either have a faulty piece of hardware, or your windows installation is corrupt. This just started a while ago? Or has it been happening since you got your pc? I'd recommend format/reinstall.

 

And why 64bit windows? What I've heard it sucks mostly...

 

Yeah, i was gonna use vista x64, but i aint gonna use that now.

Bogbas Newbie

Bogbas

Posted
Posted

Maybe people wouldn't need to use unofficial and improper drivers if the manufacturer would make drivers that actually worked ;)

 

edit: I'll probably move to vista when it's succesor launches. At the moment can't see the point in spending few hundred euros for directx10.

Guest Jordan

Guest Jordan

Posted
Posted

I'm not moving to Vista till i really really need to...

I'm quite happy with XP x64.

dabookerman Newbie

dabookerman

Posted
  • Author
Posted

right i am certain all these problems is because of windows xp x64 edition, is there a way to downgrade to 32 bit windows?

 

edit: it crashed again btw

 

EDIT!!!!: Whats an IWAM account?!?!?!?!

Bogbas Newbie

Bogbas

Posted
Posted
right i am certain all these problems is because of windows xp x64 edition, is there a way to downgrade to 32 bit windows?

 

edit: it crashed again btw

 

EDIT!!!!: Whats an IWAM account?!?!?!?!

 

I don't think that downgrading is possible without paying. (legally...)

 

And IWAM account seems to be something that comes with IIS. Apparently it's some server stuff. Where does the IWAM show up?

dabookerman Newbie

dabookerman

Posted
  • Author
Posted

http://www.eventid.net/display.asp?eventid=10020&eventno=5388&source=DCOM&phase=1

 

that seems to be the catylist of the crashes, i check the event logs, and they always appear before the mini dumps.

 

anyhoo, once my HDD arrives, i will back everything up, make a list of all the shit i have installed on the windows partition, and its time to get rid of this sonofabitch

 

Right consider me a 32bitter, i finally get to use programs and hardware that i couldnt before, in yo face x64 biatch

 Share
Go to topic listing
×
×
  • Create New...