Various BSODs on a friend's computer

Punk

Moderator
Staff member
Hey, a friend on a gaming comunity has been having a few BSODs lately.

Here are the minidumps:

==================================================
Dump File : Mini082913-01.dmp
Crash Time : 29/08/2013 13:50:33
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b16a
Parameter 3 : 0xb854b870
Parameter 4 : 0xb854b56c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7416a
File Description : Noyau et système NT
Product Name : Système d'exploitation Microsoft® Windows®
Company : Microsoft Corporation
File Version : 5.1.2600.6223 (xpsp_sp3_gdr.120504-1619)
Processor : 32-bit
Crash Address : ntoskrnl.exe+7416a
Stack Address 1 : ntoskrnl.exe+7475f
Stack Address 2 : ntoskrnl.exe+10e71c
Stack Address 3 : ntoskrnl.exe+10eadd
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082913-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 98 304
Dump File Time : 29/08/2013 13:51:31
==================================================

==================================================
Dump File : Mini082813-01.dmp
Crash Time : 28/08/2013 14:44:47
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8052272c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b72c
File Description : Noyau et système NT
Product Name : Système d'exploitation Microsoft® Windows®
Company : Microsoft Corporation
File Version : 5.1.2600.6223 (xpsp_sp3_gdr.120504-1619)
Processor : 32-bit
Crash Address : ntoskrnl.exe+4b72c
Stack Address 1 : ntoskrnl.exe+4bc56
Stack Address 2 : ntoskrnl.exe+45afb
Stack Address 3 : ntoskrnl.exe+1c2b94
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082813-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 98 304
Dump File Time : 28/08/2013 14:46:46
==================================================

==================================================
Dump File : Mini082713-01.dmp
Crash Time : 27/08/2013 15:15:53
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xe9709000
Parameter 3 : 0xe9709188
Parameter 4 : 0x0c310600
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+5400
File Description : Pilote Win32 multi-utilisateurs
Product Name : Système d'exploitation Microsoft® Windows®
Company : Microsoft Corporation
File Version : 5.1.2600.6244 (xpsp_sp3_gdr.120613-1618)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22f5f
Stack Address 1 : ntoskrnl.exe+74583
Stack Address 2 : win32k.sys+2a50
Stack Address 3 : win32k.sys+b93
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082713-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 98 304
Dump File Time : 27/08/2013 15:18:07
==================================================

And the latest:

==================================================
Dump File : Mini112913-02.dmp
Crash Time : 29/11/2013 12:28:43
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x0000000d
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+10c6
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+6d69e
Stack Address 1 : ntoskrnl.exe+69b45
Stack Address 2 : ntoskrnl.exe+6ef9f
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112913-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 114 688
Dump File Time : 29/11/2013 12:29:45
==================================================

Any ideas?
 
Zip up those dump files and attach them and ill look at them this afternoon when I get home from work.
 
Zip up those dump files and attach them and ill look at them this afternoon when I get home from work.

He's giving them to through a forum so that's all I can give. Unless you want .txt files for each dump file, in that case I will create them and zip them.

Here are new ones:

==================================================
Dump File : Mini112913-04.dmp
Crash Time : 29/11/2013 15:52:13
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x80b0d0f0
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000001
Parameter 4 : 0x806e60bf
Caused By Driver : hal.dll
Caused By Address : hal.dll+10bf
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : hal.dll+10bf
Stack Address 1 : hal.dll+2ae4
Stack Address 2 : ntoskrnl.exe+30aa6
Stack Address 3 : VIDEOPRT.SYS+8c8f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112913-04.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 114 688
Dump File Time : 29/11/2013 15:53:24
==================================================

==================================================
Dump File : Mini112713-01.dmp
Crash Time : 27/11/2013 15:03:32
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x806e7ae4
Parameter 2 : 0x006e7121
Parameter 3 : 0xa97e30e0
Parameter 4 : 0x0000000a
Caused By Driver : hal.dll
Caused By Address : hal.dll+10cb
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : hal.dll+10cb
Stack Address 1 : hal.dll+2ae4
Stack Address 2 : ntoskrnl.exe+30aa6
Stack Address 3 : VIDEOPRT.SYS+8c8f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112713-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 114 688
Dump File Time : 27/11/2013 15:04:33
==================================================

==================================================
Dump File : Mini112713-05.dmp
Crash Time : 27/11/2013 18:20:59
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xa70dbf24
Parameter 3 : 0xa70dbc20
Parameter 4 : 0x80569f97
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+dff0
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22fa3
Stack Address 1 : Ntfs.sys+dff0
Stack Address 2 : Ntfs.sys+5f7f
Stack Address 3 : ntoskrnl.exe+181f9
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112713-05.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 114 688
Dump File Time : 27/11/2013 18:22:03
==================================================

==================================================
Dump File : Mini112713-06.dmp
Crash Time : 27/11/2013 18:39:58
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x81545b9d
Parameter 2 : 0x00000002
Parameter 3 : 0x00000008
Parameter 4 : 0x81545b9d
Caused By Driver : hal.dll
Caused By Address : hal.dll+2d43
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address :
Stack Address 1 : hal.dll+2ae4
Stack Address 2 : ntoskrnl.exe+6d75c
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112713-06.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 114 688
Dump File Time : 27/11/2013 18:40:59
==================================================
 
I would need all the windows minidump files zipped and attached. They would be the file names listed in the full path section of each section. For example..

C:\WINDOWS\Minidump\Mini112713-06.dmp
 
I would need all the windows minidump files zipped and attached. They would be the file names listed in the full path section of each section. For example..

C:\WINDOWS\Minidump\Mini112713-06.dmp

Ok I will ask him to do that after he's done with memtest86. Asked him to test his RAM since the problem was coming from multiple places including the processor...
 
Ok, there are various outcomes in the first 5 dump files I've examined.

Causes

1 was from video driver
2 involved chrome
1 was from league of legends
1 was from norton software

So we have a wide variety of issues here just from the first 5 dump files. What OS is on this system? Ask if there was any new software or hardware added before the blue screens started appearing.
 
Ok, there are various outcomes in the first 5 dump files I've examined.

Causes

1 was from video driver
2 involved chrome
1 was from league of legends
1 was from norton software

So we have a wide variety of issues here just from the first 5 dump files. What OS is on this system? Ask if there was any new software or hardware added before the blue screens started appearing.

MS Windows XP Professional SP3
AMD Phenom 8600 Triple-Core Processor with 3 GB RAM and NVIDIA GeForce G210

He just had the shockwave plugin of chrome crash...
 
BSODs he has are all different.He is having some serious problems with his system...

Anyway:

-DRIVER_IRQL_NOT_LESS_OR_EQUAL:

This error is generated when a driver or part of Windows attempts to access pageable memory using the IRQL kernel process that is invalid.It can be bad hardware drivers,bad memory or mismatched memory or even corrupt or bad virtual memory page file.There are cases when the whole RAM is used and when the user attempts to use more resources on his/her computer and there is no free RAM left anymore that this will happen and therefore he should also enable PAGE FILE and put it on maximum.I put mine on 4096 MB and I noticed it gets used a lot since my RAM usually gets completely full when doing something heavy...


-ATTEMPTED_WRITE_TO_READONLY_MEMORY:

This would suggest a hardware problem with the first suspect being the physical RAM if you ask me...
For how long did he run MEM TEST?I always run it for at least 24 hours...
There are many programs for this purpose...I would recommend to use the one which works directly when booted from the CD disk rather than within Windows OS...

-NTFS_FILE_SYSTEM:

This type of the BSOD indicates that a problem occurred within "Ntfs.sys" file (the driver file that allows the system to read and write to NTFS drives).Corruption in the NTFS file system or in blocks (sectors) on the hard disk drive can cause this error.Corrupted SCSI and EIDE drivers can also adversely affect the systems ability to read and write to the hard disk drive and therefore cause the error.Tell your friend to start Windows in SAFE MODE WITH COMMAND PROMPT and then use the following command to fix all errors on the drive:

chkdsk.exe C: /F /R /X /V

He will probably be asked wether he wants to use the CHKDSK on the next restart.Tell him to confirm with YES.After that,write the following command to restart the computer:

shutdown.exe -R -T 0

If he has more than one C: partition then tell him to do the SAME on all other partitions such as D: , E: , F: and so on...

-IRQL_NOT_LESS_OR_EQUAL:

This BSOD indicates that a kernel mode process or driver attempted to access a memory address to which it did not have permission to access.The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory.A pointer such as INT is a variable used by a program to refer to a block of memory.If the variable has an incorrect value in it the program tries to access memory that it should not.When this occurs in a user mode application,it generates an access violation.When it occurs in kernel mode,it generates a STOP 0x0000000A message.I must admit that this happened to me quite a few times when I used improper strings and integers when I was working on a few programs lol...I guess I just stored some bad data in them...It was a long time ago anyway lol.
But anyway...this can be caused by a bad program that he has installed...



Of course...it can also be that he is having HARDWARE issues.
But let's not go that far just yet...:D





Cheers!
 
I dunno... new CPU in a older motherboard? BIOS update? Chipset drivers updated?> Insufficient PSU? all coould be contributing.
 
Back
Top