Announcement

Collapse
No announcement yet.

BSOD

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BSOD

    Is anyone else having the blue screen of death while playing bad company 2?

  • #2
    Re: BSOD

    No.

    What does your bluescreen say and has it always done this?

    Crunch
    Twitter: @CptainCrunch
    Battlelog/Origin: CptainCrunch

    Comment


    • #3
      Re: BSOD

      ouch, BSODs are never fun

      Comment


      • #4
        Re: BSOD

        I just got one of these! First time it ever happened. Any idea why?

        Comment


        • #5
          Re: BSOD

          Just got it for a second time. After reboot this was on my desktop.
          Problem signature:
          Problem Event Name: BlueScreen
          OS Version: 6.1.7600.2.0.0.768.3
          Locale ID: 1033

          Additional information about the problem:
          BCCode: 124
          BCP1: 0000000000000000
          BCP2: FFFFFA8008056028
          BCP3: 00000000BF800000
          BCP4: 0000000000200001
          OS Version: 6_1_7600
          Service Pack: 0_0
          Product: 768_1
          And I ran a program called. BlueScreenView This is what it told me.

          ==================================================
          Dump File : 041211-23805-01.dmp
          Crash Time : 4/12/2011 12:35:17 AM
          Bug Check String :
          Bug Check Code : 0x00000124
          Parameter 1 : 00000000`00000000
          Parameter 2 : fffffa80`08056028
          Parameter 3 : 00000000`bf800000
          Parameter 4 : 00000000`00200001
          Caused By Driver : hal.dll
          Caused By Address : hal.dll+12903
          File Description :
          Product Name :
          Company :
          File Version :
          Processor : x64
          Computer Name :
          Full Path : C:\Windows\Minidump\041211-23805-01.dmp
          Processors Count : 4
          Major Version : 15
          Minor Version : 7600
          Dump File Size : 290,896
          ==================================================

          ==================================================
          Dump File : 041111-24632-01.dmp
          Crash Time : 4/11/2011 11:41:23 PM
          Bug Check String :
          Bug Check Code : 0x00000124
          Parameter 1 : 00000000`00000000
          Parameter 2 : fffffa80`078cd028
          Parameter 3 : 00000000`bf800000
          Parameter 4 : 00000000`00200001
          Caused By Driver : hal.dll
          Caused By Address : hal.dll+12903
          File Description :
          Product Name :
          Company :
          File Version :
          Processor : x64
          Computer Name :
          Full Path : C:\Windows\Minidump\041111-24632-01.dmp
          Processors Count : 4
          Major Version : 15
          Minor Version : 7600
          Dump File Size : 290,968
          ==================================================

          Comment


          • #6
            Re: BSOD

            Caused By Driver : hal.dll
            Google hal.dll, there seems to be some issues with it.

            Comment


            • #7
              Re: BSOD

              From what I've been told and read on several tech sites is that is could be a whole slew of problems. NVIDIA drivers, memory, hard drive. etc.

              Comment


              • #8
                Re: BSOD

                Yeah, hal.dll is the main link to the Hardware Abstract Layer and the software. All it means is that the hardware is not playing nice with a piece of software. Problem is, which one?

                You might be able to narrow it down by looking in the event log around the time the BSOD happened. See if anything stopped responding or hanged. Usually BSODs are fast enough that it doesnt get recorded, but you never know.

                Crunch
                Twitter: @CptainCrunch
                Battlelog/Origin: CptainCrunch

                Comment


                • #9
                  Re: BSOD

                  By the event log do you mean- C:\Windows\Minidump\041211-23805-01.dmp ? I tried opening both in Notepad and it said access denied.

                  **** Edit. found Event viewer and looked at the two crashes ****
                  Log Name: System
                  Source: Microsoft-Windows-Kernel-Power
                  Date: 4/11/2011 11:41:08 PM
                  Event ID: 41
                  Task Category: (63)
                  Level: Critical
                  Keywords: (2)
                  User: SYSTEM
                  Computer: Manzi-PC
                  Description:
                  The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
                  Event Xml:
                  <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="2011-04-12T03:41:08.028420300Z" />
                  <EventRecordID>17914</EventRecordID>
                  <Correlation />
                  <Execution ProcessID="4" ThreadID="8" />
                  <Channel>System</Channel>
                  <Computer>Manzi-PC</Computer>
                  <Security UserID="S-1-5-18" />
                  </System>
                  <EventData>
                  <Data Name="BugcheckCode">292</Data>
                  <Data Name="BugcheckParameter1">0x0</Data>
                  <Data Name="BugcheckParameter2">0xfffffa80078cd028</Data>
                  <Data Name="BugcheckParameter3">0xbf800000</Data>
                  <Data Name="BugcheckParameter4">0x200001</Data>
                  <Data Name="SleepInProgress">false</Data>
                  <Data Name="PowerButtonTimestamp">0</Data>
                  </EventData>
                  </Event>
                  Log Name: System
                  Source: Microsoft-Windows-Kernel-Power
                  Date: 4/12/2011 12:35:00 AM
                  Event ID: 41
                  Task Category: (63)
                  Level: Critical
                  Keywords: (2)
                  User: SYSTEM
                  Computer: Manzi-PC
                  Description:
                  The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
                  Event Xml:
                  <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="2011-04-12T04:35:00.310819000Z" />
                  <EventRecordID>18051</EventRecordID>
                  <Correlation />
                  <Execution ProcessID="4" ThreadID="8" />
                  <Channel>System</Channel>
                  <Computer>Manzi-PC</Computer>
                  <Security UserID="S-1-5-18" />
                  </System>
                  <EventData>
                  <Data Name="BugcheckCode">292</Data>
                  <Data Name="BugcheckParameter1">0x0</Data>
                  <Data Name="BugcheckParameter2">0xfffffa8008056028</Data>
                  <Data Name="BugcheckParameter3">0xbf800000</Data>
                  <Data Name="BugcheckParameter4">0x200001</Data>
                  <Data Name="SleepInProgress">false</Data>
                  <Data Name="PowerButtonTimestamp">0</Data>
                  </EventData>
                  </Event>
                  I also uninstalled my Realtek and NVIDIA drivers and installed the newest ones, they were already the newest before I uninstalled. Ran a windows memory test, no problems were detected.

                  This BSOD happened after about 20 minutes of playing BFBC2 Vietnam. Had no obvious graphic errors or problems before it went to Bluescreen. EVGA Precision shows me that the temp is fine when in-game (60's C). Since reinstalling the audio and graphics drivers I haven't played the game. (Don't want to do it with everyone here at home up my ass about the issue).

                  Also in the BlueScreenView it mentions ntoskrnl.exe+1865a3 and has its line highlighted in red like it does hal.dll

                  System Specs:

                  Manufacturer: iBuyPower
                  Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.6GHz
                  Memory: 8192MB RAM
                  Hard Drive: 1 TB
                  Video Card: Palit Sonic Platinum NVIDIA GeForce GTX 460
                  Sound Card: Speakers (Realtek High Definition Audio)
                  Speakers/Headphones: Plantronics USB DSP 550
                  Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.101026-1503)
                  Motherboard: Gigabyte GA-P67A-UD3-B3 Intel P67 Chipset
                  Computer Case: Thermaltake Dokker

                  Comment


                  • #10
                    Re: BSOD

                    Okay just played BFBC2 Vietnam for again I'd say 20 or so minutes and it BSOD'd. Same errors. So updating the graphics and audio drivers did not work. Next idea?

                    The BSOD said i should disable Bios memory options such as caching or shadowing?


                    Also I read several places that overclocking can cause issues. My machine came default as is, except for the graphics card by Palit which is made by Palit to be overclocked to 800 ( at least i think it is overclocked) http://www.palit.biz/main/vgapro.php?id=1338

                    Comment


                    • #11
                      Re: BSOD

                      The Windows event log. Its found by right clicking on your MY COMPUTER icon and selecting MANAGE. It will say EVENT VIEWER. The logs are in there.

                      Unless you made changes in the BIOS, I wouldnt worry about that. You could reset your BIOS, but if you dont know how your machine was set before, I would either write all the settings down or dont do it. Your system is being overclocked and its not impossible that its a little too much and is causing the BSOD. Since its taking 20 minutes, it could be a heat issue. You might check that and see how it runs. Alex had some overclocking guidelines in the tech center with tools to use for testing that.

                      Crunch
                      Twitter: @CptainCrunch
                      Battlelog/Origin: CptainCrunch

                      Comment


                      • #12
                        Re: BSOD

                        I edited my post earlier to include those logs. Like I said everything (as far as I know) is standard and not overclocked.

                        The computer manufacturer sent me to this.

                        Here is a link that may be a fix for the current errors you are receiving on the PC. This site will explain the current file being detected within the PC. http://pcsupport.about.com/od/fixthe...ws-7-vista.htm. See if this may provide any results. You can try a reinstallation of Windows as well on the PC if needed. See if that may allow the system to run stable. If the same problems continues then there may be a further hardware error within the PC causing this issue.
                        Here is part of what that link states.
                        Hal.dll errors are common when it comes to show-stopping, boot-time error messages... in Windows XP. In fact, beginning in Windows Vista, hal.dll doesn't even exist. It's nowhere to be found in Windows Vista, Windows 7, or later Windows operating systems.

                        Of course if that's true, why did your Windows 7 or Windows Vista computer stop booting and tell you that this file is missing? How can the hal.dll file be missing if it's not even supposed to be there?!

                        The answer has to do with the master boot record on your hard drive. One type of master boot record is only compatible with Windows XP and earlier, while the other type is compatible only with later versions of Windows like Windows Vista and Windows 7.

                        So, if you have Windows Vista or Windows 7 installed and you're seeing the hal.dll error, it most likely means that for whatever reason, your master boot record has been changed to the one only compatible with Windows XP... and it's looking for hal.dll.
                        Also this post on a windows support site seems very similar to my problem. http://www.sevenforums.com/crashes-d...er-20mins.html

                        The one guy suggests uninstalling all Gigabyte Software (my mobo is Gigabyte) i have 6 Gigabyte programs installed. Easy Tune 6, Auto Green, Smart 6, On_Off Charge, Des 2.0, and @BIOS. Should I uninstall these.

                        Comment


                        • #13
                          Re: BSOD

                          Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.6GHz
                          That tells me the system is running 300 MHz above its CPU speed. That could just be what the BIOS is reading, but thats a big difference. If its not overclocked I would think it would say something more like 3.36 or 3.29.

                          You can try uninstalling the software. They all control different features of your hardware and not the OS itself. I would check Gigabyte's website to make sure you could download them to re-install later. More than likely you will be able to.

                          Looking up Event 41 points to - Bad Drivers, Overheating, bad overclocking, and faulty hardware.

                          After that, the simplest thing to check is overheating first. Not just the video card, but the system. I looked up your card specs and it tends to run hot. There is also a fan issue on some of the models. Keep an eye on that.

                          Next easiest thing is updating your chipset drivers. You already did your sound and video, so I would go to Intel's site and download the latest ones. Intel has a hard site to navigate through, but you should be able to find it.

                          After that, you can check the hard drive. You have to know the manufacturer and go to their site and download diagnostic tools to check it, though I dont think its that myself.

                          Just try one thing at a time and see if it stops.

                          Crunch
                          Twitter: @CptainCrunch
                          Battlelog/Origin: CptainCrunch

                          Comment


                          • #14
                            Re: BSOD

                            According to the properties on my hard drive it is a Hitachi HDS721010CLA332 ATA Device
                            1 TB HARD DRIVE -- 16M Cache, 7200 RPM, 3.0Gb/s

                            That processor listing is what Xfire came out to, but I just looked at my properties and it is also listed as such. The gigabytye software came on a DVD with the computer (i already did a recovery once on this thing on the 2nd day to correct something else). The mobo is on the right wall of the case with the card hanging and pointing downward with the back plate on top and the fan part on the bottom. Like I said I kept alt tabbing while in game to check the GPU temp and it was in the 60's but obviously couldnt get reading right before the BSOD.

                            Someone else told me to run a 3rd party memory test for a few hours which I will do later tonight. I am still bamboozled as to how this happens after 20 minutes of BFBC2 and not after two hours of Metro 2033. The 2500k model is designed with overclocking in mind so maybe intel ships them already overclocked? I did not think ibuypower did the overclocking because i did not pay extra for them to do it, but you never know, maybe they were being generous.

                            Comment


                            • #15
                              Re: BSOD

                              I havent run the next set of tests yet but I was thinking that maybe the ram is set wrong in the bios. the ram is 1600 and i thought maybe it is listed as 1066 or something then I thought also that maybe it is not a supported ram and what do you know it isnt. http://download.gigabyte.us/FileList...67a-ud3-b3.pdf my ram are CM3X2G1600C9NX from Corsair and I looked up and down on this pdf and this model is not listed. So should I contact the manufacturer and ask for a new set of ram?

                              Comment

                              Working...
                              X