many blue screens!please help...
-
Re: many blue screens!please help...
-
Did you update the BIOS?
Did you run Check Disk?
-
yes i run check disk a few times...
ok i decided to format my computer and reinstall everything.
1) what's the best way to format? through the DOS windows boot installation? or maybe through the "write zeroes" option in Western Digital Data Lifeguard Diagnostics?
2) what's the proper order of these installations on a new computer?:
winamp
haali media splitter codec
samsung 206bw driver
ffdshow codec
logitech keyboard driver
asus 2014l1t driver
nvidia 8600gts driver
emule
utorrent
asus pc probe
icq
eset nod32
winrar
soundblaster x-fi driver
amd 4800+ driver
amd dual-core optimizer
daemon tools
asus m2n-e chipset driver
3) do you think i need to update my BIOS? i have M2N-E mb with revision 1001 BIOS.
-
A Clean Install of XP will format during the install.
If you want to wipe the drive first then use the WD Tool.
After install load SP2 first if it is not on your CD.
Then your motherboard drivers then your graphics drivers.
That is the important stuff. The rest is up to you. Doesn't really matter.
I would not install any codecs unless you know specifically that you need them for a specific purpose.
If you continue to have Memory issues I would update your BIOS as they do address Memory issues.
-
what does it mean "wipe"? is it better than just formatting?
if i update my bios and then format the hard disk, does the bios stays at the same revision?
-
The BIOS is stored on a motherboard chip.
Changing hard drives and or operating systems will not affect it.
Wipe means writing zeros to the disk.
Formatting will just say to the system: 1) the drive is empty: open to be written to. 2) write in this format: NTFS (in XP).
Setup will then just overwrite the old data.
Wiping will also remove the current Boot Sector which formatting will not.
However reinstalling the same OS (XP) will just recreate the same Boot Sector.
The only advantage to removing the Boot Sector is in the rare case of a Boot Sector virus.
If you have the time go ahead and wipe it is what I'd suggest. But it is not necessary.
-
should i update the bios through "asus update" program or "ez flash"?
-
ok i've searched a little about my comp problem and i found this website:
http://www.vladd44.com/other/irq_error.php
according to what they say there the problem is caused by drivers which has the same IRQ numbers...and i do have that problem when i enter the Device Manager.
do you think it might fix the problem?
-
"should i update the bios through "asus update" program or "ez flash"?"
See my post #4. However, the means towards updating is your choice.
"according to what they say there the problem is caused by drivers which has the same IRQ numbers...and i do have that problem when i enter the Device Manager.
do you think it might fix the problem?"
From my post #2'
"Based upon your listed reports, you probably have a memory problem, or possibly an incorrect/corrupted driver."
If your memory has been fully tested and considered error free, and if you've updated you bios to what I recommended in my post #4, drivers are the next step.
If you have some "new" Blue Screen logs, please post them.
-
1) my current bios revision is 1001...should i update it to revision 1202?
2) "drivers are the next step" - but i already have the latest graphic, sound and chipset drivers....
new blue screens:
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {f19ffff0, 2, 0, 805238e0}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+188 )
Followup: MachineOwner
---------
1: 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: f19ffff0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 805238e0, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: f19ffff0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiDeletePte+198
805238e0 8b420c mov eax,dword ptr [edx+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: iexplore.exe
LAST_CONTROL_TRANSFER: from 80523d5e to 805238e0
STACK_TEXT:
b1c585a8 80523d5e c0012490 02492000 00000000 nt!MiDeletePte+0x198
b1c58670 8051a434 00000010 024b7fff 00000000 nt!MiDeleteVirtualAddresses+0x164
b1c5868c 805b21b0 02490000 024b7fff b1c58744 nt!MiDeleteFreeVm+0x20
b1c5872c 8054137c ffffffff b1c5880c b1c58818 nt!NtFreeVirtualMemory+0x42e
b1c5872c 80500389 ffffffff b1c5880c b1c58818 nt!KiFastCallEntry+0xfc
b1c587b4 bf809e43 ffffffff b1c5880c b1c58818 nt!ZwFreeVirtualMemory+0x11
b1c58810 bf809eae 00000000 00000000 b1c58834 win32k!SURFACE::bDeleteSurface+0x188
b1c58820 bf80fa34 00000000 00000000 e2e2ee18 win32k!SURFREF::bDeleteSurface+0x12
b1c58834 bf80fb0d 54051731 0012dfb4 b1c58854 win32k!bDeleteSurface+0x20
b1c58848 8054137c 54051731 0012dfc8 7c90eb94 win32k!NtGdiDeleteObjectApp+0x74
b1c58848 7c90eb94 54051731 0012dfc8 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012dfc8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+188
bf809e43 e964ffffff jmp win32k!SURFACE::bDeleteSurface+0x1a8 (bf809dac)
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+188
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46d2c6a4
FAILURE_BUCKET_ID: 0xA_win32k!SURFACE::bDeleteSurface+188
BUCKET_ID: 0xA_win32k!SURFACE::bDeleteSurface+188
Followup: MachineOwner
---------
----------------------------------------------------------------------------------------------------------------------
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 277a65, 7, 0}
Probably caused by : memory_corruption ( nt!MiDeletePte+447 )
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00277a65, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: wmplayer.exe
LAST_CONTROL_TRANSFER: from 80523b8f to 804f9f05
STACK_TEXT:
b219fb84 80523b8f 0000004e 00000099 00277a65 nt!KeBugCheckEx+0x1b
b219fbc8 80523d5e c0035490 06a92000 00000000 nt!MiDeletePte+0x447
b219fc90 8051a434 00000210 07311fff 00000000 nt!MiDeleteVirtualAddresses+0x164
b219fcac 805b21b0 06a50000 07311fff b219fd64 nt!MiDeleteFreeVm+0x20
b219fd4c 8054137c ffffffff 02c8eca0 02c8ecb8 nt!NtFreeVirtualMemory+0x42e
b219fd4c 7c90eb94 ffffffff 02c8eca0 02c8ecb8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02c8ebe8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeletePte+447
80523b8f 8b5008 mov edx,dword ptr [eax+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiDeletePte+447
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+447
BUCKET_ID: 0x4E_99_nt!MiDeletePte+447
Followup: MachineOwner
---------
Newbie
