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

Random BSOD at Windows shutdown


  • Please log in to reply
15 replies to this topic

#1 phoenix85

phoenix85

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 14 July 2011 - 09:50 PM

Hi,

As mentioned above, I've been getting random blue screen messages during shutdown process.
Have been searching around for possible causes, and tried to troubleshoot them as much as I could.
Now, I have run Memtest+ v4.20 twice so far, and I have ruled out faulty RAM(assuming the test is conclusive).
I suspect that either the integrated graphics chipset or the wireless card maybe the culprits. Please
note that I have made all necessary software/driver updates as well ran MalwareBytes/Anti-Virus programs which came back clean.

I should mention that MagicDisc(freeware to read iso images) was installed recently, but I don't think that's causing the problem.I have this installed on another computer and it works fine.

Here are my basic system specs

Mobile Intel 915GM chipset
Graphics : Intel GMA900 controller
Wireless: Intel PRO Wireless 2200B/G
O/S: WIndows XP Pro SP3

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 15 July 2011 - 06:55 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 15 July 2011 - 04:46 PM

Hi Allan,

Here's the info you requested..

Dump File : Mini062311-01.dmp
Crash Time : 23/06/2011 1:56:52 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xff463760
Parameter 2 : 0x00000000
Parameter 3 : 0xa8f8d537
Parameter 4 : 0x00000000
Caused By Driver : int15.sys
Caused By Address : int15.sys+537
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address : int15.sys+537
Stack Address 1 : ntoskrnl.exe+17129
Stack Address 2 : ntoskrnl.exe+9ed11
Stack Address 3 : ntoskrnl.exe+9757c
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062311-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536

#4 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 15 July 2011 - 06:39 PM

There seems to be some question about the int15.sys file - whether or not it is legitimate. It probably is, but let's try this:

1) Run a full system scan with your anti virus app (you do have one installed, yes?)

2)Open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Now shut down. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming procedure, but it is the best way to determine if some process loading with the system is the cause of your problem.
After you've isolated the cause, do not use msconfig to permanently disable the process. Instead, if it is a service go to START - RUN and type: services.msc (then press enter) and disable the service OR, if it a program, you can download & run a simple app such as Mike Lin's Startup Control Panel (http://www.mlin.net/StartupCPL.shtml) to enable, disable, or otherwise manage startup programs.

#5 abauw

abauw

  • Members
  • 951 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Kebun Kelapa
  • Local time:02:53 AM

Posted 15 July 2011 - 07:09 PM

@phoenix85...
does your use acer computer?
int15.sys is are part of Acer’s system recovery mechanism (eRecovery)...

and does your last BSOD is at 23/06/2011 1:56:52 PM??? or you have another .dmp file...
if you have another please paste it too...

Edited by abauw, 15 July 2011 - 07:10 PM.

:guitar: Take me to a place where time is frozen
You don't have to close your eyes to dream :busy:
You can find escape inside this moment :smash:
And I will follow  :whistle:


#6 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 16 July 2011 - 04:43 PM

Hey guys..

First and foremost, I must mention that I have an Acer laptop. The driver in question as
mentioned in the BlueScreenView report,is part of the Acer eRecovery software (int15.sys)

Missed the fact that the report was a bit outdated (June 23rd, 2011) and later,the system
crashed a no. of times during shutdown. Now, I only found one .dmp file in C:WINDOWS\Minidump and
whenever i run the BlueScreenView app, it provides the same dated report.

I also ran a full virus scan last night in safe mode, and no infections were found.
I don't quite understand how Acer eRecovery could possibly cause a BSOD all of a sudden. I have had
this laptop for over 7 years now.

#7 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 16 July 2011 - 04:46 PM

As I said, that file is sometimes spoofed and can be malicious - but as long as you say it scans clean, that's fine. Have you done the selective startup?

#8 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 16 July 2011 - 05:23 PM

Not yet Allan.
Under selective startup, there are four items-
1)SYSTEM.INI
2)WIN.INI
3)SYSTEM SERVICES
4)STARTUP ITEMS

I just want to make sure that I can log into Windows if I uncheck them all.
By unchecking items, did you mean just these above?
Did you also mean unchecking listings under services and startup tabs in msconfig?

#9 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 16 July 2011 - 05:31 PM

System.ini and Win.ini are ignored by XP. but just go ahead and uncheck everything under Selective Startup

#10 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 17 July 2011 - 04:08 PM

I did the selective startup process to get strange results.

Checked each of the four items one at a time, and did the reboot-shutdown procedure. The system shutdown normally.
I tried different combinations i.e. two, three at a time and the result was the same as above. The blue screen only presents
itself in the normal startup mode.Now, I have only did this once and will try again later tonight.


Booted up the system in safe mode and ran MalwareBytes. As expected, no malicious items were found. I also counted the
no.of startup items and services in msconfig both in safe mode as well as in normal mode. Found them to be the exact same number.
Yet, for some reason, the system shuts down fine in safe mode.

#11 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 17 July 2011 - 04:14 PM

Please follow the selective startup procedure as I outlined it.

#12 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 19 July 2011 - 08:29 PM

Hi,

I did the selective startup as outlined in post#4 and couldn't isolate the cause.
Due to the random nature of the BSOD event, I can't quite pinpoint the source of the crash.
For instance, if I selected win.ini, system.ini and services as my bootup options, the system
shuts down normally.I tried this configuration repeatedly and no stop error appeared
on the screen. Similarly, if I chose to bootup the system with options win.ini,sys.ini and
startup options, the system shuts down fine again, even under repeated trials.

So you see, finding the source of the crash is quite simply difficult. I mean, if I could isolate
either the services or startup options as my source of crash, I could have narrowed it down to
one of the many entries in the startup/services tab.

Could you suggest another diagnostic tool to troubleshoot the problem?

#13 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 20 July 2011 - 07:08 AM

Fine, disable all startup items and see what happens. If one of them is the cause, add them back one at a time until the problem recurs.

#14 phoenix85

phoenix85
  • Topic Starter

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:03:53 PM

Posted 23 July 2011 - 06:10 PM

Hi,

Just a quick update about my PC issue.
For the last couple of days, my laptop seems to be shutting down normally.
It's to be noted that I did not make any changes to the PC configuration/settings except run the startup program test
as mentioned in your previous post.I did the procedure and found my computer to be shutting down normally.

For now, everything seems to be fine.
I will revisit this topic if the problem recurs.
In the meantime, I will monitor my PC health for the next couple of weeks.

Thanks

#15 Allan

Allan

  • BC Advisor
  • 8,611 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:53 PM

Posted 24 July 2011 - 07:28 AM

Well, glad it's okay now :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users