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 BSODs on a new computer


  • Please log in to reply
21 replies to this topic

#1 chocobog

chocobog

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 10 October 2010 - 04:28 AM

Hello everyone,

I bought a new computer several weeks ago, and after some problems ("Bad Bios Checksum - Starting Bios recovery" when I started it),it worked very well with Win XP after I replaced a defectuous memory module.

So I installed Win 7, and since then I got several BSOD (mostly MEMORY_MANAGEMENT, and one time PFN_LIST_CORRUPT)


here is my piriform summary :
http://speccy.piriform.com/results/B8RE7A72pQwDOuyeobOlnT0

and here are the 3 latest dump reports I saved :


04/10/2010 :

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 4E, {99, 10d8ab, 0, 931ab}Page 12a06f not present in the dump file. Type ".hh dbgerr004" for detailsProbably caused by : memory_corruption ( nt!MiBadShareCount+4c )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************PFN_LIST_CORRUPT (4e)Typically caused by drivers passing bad memory descriptor lists (ie: callingMmUnlockPages twice with the same list, etc).  If a kernel debugger isavailable get the stack trace.Arguments:Arg1: 0000000000000099, A PTE or PFN is corruptArg2: 000000000010d8ab, page frame numberArg3: 0000000000000000, current page stateArg4: 00000000000931ab, 0Debugging Details:------------------BUGCHECK_STR:  0x4E_99DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  firefox.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff8000291c38c to fffff8000288c740STACK_TEXT:  fffff880`080dfe08 fffff800`0291c38c : 00000000`0000004e 00000000`00000099 00000000`0010d8ab 00000000`00000000 : nt!KeBugCheckExfffff880`080dfe10 fffff800`0282537c : e5d00001`0d8ab863 fffffa80`0328a010 00000000`00000000 00000d10`00000000 : nt!MiBadShareCount+0x4cfffff880`080dfe50 fffff800`02881d49 : 00000000`00000000 00000000`0000059a 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x47857fffff880`080dffb0 fffff800`029bd34f : 00000000`00000001 fffff800`02898772 00000000`00000000 fffff880`023e6000 : nt!MiFreePagedPoolPages+0x129fffff880`080e0100 fffff800`029c187c : 00000000`00000000 fffff880`080e02d0 fffff880`080e0240 00000000`00000001 : nt!MiFreePoolPages+0x343fffff880`080e0210 fffff960`00184bc8 : fffff900`c4200228 fffff880`080e0310 00000000`35316847 00000000`00000001 : nt!ExFreePoolWithTag+0x7ccfffff880`080e02c0 fffff960`0018539a : fffff900`c00b5010 fffff900`c4200000 00000000`00000000 fffff900`c4200228 : win32k!FreeObject+0x58fffff880`080e02f0 fffff960`00185534 : 00000000`00000000 fffff880`00000000 fffff900`c4200000 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x58afffff880`080e0440 fffff960`00146645 : 00000000`59050f81 fffff900`c4200000 00000000`00000f81 00000000`7efdb000 : win32k!bDeleteSurface+0x34fffff880`080e0470 fffff800`0288b993 : fffffa80`0698f060 fffff880`080e0520 00000000`09f60b60 00000000`10040404 : win32k!NtGdiDeleteObjectApp+0xd5fffff880`080e04a0 00000000`752f2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0016ce18 fffff800`02884080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752f2dd9fffff880`080e0880 fffff900`00000003 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCallUserModefffff880`080e0888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`080e0db0 : 0xfffff900`00000003STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiBadShareCount+4cfffff800`0291c38c cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiBadShareCount+4cFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cBUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cFollowup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************PFN_LIST_CORRUPT (4e)Typically caused by drivers passing bad memory descriptor lists (ie: callingMmUnlockPages twice with the same list, etc).  If a kernel debugger isavailable get the stack trace.Arguments:Arg1: 0000000000000099, A PTE or PFN is corruptArg2: 000000000010d8ab, page frame numberArg3: 0000000000000000, current page stateArg4: 00000000000931ab, 0Debugging Details:------------------BUGCHECK_STR:  0x4E_99DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  firefox.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff8000291c38c to fffff8000288c740STACK_TEXT:  fffff880`080dfe08 fffff800`0291c38c : 00000000`0000004e 00000000`00000099 00000000`0010d8ab 00000000`00000000 : nt!KeBugCheckExfffff880`080dfe10 fffff800`0282537c : e5d00001`0d8ab863 fffffa80`0328a010 00000000`00000000 00000d10`00000000 : nt!MiBadShareCount+0x4cfffff880`080dfe50 fffff800`02881d49 : 00000000`00000000 00000000`0000059a 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x47857fffff880`080dffb0 fffff800`029bd34f : 00000000`00000001 fffff800`02898772 00000000`00000000 fffff880`023e6000 : nt!MiFreePagedPoolPages+0x129fffff880`080e0100 fffff800`029c187c : 00000000`00000000 fffff880`080e02d0 fffff880`080e0240 00000000`00000001 : nt!MiFreePoolPages+0x343fffff880`080e0210 fffff960`00184bc8 : fffff900`c4200228 fffff880`080e0310 00000000`35316847 00000000`00000001 : nt!ExFreePoolWithTag+0x7ccfffff880`080e02c0 fffff960`0018539a : fffff900`c00b5010 fffff900`c4200000 00000000`00000000 fffff900`c4200228 : win32k!FreeObject+0x58fffff880`080e02f0 fffff960`00185534 : 00000000`00000000 fffff880`00000000 fffff900`c4200000 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x58afffff880`080e0440 fffff960`00146645 : 00000000`59050f81 fffff900`c4200000 00000000`00000f81 00000000`7efdb000 : win32k!bDeleteSurface+0x34fffff880`080e0470 fffff800`0288b993 : fffffa80`0698f060 fffff880`080e0520 00000000`09f60b60 00000000`10040404 : win32k!NtGdiDeleteObjectApp+0xd5fffff880`080e04a0 00000000`752f2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0016ce18 fffff800`02884080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752f2dd9fffff880`080e0880 fffff900`00000003 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCallUserModefffff880`080e0888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`080e0db0 : 0xfffff900`00000003STACK_COMMAND:  kbFOLLOWUP_IP: nt!MiBadShareCount+4cfffff800`0291c38c cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiBadShareCount+4cFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cBUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cFollowup: MachineOwner---------

06/10/2010 :
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1A, {41790, fffffa80021175b0, ffff, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000041790, The subtype of the bugcheck.Arg2: fffffa80021175b0Arg3: 000000000000ffffArg4: 0000000000000000Debugging Details:------------------BUGCHECK_STR:  0x1a_41790DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  explorer.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff80002937f9e to fffff800028c4740STACK_TEXT:  fffff880`0494c968 fffff800`02937f9e : 00000000`0000001a 00000000`00041790 fffffa80`021175b0 00000000`0000ffff : nt!KeBugCheckExfffff880`0494c970 fffff800`029060da : 00000000`00000000 00000000`12348fff fffffa80`00000000 fffffa80`0604b890 : nt! ?? ::FNODOBFM::`string'+0x33906fffff880`0494cb30 fffff800`028c3993 : ffffffff`ffffffff 00000000`04cfd920 00000000`04cfd8e8 00000000`00008000 : nt!NtFreeVirtualMemory+0x5cafffff880`0494cc20 00000000`7789009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`04cfd858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7789009aSTACK_COMMAND:  kbFOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33906fffff800`02937f9e cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33906FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906Followup: MachineOwner---------



10 / 10 / 2010 :
********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1A, {41790, fffffa8002171c70, ffff, 0}Probably caused by : CI.dll ( CI!I_PEVerifyBootDrivers+7ae )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000041790, The subtype of the bugcheck.Arg2: fffffa8002171c70Arg3: 000000000000ffffArg4: 0000000000000000Debugging Details:------------------BUGCHECK_STR:  0x1a_41790DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff80002b41f9e to fffff80002ace740STACK_TEXT:  fffff880`060ab508 fffff800`02b41f9e : 00000000`0000001a 00000000`00041790 fffffa80`02171c70 00000000`0000ffff : nt!KeBugCheckExfffff880`060ab510 fffff800`02b01df9 : 00000000`00000000 00000000`004aefff 00000000`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x33906fffff880`060ab6d0 fffff800`02de71d0 : fffffa80`06727410 0007ffff`00000000 fffffa80`0672af90 fffffa80`0672af90 : nt!MiRemoveMappedView+0xd9fffff880`060ab7f0 fffff800`02de75db : fffff880`00000000 00000000`003f0000 fffffa80`00000001 00000000`003f0000 : nt!MiUnmapViewOfSection+0x1b0fffff880`060ab8b0 fffff800`02acd993 : 00000000`00000000 fffff880`060abc28 fffffa80`03cd0040 00000000`00000000 : nt!NtUnmapViewOfSection+0x5ffffff880`060ab900 fffff800`02ac9f30 : fffff880`00ca206e 00000000`00000001 fffff880`031d7f40 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13fffff880`060aba98 fffff880`00ca206e : 00000000`00000001 fffff880`031d7f40 00000000`00000000 fffff8a0`00004500 : nt!KiServiceLinkagefffff880`060abaa0 fffff800`02e2aaec : 00000000`00000103 fffff880`00c90cb0 00000000`00000000 fffff880`00ca18c0 : CI!I_PEVerifyBootDrivers+0x7aefffff880`060abcb0 fffff880`00ca1875 : 00000000`00000001 00000000`00000080 00000000`00000008 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x4d5acfffff880`060abcf0 fffff800`02d72c06 : 00000000`00000005 fffff880`00000001 fffffa80`06726670 fffffa80`06726670 : CI!PEWorkerThread+0xadfffff880`060abd40 fffff800`02aacc26 : fffff880`031d3180 fffffa80`06726670 fffffa80`0670ab60 fffff880`01439bf0 : nt!PspSystemThreadStartup+0x5afffff880`060abd80 00000000`00000000 : fffff880`060ac000 fffff880`060a6000 fffff880`060aac90 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: CI!I_PEVerifyBootDrivers+7aefffff880`00ca206e 48895c2470      mov     qword ptr [rsp+70h],rbxSYMBOL_STACK_INDEX:  7SYMBOL_NAME:  CI!I_PEVerifyBootDrivers+7aeFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: CIIMAGE_NAME:  CI.dllDEBUG_FLR_IMAGE_TIMESTAMP:  4a5be01dFAILURE_BUCKET_ID:  X64_0x1a_41790_CI!I_PEVerifyBootDrivers+7aeBUCKET_ID:  X64_0x1a_41790_CI!I_PEVerifyBootDrivers+7aeFollowup: MachineOwner

thanks in advance for your precious help !

BC AdBot (Login to Remove)

 


#2 keyboardNinja

keyboardNinja

    Bleepin' Ninja


  • Members
  • 4,815 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh interwebz
  • Local time:04:43 PM

Posted 10 October 2010 - 11:41 AM

Hi there, chocobog. :huh:

:huh: to Bleeping Computer.

Did this computer come brand new with XP on it?? That seems odd to me...

Also, those crash dumps aren't very useful until you run them through BlueScreenView:

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
PICNIC - Problem In Chair, Not In Computer

Posted Image Posted Image

20 Things I Learned About Browsers and the Web

#3 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 10 October 2010 - 12:59 PM

hello keyboardNinja ! (cool nickname by the way)

thx for your answer !
In fact I bought the computer in separate pieces in an hardware shop (except the graphic card bought online), and I had them put together in this shop...
As I only had Win XP at this time, I installed it first, and then I switched to 7 !


Here is the result of BlueScreenView : 4 times out of 5, the crash is caused by ntoskrn.exe...

==================================================
Dump File : 101010-19203-01.dmp
Crash Time : 10/10/2010 10:55:49
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`02171c70
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\101010-19203-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 100610-12885-01.dmp
Crash Time : 06/10/2010 22:21:37
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`021175b0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100610-12885-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 100410-12838-01.dmp
Crash Time : 04/10/2010 21:47:02
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0010d8ab
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`000931ab
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1d290b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100410-12838-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 092910-14445-01.dmp
Crash Time : 29/09/2010 21:46:47
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`021175b0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\092910-14445-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 092610-26208-01.dmp
Crash Time : 26/09/2010 09:55:27
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`02171c70
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\092610-26208-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

Edited by chocobog, 10 October 2010 - 12:59 PM.


#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:43 PM

Posted 10 October 2010 - 01:49 PM

How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    Posted Image
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    Posted Image

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    Posted Image
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :huh:

Compliments of Billy O'Neal.

#5 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 14 October 2010 - 06:55 AM

hello,

I ran Memtest for 4hours this morning : no error has been detected...

#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:43 PM

Posted 14 October 2010 - 12:57 PM

I am not sure if Samsung makes diagnostic tools for their drives, but I would would down Data Life Guard tools from http://www.wdc.com and run it.

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:43 PM

Posted 16 October 2010 - 07:07 AM

Samsung uses the Hutil utility, http://www.samsung.com/global/business/hdd...port_HUTIL.html.

Louis

#8 rayj0054

rayj0054

  • Members
  • 126 posts
  • OFFLINE
  •  
  • Location:texas
  • Local time:05:43 PM

Posted 16 October 2010 - 08:27 PM

check your processor settings in setup that processor should be running about 2.9 ghz and the multiplier should be 14 from what i saw on speecy your not even running 1 ghx and your multiplier is x4 this could be conflicting with your memory since that processor has no L3 cache

#9 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 07 November 2010 - 08:03 AM

Hello everybody

thanks for your answer (I didn't have time to test my HDD until yesterday)

-For my WD HDD : Data Life Guard showed no errors

-For my Samsung HDD : I burned a CD with the ES tool, but my computer didn't boot on it. I used HD Tune, and here is the result :

HD Tune: SAMSUNG HD501LJ Error Scan
Scanned data : 476749 MB
Damaged Blocks : 0.0 %
Elapsed Time : 131:58

I don't really understand the processor settings...I didn't do anay o/c, so this must be the default values, and I'm not really comfortable with the idea of changing these...

#10 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 14 November 2010 - 04:01 PM

I add the BlueScreenView results I hadn't posted yet : still ntoskrnl.exe most of the times, but I also got one BOSD caused by dxgkrnl.sys and one caused by Ntfs.sys :

==================================================
Dump File : 111310-13135-01.dmp
Crash Time : 13/11/2010 10:30:20
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0226bd80
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\111310-13135-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 110710-13509-01.dmp
Crash Time : 07/11/2010 16:07:16
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`05260dfe
Parameter 3 : fffff880`05c330f0
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5fdfe
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\110710-13509-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 110510-14430-01.dmp
Crash Time : 05/11/2010 22:30:21
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`021175b0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\110510-14430-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 110110-25022-01.dmp
Crash Time : 01/11/2010 08:56:58
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`05f19bf8
Parameter 3 : fffff880`05f19460
Parameter 4 : fffff800`02acce2e
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+213d8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\110110-25022-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 101710-22729-01.dmp
Crash Time : 17/10/2010 14:55:56
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`021175b0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\101710-22729-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 101210-16411-01.dmp
Crash Time : 12/10/2010 17:41:15
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`02171c70
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\101210-16411-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

Edited by chocobog, 14 November 2010 - 04:02 PM.


#11 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:43 PM

Posted 14 November 2010 - 05:33 PM

Are you video card drivers updated along with everything else?

#12 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 15 November 2010 - 01:18 PM

they were when I started this topic...but now the audio and the video drivers were not updated anymore : I just updated them...we'll see if it solves the problem

#13 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 17 November 2010 - 02:43 PM

a new BSOD after I updated again my drivers :'(

==================================================
Dump File : 111710-14804-01.dmp
Crash Time : 17/11/2010 18:23:52
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0521a756
Parameter 3 : fffff880`06ec8ce0
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+2756
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\111710-14804-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

#14 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:43 PM

Posted 17 November 2010 - 06:46 PM

1 Thread on the web states that this issue was resolved by the OP replacing the CPU:

http://www.sevenforums.com/crashes-debugging/57287-dxgkrnl-sys-bsods-4.html

#15 chocobog

chocobog
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:43 AM

Posted 05 December 2010 - 07:43 AM

thanks for the link, there are some useful tips :

- I ran Memtest86+ for the whole night this time : no errors

- I ran CHKDSK /f/r
on the system partition (C:) : it cleaned some unused indexes
(if anyone speaks french : "CHKDSK est en train de vérifier les descripteurs de sécurité (étape 3 sur 5) 105472 SD/SID de fichiers traités. Nettoyage en cours de 341 entrées d’index inutilisées à partir de l’index $SII du fichier 0x9. Nettoyage en cours de 341 entrées d’index inutilisées à partir de l’index $SDH du fichier 0x9. Nettoyage en cours de 341 descripteurs de sécurité non utilisés. La vérification des descripteurs de sécurité est terminée") ==> BSODs still occur after this
on the other partitions, no problems detected...

- nothing has been detected by the free scan TrendMicro House Call

- to test the CPU, what software should I use ? Prime95 ? IntelBurnTest ? Cpu stability test ?
is it bad if the proc temperature goes over 60°C ?

another thing : the BSODs often occur just right After I do Start > Shut Down...does it mean something ?

Edited by chocobog, 05 December 2010 - 09:25 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users