Computer crashes than Blue Screen of Death.


Recommended Posts

System info:

clipboard01kw3.jpg

After various durations of using my laptop it will stop and show the BSoD. Sometimes after 6 hours sometimes after 3 minutes. And usually when i'm on the internet.

My brother recently fitted a wireless network, ''Intel? PRO/Wireless 2200BG'' is what it says.

I mention the wireless because it is the only new hardware i have installed recently.

However my computer worked fine after installing the wireless for 5 days than i got this problem so i'm not sure if they're connected.

This is the stop messsage i get:

dsc02225avr7.jpg

And than once and only once so far i had this one:

dsc02232art1.jpg

It only said that one once and now it has continued to display the first one over and over again.

I sent the microsoft error report and it said that it is a Realtek driver. So went to realtek and downloaded the driver windows suggested.

I still get the problem.

I ran the ''driver verifier'' and choose automatically find unsigned drivers, it has made no difference.

Thank You for your help.

Ive had this issue before installing my Vista x64 on my rig. But the issue was that it might be the memory of Ram thats causing the BSOD.

Two things I would do:

I would do this:

http://www.redhour.info/rhforums/showthread.php?t=2287

And run this:

http://www.memtest.org/

Thank you.

I got this far:

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini070908-01.dmp]

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

Symbol search path is: C:\WINDOWS\Symbols

Executable search path is:

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Wed Jul 9 00:59:53.725 2008 (GMT+1)

System Uptime: 0 days 0:42:22.291

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

....

Unable to load image Ntfs.sys, Win32 error 0n2

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {4, 2, 1, 8054bbb4}

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

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

Unable to load image aswMon2.SYS, Win32 error 0n2

*** WARNING: Unable to verify timestamp for aswMon2.SYS

*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS

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

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

Probably caused by : aswMon2.SYS ( aswMon2+6a14 )

Followup: MachineOwner

---------

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_CORRUPTED_EXPOOL (c5)

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

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

caused by drivers that have corrupted the system pool. Run the driver

verifier against any new (or suspect) drivers, and if that doesn't turn up

the culprit, then use gflags to enable special pool.

Arguments:

Arg1: 00000004, memory referenced

Arg2: 00000002, IRQL

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

Arg4: 8054bbb4, address which referenced memory

Debugging Details:

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

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:

nt!ExAllocatePoolWithTag+673

8054bbb4 897104 mov dword ptr [ecx+4],esi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: ashWebSv.exe

LAST_CONTROL_TRANSFER: from bae1aa62 to 8054bbb4

STACK_TEXT:

ef1e58f8 bae1aa62 00000010 00000001 6966744e nt!ExAllocatePoolWithTag+0x673

ef1e5910 bae185c4 bae38020 ef1e5950 82941f08 Ntfs!ExAllocateFromPagedLookasideList+0x27

ef1e5930 bae3d3d1 831a0e00 00000000 021e59a0 Ntfs!NtfsInitializeIrpContext+0x8b

ef1e59bc 804e37f7 82a0b5f8 831a0e00 806ef2a4 Ntfs!NtfsFsdClose+0x122

ef1e59cc 8066bec5 82a0b020 82a301e8 82938100 nt!IopfCallDriver+0x31

ef1e59f0 baebc459 ef1e5a2c 804e37f7 82a0b020 nt!IovCallDriver+0xa0

ef1e59f8 804e37f7 82a0b020 831a0e00 806ef2a4 sr!SrPassThrough+0x31

ef1e5a08 8066bec5 8276d3a0 831a0e00 82938158 nt!IopfCallDriver+0x31

ef1e5a2c baed209e 831a0e00 82a30e40 8276d3a0 nt!IovCallDriver+0xa0

ef1e5a58 804e37f7 8276d3a0 831a0e00 806ef2a4 fltmgr!FltpDispatch+0x152

ef1e5a68 8066bec5 831a0fd8 00000000 831a0e00 nt!IopfCallDriver+0x31

ef1e5a8c ef5fba14 81c5bc50 8297c248 82941f00 nt!IovCallDriver+0xa0

WARNING: Stack unwind information not available. Following frames may be wrong.

ef1e5ab0 ef5f583c 81c5bc50 001a0e00 804e37f7 aswMon2+0x6a14

ef1e5af0 8056bf74 82941ef0 82941ee0 00000000 aswMon2+0x83c

ef1e5b28 80564777 00941f08 82941ef0 00000000 nt!IopDeleteFile+0x132

ef1e5b44 804e36d5 82941f08 00000000 0000067c nt!ObpRemoveObjectRoutine+0xe0

ef1e5b68 80567847 81b47da0 e2679568 ffba6b30 nt!ObfDereferenceObject+0x5f

ef1e5b80 805678b0 e2679568 82941f08 0000067c nt!ObpCloseHandleTableEntry+0x155

ef1e5bc8 805678fa 0000067c 00000000 00000000 nt!ObpCloseHandle+0x87

ef1e5bdc 804de7ec 0000067c 0000002e 804dc8c1 nt!NtClose+0x1d

ef1e5bdc 804dc8c1 0000067c 0000002e 804dc8c1 nt!KiFastCallEntry+0xf8

ef1e5c58 efbaa188 0000067c 81b59d98 ef1e5d04 nt!ZwClose+0x11

ef1e5c60 81b59d98 ef1e5d04 00000000 045cf4d4 vsdatant+0x18188

ef1e5c64 ef1e5d04 00000000 045cf4d4 00000006 0x81b59d98

ef1e5c68 00000000 045cf4d4 00000006 81b50002 0xef1e5d04

STACK_COMMAND: kb

FOLLOWUP_IP:

aswMon2+6a14

ef5fba14 ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: aswMon2+6a14

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMon2

IMAGE_NAME: aswMon2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 482c3a50

FAILURE_BUCKET_ID: 0xC5_2_aswMon2+6a14

BUCKET_ID: 0xC5_2_aswMon2+6a14

Followup: MachineOwner

---------

kd> lmvm aswMon2

start end module name

ef5f5000 ef60a680 aswMon2 T (no symbols)

Loaded symbol image file: aswMon2.SYS

Image path: aswMon2.SYS

Image name: aswMon2.SYS

Timestamp: Thu May 15 14:27:44 2008 (482C3A50)

CheckSum: 0001EB54

ImageSize: 00015680

Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

So what is the problem?

I downloaded memtest86 and it asked me to insert a floppy disk. I don't have a floppy disk drive.

I looked up this ''aswMon2.SYS'' and found this:

http://forum.avast.com/index.php?board=2%3...3Bthreadid=1165

but i don't understand. I used to use AVG anti virus but it stopped my internet from connecting so i now use Avast!

Edited by saltlick

I turned my computer on this morning and went to Imeem.com than in a few seconds i got BSoD again.

So i did the bug check again and it gave a different code:

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

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

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

Symbol search path is: C:\WINDOWS\Symbols

Executable search path is:

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Wed Jul 9 12:31:53.283 2008 (GMT+1)

System Uptime: 0 days 0:04:40.850

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {4, 2, 1, 8054bbb4}

Probably caused by : ntoskrnl.exe ( nt!ExAllocatePoolWithTag+673 )

Followup: MachineOwner

---------

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_CORRUPTED_EXPOOL (c5)

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

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

caused by drivers that have corrupted the system pool. Run the driver

verifier against any new (or suspect) drivers, and if that doesn't turn up

the culprit, then use gflags to enable special pool.

Arguments:

Arg1: 00000004, memory referenced

Arg2: 00000002, IRQL

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

Arg4: 8054bbb4, address which referenced memory

Debugging Details:

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

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:

nt!ExAllocatePoolWithTag+673

8054bbb4 897104 mov dword ptr [ecx+4],esi

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 804e6bec to 8054bbb4

STACK_TEXT:

ef5fec44 804e6bec 0000000c 00000001 20206f49 nt!ExAllocatePoolWithTag+0x673

ef5fec68 8057aaf9 00000004 00000154 20206f49 nt!ExAllocatePoolWithQuotaTag+0x46

ef5fed00 8058efd7 000002d0 000002c4 00000000 nt!IopXxxControlFile+0x554

ef5fed34 804de7ec 000002d0 000002c4 00000000 nt!NtDeviceIoControlFile+0x2a

ef5fed34 7c90e4f4 000002d0 000002c4 00000000 nt!KiFastCallEntry+0xf8

WARNING: Frame IP not in any known module. Following frames may be wrong.

019dfc00 00000000 00000000 00000000 00000000 0x7c90e4f4

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!ExAllocatePoolWithTag+673

8054bbb4 897104 mov dword ptr [ecx+4],esi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAllocatePoolWithTag+673

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673

BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673

Followup: MachineOwner

---------

kd> lmvm nt

start end module name

804d7000 806ed680 nt M (pdb symbols) C:\WINDOWS\Symbols\exe\ntoskrnl.pdb

Loaded symbol image file: ntoskrnl.exe

Image path: ntoskrnl.exe

Image name: ntoskrnl.exe

Timestamp: Sun Apr 13 20:27:39 2008 (48025EAB)

CheckSum: 002247C2

ImageSize: 00216680

Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

Is this a curropt driver? How do i go about fixing this?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Playground Games confirms Forza Horizon 6 save wipe bug by Taras Buria Forza Horizon 6 was launched last month to critical acclaim (check out our review here), and it became a smash hit in an instant. Now, weeks into the launch, with die-hard fans clocking hundreds of hours, Forza Horizon 6 is facing a serious issue: save wipes. After multiple complaints on Reddit and social media, the studio issued a statement. The problem with missing saves came shortly after Playground Games promised the initial batch of gameplay tweaks and improvements. Unfortunately, there seems to be no temporary fixes for those affected by unexpected save wipes. However, the studio published a new support document with a few important steps users should try. First, affected gamers should open a support ticket immediately (go here to file one) so that the support team can try recovering the lost progress by reverting to an earlier save. Playground Games says this should be done the same day the issue occurs. Meanwhile, gamers are urged not to start new play sessions or create new saves. The studio also published a few things gamers should try to avoid to prevent potential progress loss: Ensure your Gaming Services app on PC or XBOX Series X|S console is fully up to date. On XBOX Series X|S consoles, disable Quick Resume for Forza Horizon 6: To disable Forza Horizon 6 from using Quick Resume, highlight the game box art anywhere in the console experience (Home, My Games & Apps, Pins, etc) and then press the Menu button, then go to Manage game and add-ons > Quick Resume settings > Disable Quick Resume. Ensure you are online when ‘quitting’ the game. Give your saved time to sync to the cloud before powering off or switching devices. Do not force quit the game during save screens. Do not power off the device during gameplay. Always "Quit" (console) or "Exit to desktop" (PC) once you've finished your play session, ensuring the save icon is not visible when you’re closing the game. Before turning off your console, shutting down your PC, or force-closing the Steam app, give your devices or clients at least a few minutes to ensure your latest progress has been synchronized with the cloud. This will reduce the risk of progress reversions as you switch between different platforms. XBOX Series X|S consoles, Steam, and the XBOX app on PC all include game save indicators that confirm your progress has been synced. You can read more about the bug in the official support document here. Forza Horizon 6 is currently available on PC (Steam and the Microsoft Store), Xbox Series X|S, and Game Pass. The game is also coming to PlayStation 5 later this year.
    • If only Windows would have a toggle switch labeled "Get the latest updates as soon as possible" inside Windows Update settings... But nah, let's hide the new stuff inside a controlled feature rollout, even if the user is explicitly asking for the new stuff as soon as possible. Awesome idea!
    • After watching the Apple event earlier this week it is quite the contrast. Apple is going back and tweaking the code to make things more efficient in many areas of MacOS. Windows is boosting your electric build to hide their issues.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      197
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      74
  • Tell a friend

    Love Neowin? Tell a friend!