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's


  • Please log in to reply
6 replies to this topic

#1 Axegrinder

Axegrinder

  • Members
  • 62 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 11 September 2008 - 07:04 AM

Hey guys, having abit of trouble with the main desktop, in that it will BSOD at the login screen or when logging in. The graphics also go weird like a stereogram. This has been happening for about a week or 2.

Here are some error codes ive been getting

0x0000005c

0x00000050

0x10000050

0x0000008e

0x100000D1

0x1000008e

--

Spec of machine

ASUS A7V400-MX
AMD Sempron 2400+ 1.67ghz
1GB of RAM PC2700
20+40GB hard disks
XP Home SP3

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:03:40 AM

Posted 11 September 2008 - 07:11 AM

These all seem to point to a driver or compatibility problem. Have you recently added any new hardware (or updated the hardware)?

Try analyzing the memory dump files using this link: http://forums.majorgeeks.com/showthread.php?t=35246
Copy and paste the 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 Axegrinder

Axegrinder
  • Topic Starter

  • Members
  • 62 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 11 September 2008 - 08:09 AM

The last piece of hardware was a 2nd hard disk about 1 month ago, then some extra ram about 6-7 months ago. These crashes ALWAYS seem to happen when logging in to windows.



Latest minidump:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini091108-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Sep 11 12:47:39.687 2008 (GMT+1)
System Uptime: 0 days 0:00:31.218
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {80b5b856, 2, 0, 80b5b856}

Probably caused by : ntoskrnl.exe ( nt!KiSwapThread+46 )

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

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

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


READ_ADDRESS: 80b5b856

CURRENT_IRQL: 2

FAULTING_IP:
+ffffffff80b5b856
80b5b856 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from f228ecec to 80b5b856

FAILED_INSTRUCTION_ADDRESS:
+ffffffff80b5b856
80b5b856 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f228eca8 f228ecec 86cf7020 ffdff120 86dd8958 0x80b5b856
f228ecb8 804dc0f7 86d17090 86d17020 804dc143 0xf228ecec
f228ecc4 804dc143 00000000 00000000 00000000 nt!KiSwapThread+0x46
f228ecec 80566210 00000001 00000006 00000001 nt!KeWaitForSingleObject+0x1c2
f228ed50 804de7ec 000003f8 00000000 00000000 nt!NtWaitForSingleObject+0x9a
f228ed50 7c90e4f4 000003f8 00000000 00000000 nt!KiFastCallEntry+0xf8
017ff17c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSwapThread+46
804dc0f7 84c0 test al,al

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSwapThread+46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiSwapThread+46

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiSwapThread+46

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


Minidump 2:


Loading Dump File [C:\WINDOWS\Minidump\Mini090708-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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Sep 7 19:35:09.718 2008 (GMT+1)
System Uptime: 0 days 0:00:39.250
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e2d53720, 1, 804e20fe, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e2d53720, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804e20fe, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: e2d53720

FAULTING_IP:
nt!RtlpInterlockedPushEntrySList+c
804e20fe 8903 mov dword ptr [ebx],eax

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 805685a4 to 804e20fe

STACK_TEXT:
f2c3dbf0 805685a4 00000000 00000100 86c3f658 nt!RtlpInterlockedPushEntrySList+0xc
f2c3dc18 8056cbeb 00000000 00000000 5658c301 nt!ObOpenObjectByName+0x3b8
f2c3dc94 8056ccba 0220fadc 80100080 0220fa7c nt!IopCreateFile+0x407
f2c3dcf0 8056cdf0 0220fadc 80100080 0220fa7c nt!IoCreateFile+0x8e
f2c3dd30 804de7ec 0220fadc 80100080 0220fa7c nt!NtCreateFile+0x30
f2c3dd30 7c90e4f4 0220fadc 80100080 0220fa7c nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0220fad4 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804e270c-804e270f 4 bytes - nt!KiServiceTable+64
[ dd 78 56 80:18 e6 8c f5 ]
804e274c-804e274f 4 bytes - nt!KiServiceTable+a4 (+0x40)
[ 5d 06 57 80:d4 e4 8c f5 ]
804e27ac-804e27af 4 bytes - nt!KiServiceTable+104 (+0x60)
[ 50 2d 59 80:b2 e9 8c f5 ]
804e27b8-804e27bb 4 bytes - nt!KiServiceTable+110 (+0x0c)
[ e0 15 57 80:ac e0 8c f5 ]
804e2884-804e2887 4 bytes - nt!KiServiceTable+1dc (+0xcc)
[ 59 8d 56 80:ae e5 8c f5 ]
804e2890-804e2893 4 bytes - nt!KiServiceTable+1e8 (+0x0c)
[ c7 17 57 80:ec df 8c f5 ]
804e28a8-804e28ab 4 bytes - nt!KiServiceTable+200 (+0x18)
[ bd a1 58 80:50 e0 8c f5 ]
804e296c-804e296f 4 bytes - nt!KiServiceTable+2c4 (+0xc4)
[ f1 a1 56 80:ce e6 8c f5 ]
804e29d8-804e29db 4 bytes - nt!KiServiceTable+330 (+0x6c)
[ 91 ec 64 80:8e e6 8c f5 ]
804e2a84-804e2a87 4 bytes - nt!KiServiceTable+3dc (+0xac)
[ 89 28 57 80:0e e8 8c f5 ]
40 errors : !nt (804e270c-804e2a87)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

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


MINIDUMP 3:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini090808-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;http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Mon Sep 8 11:12:11.359 2008 (GMT+1)
System Uptime: 0 days 0:00:37.906
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ffefec6c, 0, ffefec6c, 0}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!NtQueryInformationFile+23d )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffefec6c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: ffefec6c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: ffefec6c

FAULTING_IP:
+ffffffffffefec6c
ffefec6c ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: ashServ.exe

LAST_CONTROL_TRANSFER: from 8056ca17 to ffefec6c

FAILED_INSTRUCTION_ADDRESS:
+ffffffffffefec6c
ffefec6c ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f2de9c90 8056ca17 86d7ff28 00000001 01faa13c 0xffefec6c
f2de9d48 804de7ec 000003ac 01faa164 01faa13c nt!NtQueryInformationFile+0x23d
f2de9d48 7c90e4f4 000003ac 01faa164 01faa13c nt!KiFastCallEntry+0xf8
01faa11c 7c90d7bc 7c831c63 000003ac 01faa164 0x7c90e4f4
01faa16c 64084932 000003ac 00000000 01faa190 0x7c90d7bc
01faa19c 6408498a 01faa1f0 00000000 64081568 0x64084932
01faa1c4 642a951f 01570f50 012ec688 012ec680 0x6408498a
01faa2a8 642a9734 012ec680 01570f50 00000000 0x642a951f
01faa3c0 642a4871 012ec680 01570f50 00000000 0x642a9734
01faa3fc 65013526 012ec680 01570f50 0016e6a4 0x642a4871
01faa400 012ec680 01570f50 0016e6a4 00000000 0x65013526
01faa404 01570f50 0016e6a4 00000000 00000020 0x12ec680
01faa408 0016e6a4 00000000 00000020 01fab8f4 0x1570f50
01faa40c 00000000 00000020 01fab8f4 00000000 0x16e6a4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtQueryInformationFile+23d
8056ca17 e9ad630000 jmp nt!NtQueryInformationFile+0x242 (80572dc9)

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!NtQueryInformationFile+23d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

FAILURE_BUCKET_ID: 0x50_CODE_AV_BAD_IP_nt!NtQueryInformationFile+23d

BUCKET_ID: 0x50_CODE_AV_BAD_IP_nt!NtQueryInformationFile+23d

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

Edited by Axegrinder, 11 September 2008 - 08:10 AM.


#4 Axegrinder

Axegrinder
  • Topic Starter

  • Members
  • 62 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 12 September 2008 - 01:56 PM

This is still happening =/.

#5 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:07:40 AM

Posted 12 September 2008 - 02:21 PM

Id download Memtest and run a test on your RAM.

#6 Axegrinder

Axegrinder
  • Topic Starter

  • Members
  • 62 posts
  • OFFLINE
  •  
  • Local time:08:40 AM

Posted 12 September 2008 - 02:24 PM

I think i have it on a CD somewhere, cant find it though.

#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:03:40 AM

Posted 14 September 2008 - 08:49 AM

One of the crashes occurred in ashServ.exe. This is a part of your Avast program. Try downloading a new copy, then uninstall the old one and install the new one.

As this also seems to have a memory component (and this could be a compatibility problem) - did you check for compatibility before installing the extra RAM (both between modules and for your motherboard)? To verify/rule this out I'd suggest running this free memory diagnostic: http://www.memtest86.com/
Since this may be an intermittent problem, I'd suggest running the test overnight (at a minimum) and even longer if possible.

Finally, should this be a driver problem, try enabling Driver Verifier. To do this, go to Start...Run...and type in "verifier.exe" (without the quotes) and press Enter.
In the next window, click on Next to "Create standard settings"
Then click on Next to "Automatically select unsigned drivers"
Then click on Finish to accept the list of unsigned drivers to be verified.
Reboot your system

If lucky, the system will generate another BSOD as soon as you reboot.
If it does, boot into Safe Mode and perform the analysis on that dump file and post it here.
If it doesn't, then continue to use the system normally until it does have a BSOD.
Then perform the analysis on that file and post it here.

Once you've had the BSOD, go back into Driver Verifier and select the "Delete existing settings" option on the first page and click Next/Finish to delete those settings. If necessary, you may have to do this in Safe Mode (if the system isn't booting into normal mode due to a BSOD).
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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users