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

I re-installed windows because of seemingly random reboots...still a problem


  • Please log in to reply
25 replies to this topic

#1 jmillerdls

jmillerdls

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 05:49 AM

Was having reboots about every 3 hours. They seemed to be at random, and after posting on a half dozen forums and not finding any help, I decided to re-install windows and start from scratch.

This is after buying new RAM and removing a sound card and nic card and switching to on board for both of those.

So, here I am...and I'm still crashing regularly. Does it pretty much have to be the motherboard at this point? I mean, what else could possibly explain this? I'll post the minidumps, hopefully someone can find something I can do. I'm desperate for any help.

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:49 AM

Posted 01 November 2008 - 06:04 AM

Please use this mini-guide ( http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/ ) to perform an analysis of the minidump files and post your results here for us to have a look at.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 06:11 AM

Yeah...I had this problem last time. No matter what I did, it would say that I didn't have the right symbols and therefore would not give me anything helpful. On another forum when I posted them in a zip, I got some responses about what they said, so I thought I could do that here (given that I lost all my bookmarks and can't find that other site now).

#4 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 06:33 AM

Alright, I decided to try it anyway, even though it was just another source of frustration before the re-install...and sure enough, it seems to work.

I guess I should just cut and paste the results of them? They are all different, which seems insane.




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


Loading Dump File [C:\WINDOWS\Minidump\Mini110108-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Nov 1 05:37:56.751 2008 (GMT-5)
System Uptime: 0 days 1:13:01.604
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : ipsec.sys ( ipsec!IPSecHandlePacket+8 )

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: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 00000000 to b6d67388

STACK_TEXT:
fffffffc 00000000 00000000 00000000 00000000 ipsec!IPSecHandlePacket+0x8


STACK_COMMAND: kb

FOLLOWUP_IP:
ipsec!IPSecHandlePacket+8
b6d67388 53 push ebx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ipsec!IPSecHandlePacket+8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ipsec

IMAGE_NAME: ipsec.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

FAILURE_BUCKET_ID: 0x7f_8_ipsec!IPSecHandlePacket+8

BUCKET_ID: 0x7f_8_ipsec!IPSecHandlePacket+8

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




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


Loading Dump File [C:\WINDOWS\Minidump\Mini110108-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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Nov 1 04:24:18.466 2008 (GMT-5)
System Uptime: 0 days 2:38:23.986
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {54b6976a, 2, 1, 80555fe7}

Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultStack+28e7 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 54b6976a, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80555fe7, address which referenced memory

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


WRITE_ADDRESS: 54b6976a

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiDoubleFaultStack+28e7
80555fe7 808d6a97b65460 or byte ptr [ebp+54B6976Ah],60h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 00000000 to 80555fe7

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nt!KiDoubleFaultStack+0x28e7


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultStack+28e7
80555fe7 808d6a97b65460 or byte ptr [ebp+54B6976Ah],60h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiDoubleFaultStack+28e7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a401b1

FAILURE_BUCKET_ID: 0xA_W_nt!KiDoubleFaultStack+28e7

BUCKET_ID: 0xA_W_nt!KiDoubleFaultStack+28e7

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

#5 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 06:35 AM

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


Loading Dump File [C:\WINDOWS\Minidump\Mini103108-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Sat Nov 1 00:13:36.468 2008 (GMT-5)
System Uptime: 0 days 0:12:54.181
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image ha10kx2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, b841ee71, f78e2854, f78e2550}

Probably caused by : ha10kx2k.sys ( ha10kx2k+16e71 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: b841ee71, The address that the exception occurred at
Arg3: f78e2854, Exception Record Address
Arg4: f78e2550, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
ha10kx2k+16e71
b841ee71 ff7608 push dword ptr [esi+8]

EXCEPTION_RECORD: f78e2854 -- (.exr 0xfffffffff78e2854)
ExceptionAddress: b841ee71 (ha10kx2k+0x00016e71)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0008000e
Attempt to read from address 0008000e

CONTEXT: f78e2550 -- (.cxr 0xfffffffff78e2550)
eax=00080006 ebx=00000000 ecx=b840b350 edx=ba725a44 esi=00080006 edi=00000000
eip=b841ee71 esp=f78e291c ebp=00000008 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210296
ha10kx2k+0x16e71:
b841ee71 ff7608 push dword ptr [esi+8] ds:0023:0008000e=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 0008000e

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 00080006 to b841ee71

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78e2918 00080006 882048f8 b841303c 00080006 ha10kx2k+0x16e71
f78e291c 882048f8 b841303c 00080006 882048f8 0x80006
f78e2920 b841303c 00080006 882048f8 f78e2b4c 0x882048f8
f78e2924 00080006 882048f8 f78e2b4c 00000000 ha10kx2k+0xb03c
f78e2928 882048f8 f78e2b4c 00000000 b8412fd4 0x80006
f78e292c f78e2b4c 00000000 b8412fd4 882048f8 0x882048f8
f78e2930 00000000 b8412fd4 882048f8 b8413247 0xf78e2b4c


FOLLOWUP_IP:
ha10kx2k+16e71
b841ee71 ff7608 push dword ptr [esi+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ha10kx2k+16e71

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ha10kx2k

IMAGE_NAME: ha10kx2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3c9aaed0

STACK_COMMAND: .cxr 0xfffffffff78e2550 ; kb

FAILURE_BUCKET_ID: 0x7E_ha10kx2k+16e71

BUCKET_ID: 0x7E_ha10kx2k+16e71

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

#6 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 06:36 AM

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


Loading Dump File [C:\WINDOWS\Minidump\Mini103108-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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Sat Nov 1 00:00:07.515 2008 (GMT-5)
System Uptime: 0 days 0:05:42.218
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {14, 6, 0, ba8733d0}

Probably caused by : nv4_mini.sys ( nv4_mini+533d0 )

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

0: 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: 00000014, memory referenced
Arg2: 00000006, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ba8733d0, address which referenced memory

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


READ_ADDRESS: 00000014

CURRENT_IRQL: 6

FAULTING_IP:
nv4_mini+533d0
ba8733d0 397908 cmp dword ptr [ecx+8],edi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from ba8733f9 to ba8733d0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8055822c ba8733f9 0000000c 00000009 00000001 nv4_mini+0x533d0
80558250 ba87344a 89a354e8 00000009 00000001 nv4_mini+0x533f9
80558274 ba873493 8991b640 00000009 ba8f0fdf nv4_mini+0x5344a
80558278 8991b640 00000009 ba8f0fdf 8991b640 nv4_mini+0x53493
8055827c 00000000 ba8f0fdf 8991b640 00000009 0x8991b640


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+533d0
ba8733d0 397908 cmp dword ptr [ecx+8],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+533d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 482e0095

FAILURE_BUCKET_ID: 0xD1_nv4_mini+533d0

BUCKET_ID: 0xD1_nv4_mini+533d0

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

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:49 AM

Posted 01 November 2008 - 08:22 AM

It looks like it worked for you this time! :thumbsup:

The first one (STOP 0x7f) shows ipsec.sys as the likely source of the error - this is a critical security file driver for Windows
The next one (STOP 0x0a)shows ntkrnlmp.exe as the likely source - but this happens as it reads from nv4_mini.sys (a guess on my part)
The next one (STOP 0x7e) is caused by ha10kx2k.sys - a component of your sound card drivers
The last one (STOP 0xd1) is in nv4_mini.sys - which is a component of your video drivers.

Each of the errors occurred in memory. Of the STOP errors mentioned above, all but the STOP 0x7f are usually associated with drivers. The STOP 0x7f is most commonly found to be a hardware error - with memory hardware being the most common failure.

Your previous topic is located here: http://www.bleepingcomputer.com/forums/t/175317/seemingly-random-crashes-please-help/
You've reinstalled Windows (was it a full reinstall or a repair install)?
You've purchased new RAM (presumably good)
You've removed your NIC and Sound card and are using the onboard devices in their place (did you uninstall the software and drivers for the devices that you removed?)

Memory errors can occur in several places - the RAM, the pagefile (on the hard drive), the motherboard, the CPU, or even the memory on video cards (and I'd presume any other device that houses memory). So it's a matter of testing what you can test.

You can run a memory tester to test the RAM. Even new RAM can have problems - and a memory test also involves the channels on the mobo - so it can give an indication of a problem there. A hard drive test can help to rule out issues with the hard drive (where the pagefile resides) - as can running chkdsk /r. Recreating the pagefile can flush corruption from it. There are various video card utilities out there that cmay be able to test the video card memory (but I'm not familiar with any of them) - or you can use another video card to remove that from the equation.

Motherboard testing is expensive and usually doesn't cover every circuit/component of the entire board. You can strip the motherboard down to the minimum components and that can isolate the issues down to a few components: http://www.bleepingcomputer.com/forums/t/70216/hardware-troubleshooting-via-system-stripdown/
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#8 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 01 November 2008 - 12:22 PM

Windows was a full reinstall.
The new RAM is good, I ran it through memtest86 and it didn't have any errors (unlike my previous RAM)
I replaced the NIC before the reinstall, so no old drivers with that, and I uninstalled the sound card drivers, then booted up in safe mode and driver cleaner'd the files left before installing new drivers for the on board audio.
I've done chckdsk.
I uninstalled, cleaned and then installed new video card drivers...just to try something new.

I haven't done a hard drive test (hadn't heard of that one).
I have done a video card utility either.

I guess that's where I'll look next.

#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:49 AM

Posted 01 November 2008 - 04:24 PM

The hard drive test is, admittedly, a shot in the dark. Should the hard drive be failing, then there could be errors when reading the pagefile (your virtual memory). I'd also suggest running chkdsk /r from the Run dialog to be sure that the file system is not corrupted.

You can use this to reset the pagefile:

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#10 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 02 November 2008 - 05:10 AM

Alright, so I did the pagefile thing and ran a video memory stress test that found no errors. 3 hour later I got another crash. I think it has something to do with a driver for my onboard LAN. I guess I can re-install it or whatever, but if its something different everytime, do I stop trying to fix what its telling me and assume its something bigger?






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


Loading Dump File [C:\WINDOWS\Minidump\Mini110208-03.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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Nov 2 03:55:54.829 2008 (GMT-6)
System Uptime: 0 days 3:33:44.777
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {12, 2, 0, b6b60fe0}

*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
Probably caused by : e100b325.sys ( e100b325+a128 )

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

0: 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: 00000012, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b6b60fe0, address which referenced memory

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


READ_ADDRESS: 00000012

CURRENT_IRQL: 2

FAULTING_IP:
afd!AfdBChainedReceiveEventHandler+2c3
b6b60fe0 f6470e01 test byte ptr [edi+0Eh],1

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b6bad73b to b6b60fe0

STACK_TEXT:
80555f14 b6bad73b 89458c80 8914ff68 00000a20 afd!AfdBChainedReceiveEventHandler+0x2c3
80555f74 b6ba23a2 8914ff68 00001050 80556094 tcpip!IndicateData+0x98
80555ffc b6b9fef5 894c5090 6501a8c0 66697b4c tcpip!TCPRcv+0xb55
8055605c b6bbddf9 00000020 894c5090 b6ba2076 tcpip!DeliverToUser+0x18e
80556110 b6b9e922 894c5090 89507dec 000005c8 tcpip!IPRcvPacket+0x670
80556150 b6b9e84d 00000000 894ca278 89507dca tcpip!ARPRcvIndicationNew+0x149
8055618c f7a44f45 89590cd8 00000000 b99feb40 tcpip!ARPRcvPacket+0x68
805561e0 b99f901d 004c9988 8987d510 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
805561f4 b99f91b4 8986d130 8987d510 00000001 psched!PsFlushReceiveQueue+0x15
80556218 b99f95f9 894c5938 00000000 8986d130 psched!PsEnqueueReceivePacket+0xda
80556230 f7a44d40 894c5930 89549580 89549008 psched!ClReceiveComplete+0x13
80556280 b9e7c128 004c9988 805562a0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
WARNING: Stack unwind information not available. Following frames may be wrong.
805563e8 b9e7c2e8 01549008 00000000 899ad590 e100b325+0xa128
80556410 f7a3af09 00549008 80560f00 ffdff9c0 e100b325+0xa2e8
80556428 804dcd22 895493f4 895493e0 00000000 NDIS!ndisMDpcX+0x21
80556440 80560ca0 ffdffc50 00000000 80560ca0 nt!KiRetireDpcList+0x61
80556450 804dcc07 00000000 0000000e 00000000 nt!KiIdleThread0
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
e100b325+a128
b9e7c128 ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: e100b325+a128

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e100b325

IMAGE_NAME: e100b325.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3e6504e9

FAILURE_BUCKET_ID: 0xD1_e100b325+a128

BUCKET_ID: 0xD1_e100b325+a128

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

#11 iisjman07

iisjman07

  • Members
  • 94 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 02 November 2008 - 05:11 AM

Is your PC overheating? Is the PSU powerful enough?

#12 Guest_Abacus 7_*

Guest_Abacus 7_*

  • Guests
  • OFFLINE
  •  

Posted 02 November 2008 - 05:25 AM

I agree about the PSU.

Just get it Tested?

If it is at fault it can burn out the Motherboard

:thumbsup:

#13 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  

Posted 02 November 2008 - 05:32 AM

speedfan seems to think my CPU, hard drive, and ambient temps are all below normal, so I'd be surprised if that's it.

My PSU is a Thermaltake 430W, and my video card is a 6800GT. It has 2 monitors. Now, it has been running fine for quite awhile, so I'd be surprised if it suddenly wasn't strong enough. I got a new monitor that runs at a higher resolution (does that put more stress on a PSU?), but I've had it over 2 months now, and this problem is only 2 weeks old.

#14 Guest_Abacus 7_*

Guest_Abacus 7_*

  • Guests
  • OFFLINE
  •  

Posted 02 November 2008 - 05:42 AM

speedfan seems to think my CPU, hard drive, and ambient temps are all below normal, so I'd be surprised if that's it.

My PSU is a Thermaltake 430W, and my video card is a 6800GT. It has 2 monitors. Now, it has been running fine for quite awhile, so I'd be surprised if it suddenly wasn't strong enough. I got a new monitor that runs at a higher resolution (does that put more stress on a PSU?), but I've had it over 2 months now, and this problem is only 2 weeks old.


Your call, Mate, if it was me I would get the PSU checked out, if that tests out then maybe Motherboard has reached the end of life? You have replaced RAM, that is also an Area to look at? Not all RAM is compatible?

Basically your Problem, IMHO, centres around those three things.

I personally think it is a Hardware Problem.

:thumbsup:

#15 jmillerdls

jmillerdls
  • Topic Starter

  • Members
  • 53 posts
  • OFFLINE
  •  
  • Local time:11:49 PM

Posted 02 November 2008 - 05:47 AM

How do I find out if its the PSU or Motherboard?

The new ram is compatible and has no errors after being tested with memtest86.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users