Random crashes with pattern in event log

Page 1 of 2 12 LastLast

  1. Posts : 47
    Windows 7 Prof x64
       #1

    Random crashes with pattern in event log


    Hello Everyone,
    Can I get some help in relation to the above from you guys? It seems I do experience certain crashes for which I cannot find any possible explanation. There are few similar threads out there where similar events in the event log occur near the crash, but I haven't been able to resolve my issue after their examining. First of all my PC specs:

    Win 7 Prof X64
    AMD Phenom II x4 955BE
    GA-790FXTA-UD5 F2
    Corsair Dominator 4 x 2GB CL7 CMD8GX3M4A1333C7
    MSI N460GTX Cyclone 678 D5 OC/Sapphire Radeon HD 5870 Vapor-X 2GB
    Cooler Master Silent Pro M700 700W 80+
    +3.3V - 28 A
    +5V - 25 A
    +12V1 - 50 A
    -12V - 0,5 A
    +5VSB - 2,5 A

    None of the components has been overclocked. All the drivers are up to date. The GPU is a stock overclock, and the crashes occur both with Nvidia and ATI. (I have Nvidia now as my HD 5870 has been RMA'd). RAM was checked by Memtest - OK ( although I might do few more continuous runs later on as per suggestions in the different forums).

    The crash relates to Kernel Power errors. I have only two dumps from the said crashes (they both relate, I think, to the graphics - see attached zip's).

    Attachment 115031

    Attachment 115032

    The remaining crashes for which I'm going to put the event log excerpts, ended up with hard resets and no crash dump file.

    If you have a look at the event log below, you'll see that there are two events before the kernel power crash that have sth to do with Microsoft Filter Manager. Both are exactly the same, and even all the values are exactly the same. There is one more thing that I've just noticed; other event, just before those two filter manager events is very odd; it says that "the operating system has been launched at the (time given plus couple of digits and letters). This particular event always comes BEFORE the filter manager events and approx 8-10 seconds BEFORE!! the crash.. Isn't it weird? The crashes happen only during gaming in 3D mode, never in 2D mode. Please note this event is not included in the piece below.

    The following is the excerpt from the event log in relation to the filter manager and crash events (all other crashes are preceded with EXACTLY the same filter manager events - even the alpha numeric strings are the same) Please note I'm Polish, the OS is Polish version as well, and I'll do my best to translate all the details highlighted in red into English (if you need to have more details translated please let me know:


    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-Kernel-Power
    Data: 2010-11-05 13:39:39
    Identyfikator zdarzenia:41
    Kategoria zadania: (63)
    Poziom: Krytyczne
    Słowa kluczowe: (2)
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    System został uruchomiony ponownie bez uprzedniego czystego zamknięcia. Przyczyną tego błędu może być fakt, że system przestał odpowiadać, uległ awarii lub nastąpiła nieoczekiwana utrata zasilania (The system has been booted again without a previous clean shutdown. The reason for this error might be the fact that the system stopped responding, malfunctioned or there was a sudden power loss).
    Kod XML zdarzenia:
    <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-11-05T13:39:39.487213900Z" />
    <EventRecordID>20131</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">59</Data>
    <Data Name="BugcheckParameter1">0xc0000005</Data>
    <Data Name="BugcheckParameter2">0xfffff880049a1c8e</Data>
    <Data Name="BugcheckParameter3">0xfffff88008e318c0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>

    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-FilterManager
    Data: 2010-11-05 13:39:39
    Identyfikator zdarzenia:6
    Kategoria zadania:Brak
    Poziom: Informacje
    Słowa kluczowe:
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    Filtr systemu plik๓w MpFilter (6.1, ?2010?-?03?-?20T05:58:08.000000000Z) został pomyślnie załadowany i zarejestrował się w menedżerze filtr๓w ((The filter for files system MpFilter has been loaded and it registered itself in the filter manager).
    Kod XML zdarzenia:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-FilterManager" Guid="{F3C5E28E-63F6-49C7-A204-E48A1BC4B09D}" />
    <EventID>6</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-05T13:39:39.440413900Z" />
    <EventRecordID>20126</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="FinalStatus">0x0</Data>
    <Data Name="DeviceVersionMajor">6</Data>
    <Data Name="DeviceVersionMinor">1</Data>
    <Data Name="DeviceNameLength">8</Data>
    <Data Name="DeviceName">MpFilter</Data>
    <Data Name="DeviceTime">2010-03-20T05:58:08.000000000Z</Data>
    </EventData>
    </Event>

    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-FilterManager
    Data: 2010-11-05 13:39:31
    Identyfikator zdarzenia:6
    Kategoria zadania:Brak
    Poziom: Informacje
    Słowa kluczowe:
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    Filtr systemu plik๓w FileInfo (6.1, ?2009?-?07?-?13T23:34:25.000000000Z został pomyślnie załadowany i zarejestrował się w menedżerze filtr๓w. (The filter for files system FileInfo has been loaded and it registered itself in the filter manager))
    Kod XML zdarzenia:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-FilterManager" Guid="{F3C5E28E-63F6-49C7-A204-E48A1BC4B09D}" />
    <EventID>6</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-05T13:39:31.702800400Z" />
    <EventRecordID>20125</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="FinalStatus">0x0</Data>
    <Data Name="DeviceVersionMajor">6</Data>
    <Data Name="DeviceVersionMinor">1</Data>
    <Data Name="DeviceNameLength">8</Data>
    <Data Name="DeviceName">FileInfo</Data>
    <Data Name="DeviceTime">2009-07-13T23:34:25.000000000Z</Data>
    </EventData>
    </Event>

    Please HELP!!

    Thank you.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Ukiii said:
    Hello Everyone,
    Can I get some help in relation to the above from you guys? It seems I do experience certain crashes for which I cannot find any possible explanation. There are few similar threads out there where similar events in the event log occur near the crash, but I haven't been able to resolve my issue after their examining. First of all my PC specs:

    Win 7 Prof X64
    AMD Phenom II x4 955BE
    GA-790FXTA-UD5 F2
    Corsair Dominator 4 x 2GB CL7 CMD8GX3M4A1333C7
    MSI N460GTX Cyclone 678 D5 OC/Sapphire Radeon HD 5870 Vapor-X 2GB
    Cooler Master Silent Pro M700 700W 80+
    +3.3V - 28 A
    +5V - 25 A
    +12V1 - 50 A
    -12V - 0,5 A
    +5VSB - 2,5 A

    None of the components has been overclocked. All the drivers are up to date. The GPU is a stock overclock, and the crashes occur both with Nvidia and ATI. (I have Nvidia now as my HD 5870 has been RMA'd). RAM was checked by Memtest - OK ( although I might do few more continuous runs later on as per suggestions in the different forums).

    The crash relates to Kernel Power errors. I have only two dumps from the said crashes (they both relate, I think, to the graphics - see attached zip's).

    Attachment 115031

    Attachment 115032

    The remaining crashes for which I'm going to put the event log excerpts, ended up with hard resets and no crash dump file.

    If you have a look at the event log below, you'll see that there are two events before the kernel power crash that have sth to do with Microsoft Filter Manager. Both are exactly the same, and even all the values are exactly the same. There is one more thing that I've just noticed; other event, just before those two filter manager events is very odd; it says that "the operating system has been launched at the (time given plus couple of digits and letters). This particular event always comes BEFORE the filter manager events and approx 8-10 seconds BEFORE!! the crash.. Isn't it weird? The crashes happen only during gaming in 3D mode, never in 2D mode. Please note this event is not included in the piece below.

    The following is the excerpt from the event log in relation to the filter manager and crash events (all other crashes are preceded with EXACTLY the same filter manager events - even the alpha numeric strings are the same) Please note I'm Polish, the OS is Polish version as well, and I'll do my best to translate all the details highlighted in red into English (if you need to have more details translated please let me know:


    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-Kernel-Power
    Data: 2010-11-05 13:39:39
    Identyfikator zdarzenia:41
    Kategoria zadania: (63)
    Poziom: Krytyczne
    Słowa kluczowe: (2)
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    System został uruchomiony ponownie bez uprzedniego czystego zamknięcia. Przyczyną tego błędu może być fakt, że system przestał odpowiadać, uległ awarii lub nastąpiła nieoczekiwana utrata zasilania (The system has been booted again without a previous clean shutdown. The reason for this error might be the fact that the system stopped responding, malfunctioned or there was a sudden power loss).
    Kod XML zdarzenia:
    <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-11-05T13:39:39.487213900Z" />
    <EventRecordID>20131</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">59</Data>
    <Data Name="BugcheckParameter1">0xc0000005</Data>
    <Data Name="BugcheckParameter2">0xfffff880049a1c8e</Data>
    <Data Name="BugcheckParameter3">0xfffff88008e318c0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>

    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-FilterManager
    Data: 2010-11-05 13:39:39
    Identyfikator zdarzenia:6
    Kategoria zadania:Brak
    Poziom: Informacje
    Słowa kluczowe:
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    Filtr systemu plik๓w MpFilter (6.1, ?2010?-?03?-?20T05:58:08.000000000Z) został pomyślnie załadowany i zarejestrował się w menedżerze filtr๓w ((The filter for files system MpFilter has been loaded and it registered itself in the filter manager).
    Kod XML zdarzenia:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-FilterManager" Guid="{F3C5E28E-63F6-49C7-A204-E48A1BC4B09D}" />
    <EventID>6</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-05T13:39:39.440413900Z" />
    <EventRecordID>20126</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="FinalStatus">0x0</Data>
    <Data Name="DeviceVersionMajor">6</Data>
    <Data Name="DeviceVersionMinor">1</Data>
    <Data Name="DeviceNameLength">8</Data>
    <Data Name="DeviceName">MpFilter</Data>
    <Data Name="DeviceTime">2010-03-20T05:58:08.000000000Z</Data>
    </EventData>
    </Event>

    Nazwa dziennika:System
    Źr๓dło: Microsoft-Windows-FilterManager
    Data: 2010-11-05 13:39:31
    Identyfikator zdarzenia:6
    Kategoria zadania:Brak
    Poziom: Informacje
    Słowa kluczowe:
    Użytkownik: SYSTEM
    Komputer: Luki-Komputer
    Opis:
    Filtr systemu plik๓w FileInfo (6.1, ?2009?-?07?-?13T23:34:25.000000000Z został pomyślnie załadowany i zarejestrował się w menedżerze filtr๓w. (The filter for files system FileInfo has been loaded and it registered itself in the filter manager))
    Kod XML zdarzenia:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-FilterManager" Guid="{F3C5E28E-63F6-49C7-A204-E48A1BC4B09D}" />
    <EventID>6</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-05T13:39:31.702800400Z" />
    <EventRecordID>20125</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Luki-Komputer</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="FinalStatus">0x0</Data>
    <Data Name="DeviceVersionMajor">6</Data>
    <Data Name="DeviceVersionMinor">1</Data>
    <Data Name="DeviceNameLength">8</Data>
    <Data Name="DeviceName">FileInfo</Data>
    <Data Name="DeviceTime">2009-07-13T23:34:25.000000000Z</Data>
    </EventData>
    </Event>

    Please HELP!!

    Thank you.

    Both of the 2 DMP files enclosed were caused by the video driver. Use these instructions to remove and re-install


    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    When it is removed then download and install the fresh copy.


    Let us know if you need further assistance


    Ken J
      My Computer


  3. Posts : 47
    Windows 7 Prof x64
    Thread Starter
       #3

    Thank you Ken J,

    I already did that. It didn't help. The GPU i have right now has been installed after uninstalling my 5870, and the OS was cleaned by Driver Sweeper from the old drivers in safe mode. Any othersuggestions?
      My Computer


  4. Posts : 47
    Windows 7 Prof x64
    Thread Starter
       #4

    Is there no one who could have a look at this issue?
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    We will need any memory dump files that have occurred since you've updated the video drivers. That will enable us to see if there's another cause.

    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    Also, please try this procedure:
    SFC.EXE /SCANNOW
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
    In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
    Let the program run and post back what it says when it's done.
    Finally, please post this information for us to have a look at. The additional reports will be of value even if you aren't having any more BSOD's: https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  6. Posts : 47
    Windows 7 Prof x64
    Thread Starter
       #6

    Hello Usasma,
    Thank you for taking your time to help with the matter.

    I've done few of the suggested actions:

    Sysytem File Check - reported full OS integrity
    Malware check (ESET) - no threats found (I do use Microsoft Security Essentials)

    Memtest86+:
    I had two sessions not long ago which didn't show any issues with RAM chips. I did however run only one pass of the test, hence I will repeat it again and run for at least three passes (as suggested in your website - nice one btw).

    When it comes to the HDD test, I have Samsung Spinpoint F3 HD502HJ with the OS on it. It seems that the DOS application HUTIL from Samsung's website does not support my model. Should I use it anyway??

    Thanks.
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #7

    Give the Samsung test a try. If it doesn't work for you, then try these:
    - Seagate Seatools
    - Hitachi Drive Fitness Test
    - HDTune
      My Computer


  8. Posts : 47
    Windows 7 Prof x64
    Thread Starter
       #8

    I've just experienced another crash while playing game in 3D mode.
    Below you'll find BSOD dump and System File Collection zip attached.

    EDIT:
    I'm not sure if what's in the attachment is in English or Polish. Let me know if you encounter any linguistci issues.
    Last edited by Ukiii; 22 Nov 2010 at 12:55. Reason: additional info
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    Have you run the hard drive test?

    The perfmon report shows:
    NVIDIA High Definition Audio is disabled
    Realtek PCIe GBE Family Controller is disabled
    Is this deliberate? If so, why?

    I suspect your video card. First, please do the following:
    - download the Drivers Only for your video card (DO NOT download the entire Catalyst Control Center)
    - uninstall the ATI stuff from your system using Control Panel...Programs...Uninstall a program
    - install the freshly downloaded Driver Only package and monitor for further BSOD's


    Then, please run Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    Because of the different BSOD error codes, please also run these free stress tests (DON'T run when running Driver Verifier):
    FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    - Click "Quit" to exit
    Prime95 download site: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    This won't necessarily crash the system - but check the output in the test window for errors.
    The Test selection box and the stress.txt file describes what components that the program stresses.
    More details on the use of this test: Torture test your CPU with Prime95
    Two other video stress tests (may be more stressful than FurMark):
    Video Memory stress Test - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
    Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
    Sorry, but I don't read the language that this website is made in.
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov 22 09:52:27.427 2010 (UTC - 5:00)
    System Uptime: 0 days 6:19:12.160
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )
    BUGCHECK_STR:  0xc2_7
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Addon.exe
    Bugcheck code 000000C2
    Arguments 00000000`00000007 00000000`00001097 00000000`0022dff8 fffffa80`00e96a20
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Nov 16 11:58:44.341 2010 (UTC - 5:00)
    System Uptime: 0 days 8:45:51.699
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    Bugcheck code 1000007E
    Arguments ffffffff`c0000005 fffff880`03f79cf7 fffff880`038ff6a8 fffff880`038fef10
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Nov  5 08:39:00.779 2010 (UTC - 5:00)
    System Uptime: 0 days 4:51:36.090
    Probably caused by : atikmdag.sys ( atikmdag+383c8e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Addon.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff880`049a1c8e fffff880`08e318c0 00000000`00000000
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
      
      My Computer


  10. Posts : 47
    Windows 7 Prof x64
    Thread Starter
       #10

    Have you run the hard drive test?
    Hi Usasma,

    Well, i don't know what's going on but i tried to use HDTune and it crashed twice while I was trying to error scan the Samsung. What's more, there are only two lines under "health" tab, whereas my second disk WD Caviar Black shows at least 15.

    Samsung Health Tab:
    Attachment 116949

    each time I try to switch to Samsung view, HDTune crashes. would it not have HDD SMART enabled? God, I think I'll simply buy new HDD and work away with the new one...

    There is another view from Crystal Disk Info:

    Caviar
    Attachment 116958


    Samsung
    Attachment 116957


    What's going on???
      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 09:34.
Find Us