BSoD but restarts before I can get any codes: now I have codes, but they're different

Lardalish

Ok, so I come back from visiting my parents for about a week and my computer is now getting a BSoD but it's restarting before I can really read anything. I havent done anything new to the machine (though skype updated) and I have not been doing anything out of the ordinary. Basically Ive been using Digsby and Chrome. I checked the Action Center and all it said was that I needed to update my video card driver, so I did that and its still restarting.

After I got home and turned my computer on, it blue screened and restarted after about 20min. When I got it running again, it restarted after about 5, then it didnt do it again until sometime over night. Once I turned it on this morning it went for about an hour, and then it did it again while I was out running some errands. Every time I turn it on after one of these restarts a little window pops up saying windows shut down unexpectedly and asks if I want to search for a solution. I click yes, it chuggs for a little bit then goes away. It never says if it found a solution or not (I imagine it didn't since it kept happening, but I dunno).

Comp Stats:
Windows 7 64 bit
Intel(R) Core i3 CPU 530 @2.93 GHz
4 GB RAM (3.87 Useable)



FAKE EDIT: Ok, it just restarted again, I make it about 40min since I logged in. I actually got a glimpse of the BSoD this time, all I really saw was "BAD_POOL_HEADER" and then the code at the bottom but I didnt have time to write it down.


REAL EDIT: Annnnd again, this time it was about 3min after logging in, and they BSoD said "SERVICE_SYSTEM_EXCEPTION"

Tofystedeth

If you right click on Computer, then go to Advanced System Settings, then click the Settings button under Error Reporting and Recovery, there should be a checkbox to automatically restart after on a crash. Uncheck that. There should also be a checkbox to write a minidump. Check that. Hit ok. Next time your BSOD will stay up.

You can check the past ones by going into the Event Viewer (Right-click Computer -> Manage -> Event Viewer or Start->Run->eventvwr.msc) then go into the Windows Logs -> Systems. It'll show them there.

It's probably a bad driver, the crash info may even say the file that caused it. They sometimes do depending on the type.

Lardalish

Ok, unchecked the restart box, Ill write down the code next time it happens.

In the event viewer, apparently its happened 17 times in the last 24 hours. in the little summary window they're all the same, Event ID: 41, Source: Kernel-Power, Log: System

Heres the XML view of the most recent one:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2010-12-28T01:40:42.577617700Z" /> 
  <EventRecordID>33512</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Bryan-PC</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">25</Data> 
  <Data Name="BugcheckParameter1">0x3</Data> 
  <Data Name="BugcheckParameter2">0xfffffa80034d97a0</Data> 
  <Data Name="BugcheckParameter3">0xeffffa80034d97a0</Data> 
  <Data Name="BugcheckParameter4">0xfffffa80034d97a0</Data> 
  <Data Name="SleepInProgress">false</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>

L Ron Howard

Do a google search on the Keywords listed there. There are like three or four different things that can be causing it, but most point to vid card being a goose.

bowen

Luckily for you, 0x3 is a device driver error (INVALID_AFFINITY_SET). If you created a restore point before you updated your video card driver, use it. If not, download a previous one and install it.

Lardalish

bowen wrote: »

Luckily for you, 0x3 is a device driver error (INVALID_AFFINITY_SET). If you created a restore point before you updated your video card driver, use it. If not, download a previous one and install it.

Well, it did it 2 or 3 times before someone told me to check the action center, which is when I updated my driver. I can still do that and see if it will work.

In other news, it happened YET AGAIN, but because I unchecked the restart I got the info, here it is:

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0xFFFFFA7FFFFFFFD0, 0x0000000000000001, 0x0000000000000002, 0xFFFFF80002CDACF9)

bowen

That points to drivers still. Remove any devices like thumb drivers or cameras you have attached just in case. Though 0xFFFFFA7FFFFFFFD0 points to ntoskrnl.exe which could mean memory issues. Take out all but one stick of memory and start taking them in and out to see if you can determine if one is bad.

Memtest is another way to test that.

Lardalish

Ok, so I ran Memtest and it said I didnt have any errors.

My friend told me to update my display drivers so I went to Windows Update, told it to check for updates, it said I had 5 optional ones, one of which being a display driver. So I told it to install that one and only that one and it got started. Then I got a BSoD sayin this is probly nothin unless Ive gotten it before, talkin about the display driver, so I just restarted. When I logged on I got a message sayin that my driver installed correctly.

Soooo... I guess Ill just wait and see now?

bowen

Yeah I'm glad memtest didn't find anything wrong. Though, start making a backup of stuff you want to save you may need to reinstall windows.

Tofystedeth

Couple things. First: yeah, if you're getting several different stop codes, memory is a likely candidate. 2nd: Ideally you should run several full passes of Memtest (or the Windows memory diagnostic). Often times RAM may not give any errors on the first or second, but give some errors later. And any error in memtest means you need to replace the offending stick.