BSOD Randomly after start up

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Home Premium 64bit
       #1

    BSOD Randomly after start up


    For some reason everytime my computer gets fixed, it keeps bsoding after about 1-3 months

    I recent reformatted the comp and it keeps bsoding me at random

    It doesn't have any special causes

    It seems to do it whenever it wants to

    I have a Windows 7 Home premium 64 bit OS
    AMD Athlon II X4 640 processor
    ATI Radeon HD 4200

    It seems to be more active after the windows update

    I tried multiple times to get the perfmon report but it bsods before it even finished.
      My Computer


  2. Posts : 845
    Windows 7 - Vista
       #2

    Hi -

    A few strange items found in the system files.

    One dump file in the zip; at least 6 BSODs recorded -
    Code:
    1/5/2012 6:39 PM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010512-17191-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-40919-0.sysdata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0e130bc2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 010512-17191-01
Report Status: 0
    1/6/2012 4:51 PM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010612-22432-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-35755-0.sysdata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a9cca8e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 010612-22432-01
Report Status: 0
    1/7/2012 12:57 AM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010612-23946-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-45193-0.sysdata.xml

These files may be available here:
C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0568e771

Analysis symbol: 
Rechecking for solution: 0
Report Id: 010612-23946-01
Report Status: 0
    5/4/2011 8:01 AM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\050411-20108-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-35053-0.sysdata.xml

These files may be available here:
C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_057cc16a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 050411-20108-01
Report Status: 0
    5/4/2011 9:05 AM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\050411-30685-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-40435-0.sysdata.xml

These files may be available here:
C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_051ccf5f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 050411-30685-01
Report Status: 0
    5/4/2011 9:14 AM	Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\050411-23010-01.dmp
C:\Users\Kevin\AppData\Local\Temp\WER-32760-0.sysdata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0af9a86e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 050411-23010-01
Report Status: 0
    Windows 7 was reinstalled just 2 days ago. The dates of the BSODs puzzled me, then I noticed system time changes throughout the Event Viewer, which match the 2011 dumps. System time should not change like this.

    The most recent entry is listed first; the numbers in <> = the # of entries between events -
    Code:
      Date: 2012-01-06T16:58:55.011
      Date: 2012-01-06T16:57:19.597
    <  2,900 >
      Date: 2012-01-06T09:52:54.005
      Date: 2011-05-04T10:52:40.000
    <   500 >
      Date: 2011-05-04T01:00:22.593
      Date: 2012-01-06T08:52:06.098
    <  8,100 >  
      Date: 2012-01-04T08:38:57.718
      Date: 2011-10-07T07:53:44.610
    <     10 >
      Date: 2011-10-07T07:53:40.258   
    < 20,380 >
      Date: 2012-01-04T08:41:04.000
      Date: 2011-10-07T07:53:40.227

    The logs also show -
    - 144 Windows Updates
    - Windows 7 SP1 is NOT installed
    - app crashes - Malwarebytes, Apple iTunes, halo2, IE, Windows Updates, etc...
    - app installs from drive z: (possibly Halo 2 for Windows Vista..?)
    - WinMount drivers - http://sysnative.com/drivers/driver.php?id=wmdrive.sys
    - LIVE gaming on Windows Runtime Version 1.0.6027

    It appears that all went downhill after Live Gaming was installed, but the time change remains unexplained.

    I suggest that you reinstall Windows 7 again via the HP HDD Recovery partition. When you reach Desktop, allow ALL Windows Updates to come in, including SP1, before installing iTunes, virtual drives, games, etc...

    One other item - your 2x2 GB RAM. Config:
    - 1x2 GB Samsung
    - 1x2 GB Ramaxel

    Was the Ramaxel RAM added? I would test the RAM - Run memtest86+


    The single dump file pointed to video as the likely cause.

    Be sure to go to HP Support and update device drivers for your HP Pavilion p6727c Desktop PC. There is also a BIOS update available -

    http://h10025.www1.hp.com/ewfrf/wc/s...t=5053900#N138

    Regards. . .

    jcgriff2


    `



    Code:
    
    Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\010612-23946-01.dmp]
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Debug session time: Fri Jan  6 19:55:34.865 2012 (GMT-5)
    System Uptime: 0 days 6:32:53.400
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::WaitForEventsOrVerticalBlankEvent+cf )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_0xA_dxgkrnl!DXGADAPTER::WaitForEventsOrVerticalBlankEvent+cf
    Bugcheck code 0000000A
    Arguments 00000000`00003ca0 00000000`00000002 00000000`00000001 fffff800`02cc07a6
    BiosVersion = 6.07
    BiosReleaseDate = 05/04/2011
    SystemManufacturer = Hewlett-Packard
    SystemProductName = p6727c
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    hello jcgriff2

    I'm a bit paranoid since the bsods destroyed my computer about 3 times so i had to return it to hp since it would not even start up anything.

    For the Timeskip - I'm not 100% sure but there was a checksum error one time and i think the date/time all went back after that

    I did reformat the whole computer with a HP_RECOVERY hard drive that came with my computer.

    Maybe it's just me, but bsods seem to occur more often when i install the updates for W7. BSODS for ntoskrnl.exe start showing after a windows update more often.

    And for the ram. It came with the whole HP package, so new ones were not added. I did rearrange them once though and it went through memtest with no problems.

    So I will try updating it once again. *crosses fingers* I hope the BSODs don't come back to haunt me.

    Thank you for the response. I will try to update if any BSODs occur after it.
      My Computer


  4. Posts : 845
    Windows 7 - Vista
       #4

    Hi -

    I can only imagine the utter frustration you have endured dealing with this system & BSODs. Please know that BSODs themselves do not actually destroy a system, rather BSODs result when hardware &/or software within the system malfunctions. Think of the dreaded "check engine" light in your car. It tells you something is wrong and can often provide enough coded info to pinpoint the problem if it's within its scope of operation. BSOD kernel mini memory dumps are incapable of telling us the exact piece of hardware that is failing (assuming h/w is the cause).

    For the Timeskip - I'm not 100% sure but there was a checksum error one time and i think the date/time all went back after that
    Where did this checksum error appear? The time didn't change just once. Only the date advance in blue is normal. These are the dates in chronological order that occurred over a 2 day period -
    2011-10-07
    2012-01-04
    2011-10-07
    2012-01-04
    2012-01-06

    2011-05-04
    2012-01-06



    I did reformat the whole computer with a HP_RECOVERY hard drive that came with my computer.

    Maybe it's just me, but bsods seem to occur more often when i install the updates for W7. BSODS for ntoskrnl.exe start showing after a windows update more often.
    HP Recovery info - http://h10025.www1.hp.com/ewfrf/wc/d...roduct=5053900

    No, it's not you at all. I saw 100s of Windows Updates failures in the logs. What shocked me was to find 144 did install, yet no sign of Windows 7 SP1.

    And for the ram. It came with the whole HP package, so new ones were not added. I did rearrange them once though and it went through memtest with no problems.
    I asked about the RAM because 2 different manufacturers are listed -
    - 1x2 GB Samsung
    - 1x2 GB Ramaxel

    I don't know anything about Ramaxel or why HP would not match the sticks.

    I mentioned the BIOS update because it covers quite a bit. Just be sure the mobo listed is in fact the same one in your system - http://h10025.www1.hp.com/ewfrf/wc/s...53900&sw_lang=

    Did you buy the system new? If so, when?

    If there is any chance of getting HP Support to help you here, I would do so.

    Regards. . .

    jcgriff2
    Last edited by jcgriff2; 07 Jan 2012 at 08:33. Reason: typo
      My Computer


  5. Posts : 78
    Win 7
       #5

    Seeing the info on the SPD tab of CPUz for both occupied slots may also shed more light on the ram discrepancy. CPUID - System & hardware benchmark, monitoring, reporting
      My Computer


  6. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    I bout the system about a year ago

    11 months to be exact

    I am not sure about the checksum error ans it flashed on screen after I got something to eat :S then turned off

    Also I dled the HP bios update and it caused 2 blue screens

    1 which didn't end up in a dump
    But one did

    then the computer when i tried turning it on. it had these random numbers of (((( on screen constantly changing then i turned it off then it wouldnt turn on at all. So then i took off the power supply for about 5 minutes. plugged it back in and it worked. of course the screen glitched out once after that.

    now i am writing this on safe mode.

    @Wrench the screen got a seizure and stopped when i clicked the set up for cpuz. not sure if that was the reason.
      My Computer


  7. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    also the dump
      My Computer


  8. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    anyone know how i could revert back the bios?
      My Computer


  9. Posts : 78
    Win 7
       #9

    Sounds like the flash was either the wrong bios or did not complete, how did you flash it from within Windows or the dos boot method?
      My Computer


  10. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    Wrench97 said:
    Sounds like the flash was either the wrong bios or did not complete, how did you flash it from within Windows or the dos boot method?
    downloaded it and installed it from within windows

    i tried making the settings in the bios settings to default

    im not sure if its working or not yet

    im still waiting for a freeze.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 17:08.
Find Us