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

New mobo and CPU - BSOD


  • Please log in to reply
13 replies to this topic

#1 timsbleung

timsbleung

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 15 July 2009 - 10:17 AM

Hey guys, I recently replaced my CPU and motherboard, and soon after started getting BSOD's and app crashes

BSOD's happen mostly when I'm doing something heavier, like maybe a game, but firefox crashes quite often too.


Right now I'm running the Intel E8400, an asus p5ql-pro motherboard, and some corsair ram

The stop messages i'm getting are mostly 8e 0a and 7d's
I read around and it seemed like it might have been a memory problem, but my memtest86+ came up fine
I also read that my mobo is pretty picky about RAM, but my memory (Corsair VS1GB667D2) is actually on the "qualified" list

So I was wondering what else could be causing these problems?
Just let me know if I need to post up anything more

BC AdBot (Login to Remove)

 


#2 andrewww

andrewww

  • Members
  • 111 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Glasgow
  • Local time:06:54 PM

Posted 15 July 2009 - 10:19 AM

I have had faulty RAM and memtest not pick it up. I would borrow a stick for ram from a mate to test it.
Lucy
C2D E6600 @ 2.4, 8GB OCZ Reaper @ 1066, 500GB Barracuda, Powercolor HD4850, Asus P5Q Pro, Corsair TX650, NZXT Lexa Blackline, Windows 7 - Build 7100, Samsung 22" Monitor

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:54 PM

Posted 15 July 2009 - 11:18 AM

How To Use Event Viewer - http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/

You might also start writing down the details of the BSOD screens...and posting same here.

Louis

#4 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 15 July 2009 - 06:57 PM

alright, what information would you need? Just information from the errors? or the minidump analysis?


Thanks for the replies

#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:54 PM

Posted 15 July 2009 - 07:22 PM

If you have the .dmp file analysis, that would be great. It will probably be more specific than the BSOD screen.

Reference: Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Louis

#6 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 17 July 2009 - 08:12 PM

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


Loading Dump File [C:\WINDOWS\Minidump\Mini071809-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jul 18 08:28:42.328 2009 (GMT+8)
System Uptime: 0 days 0:05:38.046
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8054bcc7, b3e4e998, 0}

Probably caused by : klif.sys ( klif+e8cc )

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

1: kd>
1: 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: c0000005, The exception code that was not handled
Arg2: 8054bcc7, The address that the exception occurred at
Arg3: b3e4e998, Trap Frame
Arg4: 00000000

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!ExAllocatePoolWithTag+35f
8054bcc7 390e cmp dword ptr [esi],ecx

TRAP_FRAME: b3e4e998 -- (.trap 0xffffffffb3e4e998)
ErrCode = 00000000
eax=00000004 ebx=89e66000 ecx=00000001 edx=00000003 esi=00000000 edi=00000001
eip=8054bcc7 esp=b3e4ea0c ebp=b3e4ea60 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ExAllocatePoolWithTag+0x35f:
8054bcc7 390e cmp dword ptr [esi],ecx ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: avp.exe

LAST_CONTROL_TRANSFER: from b4b638cc to 8054bcc7

STACK_TEXT:
b3e4ea60 b4b638cc 00000001 00000800 7a626f73 nt!ExAllocatePoolWithTag+0x35f
WARNING: Stack unwind information not available. Following frames may be wrong.
b3e4ec28 b4b6837e 05d9fae0 00000008 001d1008 klif+0xe8cc
b3e4ed00 80579274 000006e4 00000000 00000000 klif+0x1337e
b3e4ed34 8054161c 000006e4 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b3e4ed34 7c90e4f4 000006e4 00000000 00000000 nt!KiFastCallEntry+0xfc
05d9fab0 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
klif+e8cc
b4b638cc ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: klif+e8cc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: klif

IMAGE_NAME: klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49d345f9

FAILURE_BUCKET_ID: 0x8E_klif+e8cc

BUCKET_ID: 0x8E_klif+e8cc

Followup: MachineOwner


klif.sys is apparently a file from kapersky


Here's another

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


Loading Dump File [C:\WINDOWS\Minidump\Mini071709-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jul 17 16:37:08.593 2009 (GMT+8)
System Uptime: 0 days 7:54:12.218
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 80545013, 8f7abce8, 0}

Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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: c000001d, The exception code that was not handled
Arg2: 80545013, The address that the exception occurred at
Arg3: 8f7abce8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!KeUpdateSystemTime+6f
80545013 df ???

TRAP_FRAME: 8f7abce8 -- (.trap 0xffffffff8f7abce8)
ErrCode = 00000000
eax=001bc90d ebx=001bc90d ecx=001bc90e edx=00000000 esi=00000042 edi=3ed80aec
eip=80545013 esp=8f7abd5c ebp=8f7abd64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206
nt!KeUpdateSystemTime+0x6f:
80545013 df ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: Wow.exe

LAST_CONTROL_TRANSFER: from 0048b218 to 80545013

FAILED_INSTRUCTION_ADDRESS:
nt!KeUpdateSystemTime+6f
80545013 df ???

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffff8f7abee0

STACK_COMMAND: dds 8F7ABEE0-0x20 ; kb

STACK_TEXT:
8f7abec0 555dc3fa
8f7abec4 3fecdf0b
8f7abec8 53829d72
8f7abecc bc7dd83b
8f7abed0 b0e743da
8f7abed4 3f5a2849
8f7abed8 24fafe16
8f7abedc bd529ab0 nv4_disp+0x517ab0
8f7abee0 53829d72
8f7abee4 bc7dd83b
8f7abee8 53829d72
8f7abeec bc7dd83b
8f7abef0 b7c2507a nv4_mini+0x65307a
8f7abef4 3eb7b66a
8f7abef8 1fff98c8
8f7abefc 3eba4842
8f7abf00 0ae4a399
8f7abf04 3e70d522
8f7abf08 1fff98c8
8f7abf0c 3eba4842
8f7abf10 00000000
8f7abf14 00000000
8f7abf18 00000000
8f7abf1c 00000000
8f7abf20 00000000
8f7abf24 00000000
8f7abf28 00000000
8f7abf2c 00000000
8f7abf30 00000000
8f7abf34 00000000
8f7abf38 00000000
8f7abf3c 00000000


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80545009 - nt!KeUpdateSystemTime+65
[ 89:81 ]
1 error : !nt (80545009)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption



#7 hamluis

hamluis

    Moderator


  • Moderator
  • 56,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:54 PM

Posted 18 July 2009 - 09:27 AM

Lots of possibilities that I see.

Three items I see highlighted: WoW.exe, your display driver, and Kaspersky.

Each of these employs drivers which could be the root of the problem.

The fact that memory corruption is cited...is a bit misleading, since the video memory could be what is referred to, rather than system RAM.

If it were me, I would remove WoW from the equation, literally...remove it from the system.

Then I would uninstall/reinstall Kaspersky and the video drivers, on the premise that each has become damaged and those files need to be replaced in order for the system to run smoothly.

You say that you replaced the board and CPU...did you do a clean install or simply begin to use the old hard drive (containing old drivers, settings)? If you did the latter, that could be the root cause of your problems.

Changing a Motherboard or Moving Hard Drive - http://www.michaelstevenstech.com/moving_xp.html

Louis

#8 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 19 July 2009 - 08:51 PM

Yes, I did do a clean install

Just went through all the old dumps and also found some blaming other apps like firefox, or media players, etc.... so I'm not sure if apps really is a problem, but I'll reinstalling kapersky and wow and drivers for now and see what happens.

The thing is i'm not just getting BSOD's, I'm also getting abrupt app crashes

As for memory problems, could the problem be with CPU cache?

Edited by timsbleung, 19 July 2009 - 09:10 PM.


#9 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:54 AM

Posted 20 July 2009 - 10:42 PM

Have you check the reported CPU temperatures?

Is it possible the "abrupt" stops are system shut-downs to prevent damage to your CPU?

When installing the mobo +cpu .... did you use thermal paste?

Dumb question .... but ..... ?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 21 July 2009 - 04:33 AM

yeah i did, heats not a problem, I feel the thing and it runs fairly cool

Anyway, after WoW crashed again today, I stopped and actually took a look at the log from that... Looked up the error, and it points to memory as well.


Looks like I might just have to get some new RAM

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 56,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:54 PM

Posted 21 July 2009 - 07:39 AM

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

MemTest Manual - http://hcidesign.com/memtest/manual.html Outdated, but still useful.

Icrontic Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86

Louis

#12 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 21 July 2009 - 09:05 AM

I did do Memtest86+, and it came up fine
Maybe it's not picking something up, or maybe my RAM just doesn't "get along" with the rest of my computer, I don't know


I suppose I could try tweaking the frequencies and whatnot, but I really don't know what I'm doing in that area

#13 hamluis

hamluis

    Moderator


  • Moderator
  • 56,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:54 PM

Posted 21 July 2009 - 11:07 AM

Did you read the suggested time for running Memtest?

How long did you run it?

You didn't have time to make a complete pass from the time that I posted, by my calculations.

Louis

#14 timsbleung

timsbleung
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:54 AM

Posted 22 July 2009 - 04:19 AM

running memtest was one of the first things i did when I started getting errors

But anyway, I just again let it run for well over five hours (16 passes), and still nothing




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users