Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Multiple BSOD


  • Please log in to reply

#1
scewter

scewter

    Member

  • Member
  • PipPipPip
  • 149 posts
Hello, I've recently begun to receive BSOD following normal startups. I have not installed any new hardware. Not sure if it's a driver conflict, software conflict, or malware. I figured I'd start with this forum and post the seven minidumps to see if anyone had a recommendation. I am able to run the Dell desktop in safe mode.

Look forward to any suggestions,
Thnx

Attached Files


  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
  • 0

#3
scewter

scewter

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 149 posts

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.



Broni, thnx for the reply. Here's the text as requested:

==================================================
Dump File : Mini080810-04.dmp
Crash Time : 8/8/2010 5:22:35 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf80938b
Parameter 3 : 0xaa32abc8
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+938b
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080810-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini080810-03.dmp
Crash Time : 8/8/2010 11:59:15 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe14b1ea4
Parameter 2 : 0x00000001
Parameter 3 : 0x805515a1
Parameter 4 : 0x00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7a5a1
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080810-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini080810-02.dmp
Crash Time : 8/8/2010 11:52:23 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe14c78e0
Parameter 2 : 0x00000000
Parameter 3 : 0x8055159a
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+2b04
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080810-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini080810-01.dmp
Crash Time : 8/8/2010 11:45:15 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf837050
Parameter 3 : 0xaa2f8c54
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+37050
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080810-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini080710-01.dmp
Crash Time : 8/7/2010 10:40:57 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe5ffd3f8
Parameter 2 : 0x00000001
Parameter 3 : 0x805519e9
Parameter 4 : 0x00000001
Caused By Driver : SRTSP.SYS
Caused By Address : SRTSP.SYS+2c865
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini073110-01.dmp
Crash Time : 7/31/2010 8:24:58 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe5ff300c
Parameter 2 : 0x00000000
Parameter 3 : 0xa66aba5e
Parameter 4 : 0x00000001
Caused By Driver : NAVEX15.SYS
Caused By Address : NAVEX15.SYS+42a5e
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini073110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini072910-01.dmp
Crash Time : 7/29/2010 8:03:45 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xa525c697
Parameter 3 : 0xa556f15c
Parameter 4 : 0x00000000
Caused By Driver : NAVEX15.SYS
Caused By Address : NAVEX15.SYS+5c697
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini072910-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================
  • 0

#4
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Judging from your errors, I'd start we testing your RAM.

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#5
scewter

scewter

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 149 posts
Okay - I'll try that. I've got couple (two) of RAM modules installed - 2 x 512mb I believe. Do you recc I pull one and then run the test or just see if it runs okay to isolate it?

thnx
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

Do you recc I pull one and then run the test or just see if it runs okay to isolate it?

Exactly.
  • 0

#7
scewter

scewter

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 149 posts

Do you recc I pull one and then run the test or just see if it runs okay to isolate it?

Exactly.


I have 4 modules of 256mb RAM installed. After re-reading your post I followed the instructions for "option A" and removed all but one stick and then started the computer. Following startup I ran a few different programs to observe the performance. Seemed to run okay, just slow as you can imagine on only 256mb. I performed this action four different times checking out each stick. I did not perform the "memtest" as described in "option B" on any stick.

I was able to isolate what appears to be a faulty module. With this module installed, I could not get past the Windows XP logo screen during startup - the one with the moving amber cursor. It displayed the BSOD before ever getting to the blue "Welcome" screen, and the first time I tried it I got a code of 0X000000D1. The second time I tried to run it same result with a code this time of C000021a, and 0xc0000005. Looked for the minidump, but found none to paste here for those two crashes.

Removed that stick, then installed the other three sticks and am running the computer now. Seems to be okay.

Thoughts
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Cool beans :)
  • 0

#9
scewter

scewter

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 149 posts
Broni - think it's worthwhile running memtest on each individual stick?
  • 0

#10
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
No. Why would you? If computer is running fine without that one stick, you're good to go....
  • 0

#11
scewter

scewter

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 149 posts
Okay - sounds good. Now to start shopping for more RAM...

Appreciate the help.

You folks are great.
  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You're very welcome Posted Image
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP