Tech Support Forum banner
Status
Not open for further replies.

BSOD on startup just before login screen Locale ID: 1033

2K views 19 replies 3 participants last post by  writhziden 
#1 ·
Computer Specs:
Processor - AMD A6=3670 APU with Radeon(tm) HD Graphics 2.70 GHz
Ram - 4GB
System type - Windows 7 64-bit service pack 1
Hard drive - 465GB
Graphics card - Nvidia Gforce 550ti
PSU - CiT 750W Gold Edition PSU
Motherboard - Gigabyte A55M-S2V
Computer is less than a year old, around 7 months.
 

Attachments

#2 · (Edited)
Hi -

The dumps were rather inconclusive.

Check for a driver update for the first one listed.
VM is always suspect.

Avast had some problems in the last few months, so please update your Avast program installation. Use the removal tool to uninstall vurrent version -

http://kb.eset.com/esetkb/index?page=content&id=SOLN146

Code:
[font=lucida console]
GKUPRO2D.sys                Fri Feb 18 04:57:02 2005 (4215BBEE) - Gemplus - CCID USB Smart Card Reader/Dell Smart Card Reader Keyboard drivers

VBoxDrv.sys                 Fri Oct 26 13:00:50 2012 (508AC1C2) - VM
VBoxUSBMon.sys              Fri Oct 26 12:59:41 2012 (508AC17D)- VM

aswFsBlk.SYS                Tue Oct 30 18:43:04 2012 (509057F8) - Avast
aswMonFlt.sys               Tue Oct 30 18:43:09 2012 (509057FD) - Avast
aswSP.SYS                   Tue Oct 30 18:44:06 2012 (50905836) - Avast
aswSnx.SYS                  Tue Oct 30 18:44:08 2012 (50905838) - Avast
aswTdi.SYS                  Tue Oct 30 18:43:16 2012 (50905804) - Avast
aswrdr2.sys                 Mon Oct  8 04:23:43 2012 (50728D8F) - Avast[/font]
http://www.sysnative.com/drivers/driver.php?id=GKUPRO2D.sys
http://www.sysnative.com/drivers/driver.php?id=VBoxDrv.sys
http://www.sysnative.com/drivers/driver.php?id=VBoxUSBMon.sys
http://www.sysnative.com/drivers/driver.php?id=aswFsBlk.SYS

After that, run Driver Verifier; see if it flags any 3rd party drivers - http://www.techsupportforum.com/for...-windows-7-and-vista-bsod-related-473665.html

Let it run for at least 24 hours or BSOD. The hope here is that Driver Verifier will find fault with a 3rd party driver and force a BSOD.

Regards. . .

jcgriff2


BSOD SUMMARY
Code:
[font=lucida console]
Debug session time: Mon Dec 17 11:44:33.768 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\121712-19734-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:00:28.532
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+bfd37 )
BugCheck 3B, {c0000005, fffff8000357a314, fffff88005d64050, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000357a314, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005d64050, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+bfd37

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Sat Dec 15 12:06:42.311 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\121512-21637-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:00:24.090
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BugCheck 1E, {0, 0, 0, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Bugcheck code 0000001E
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BiosVersion = F7
BiosReleaseDate = 04/12/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-A55M-S2V
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=http://sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


[/font]
 
#5 ·
Okay thankyou very much, been running it for a while now. Around 4 hours, will continue to until 24 hours. I just opened it up to check the information and noticed this

As you can see one of the drivers it not loaded, i'm not sure what it is and whether it is meant to be not loaded so thought i would just show you :) thanks.
 
#10 ·
Recommendations:
avast! is involved in your most recent crashes. Remove it and replace it with Microsoft Security Essentials to see if the system is more stable.

If that does not resolve the crashes, the crashes may be due to a memory module issue. Provide the following information about your hardware so we can check compatibility:
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:
  1. generate the images using the Snipping Tool,
  2. go to where the images are saved,
  3. right click in a blank area within the folder where the images are saved,
  4. create a new folder,
  5. name the folder CPUZ,
  6. select all the images,
  7. place the pointer over an image,
  8. press and hold down the left mouse button and drag the image (all images should move with it),
  9. drop the images into the CPUZ directory you created,
  10. create a compressed (zipped) folder of CPUZ
  11. upload the .zip file to the forums.

Run some memory related diagnostics:
NOTE:
  • If you are overclocking any hardware, please stop.
  • Run Display card memory tests to check the display card for memory problems.

  • Run Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

  • Run Prime95 to test your CPU, RAM modules, and general hardware.




Outdated and Problematic Drivers:
You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers. If you have ASACPI.sys installed, make sure it is updated and not pre-2009; pre-2009 versions are known to cause BSODs:

GKUPRO2D.sys Fri Feb 18 02:57:02 2005 (4215BBEE)
Gemplus - CCID USB Smart Card Reader/Dell Smart Card Reader Keyboard drivers
http://www.carrona.org/drivers/driver.php?id=GKUPRO2D.sys

dtsoftbus01.sys Fri Jan 13 06:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys


To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if possible.


Software Concerns:
Code:
Start Menu\Programs\ASUS\ASUS SmartDoctor
Remove the above software. It may be causing conflicts due to its interface with your hardware.


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:
Code:
[font=lucida console]**************************Thu Dec 20 09:06:03.135 2012 (UTC - 7:00)**************************
[COLOR=RED][B]GKUPRO2D.sys                Fri Feb 18 02:57:02 2005 (4215BBEE)[/B][/COLOR]
athrx.sys                   Fri Nov  6 13:56:02 2009 (4AF48D62)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
amdide64.sys                Tue Mar 30 08:48:25 2010 (4BB20F39)
usbfilter.sys               Wed Dec 15 03:34:49 2010 (4D0899C9)
speedfan.sys                Fri Mar 18 10:08:46 2011 (4D83838E)
Rt64win7.sys                Tue Aug 23 07:55:41 2011 (4E53B15D)
RTKVHD64.sys                Thu Aug 25 20:51:31 2011 (4E570A33)
nvhda64v.sys                Tue Jul  3 09:25:04 2012 (4FF30ED0)
nvlddmkm.sys                Tue Oct  2 12:21:13 2012 (506B3099)
aswrdr2.sys                 Mon Oct  8 02:23:43 2012 (50728D8F)
aswFsBlk.SYS                Tue Oct 30 16:43:04 2012 (509057F8)
aswMonFlt.sys               Tue Oct 30 16:43:09 2012 (509057FD)
aswTdi.SYS                  Tue Oct 30 16:43:16 2012 (50905804)
aswSP.SYS                   Tue Oct 30 16:44:06 2012 (50905836)
aswSnx.SYS                  Tue Oct 30 16:44:08 2012 (50905838)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 19 07:39:44.521 2012 (UTC - 7:00)**************************
IOMap64.sys                 Thu Feb  4 18:55:34 2010 (4B6B7A96)
Rt64win7.sys                Tue May 31 21:15:51 2011 (4DE5AEE7)
RTKVHD64.sys                Thu Aug 11 23:28:04 2011 (4E44B9E4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 17 09:44:33.768 2012 (UTC - 7:00)**************************
VBoxUSBMon.sys              Fri Oct 26 10:59:41 2012 (508AC17D)
VBoxDrv.sys                 Fri Oct 26 11:00:50 2012 (508AC1C2)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 15 10:06:42.311 2012 (UTC - 7:00)**************************
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 06:45:46 2012 (4F10358A)[/B][/COLOR]
[/font]
http://www.carrona.org/drivers/driver.php?id=GKUPRO2D.sys
http://www.carrona.org/drivers/driver.php?id=athrx.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amdide64.sys
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=aswrdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswFsBlk.SYS
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswTdi.SYS
http://www.carrona.org/drivers/driver.php?id=aswSP.SYS
http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys



Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
Code:
[font=lucida console]**************************Thu Dec 20 09:06:03.135 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\122012-23462-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:32.524[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]A, {144d0bb8bf, 2, 0, fffff800034c64ab}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Arguments: 
Arg1: 000000144d0bb8bf, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800034c64ab, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
  BIOS Version                  F7
  BIOS Release Date             04/12/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-A55M-S2V
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 20 09:04:56.538 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\122012-24492-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:16.317[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!RtlClearBits+17 )[/B]
BugCheck [B]50, {fffff8a001f8d1c8, 0, fffff800034ad047, 2}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arguments: 
Arg1: fffff8a001f8d1c8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800034ad047, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_nt!RtlClearBits+17[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 19 07:39:44.521 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\121912-20919-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:01:31.301[/B]
Probably caused by :[B]memory_corruption ( nt!MiGetTopLevelPfn+65 )[/B]
BugCheck [B]3B, {c0000005, fffff80003553d35, fffff8800878bc80, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003553d35, Address of the instruction which caused the bugcheck
Arg3: fffff8800878bc80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_VRF_nt!MiGetTopLevelPfn+65[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 18 08:55:56.270 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\121812-17425-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:08.644[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]24, {1904fb, fffff880037ca3f8, fffff880037c9c50, fffff880012ad885}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000024]NTFS_FILE_SYSTEM (24)[/url]
Arguments: 
Arg1: 00000000001904fb
Arg2: fffff880037ca3f8
Arg3: fffff880037c9c50
Arg4: fffff880012ad885
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 17 09:44:33.768 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\121712-19734-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:28.532[/B]
Probably caused by :[B]win32k.sys ( win32k!xxxInitProcessInfo+df )[/B]
BugCheck [B]3B, {c0000005, fffff8000357a314, fffff88005d64050, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000357a314, Address of the instruction which caused the bugcheck
Arg3: fffff88005d64050, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]csrss.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_win32k!xxxInitProcessInfo+df[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 15 10:06:42.311 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\DeccyFitz\Windows7_Vista_jcgriff2\121512-21637-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:00:24.090[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]AvastSvc.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
  BIOS Version                  F7
  BIOS Release Date             04/12/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-A55M-S2V
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
 
#12 ·
Rounding errors in Prime95 typically indicate a RAM fault. I would recommend doing an RMA of the RAM. Contact the manufacturer of the RAM and ask for a replacement under warranty.

The rounding errors could also be due to a bad processor, but that is very uncommon, which is why I recommend replacing the RAM first under warranty.
 
#14 ·
I mean the company that has its name on the RAM module itself. If you need help determining that, you can upload the CPU-Z images.
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:
  1. generate the images using the Snipping Tool,
  2. go to where the images are saved,
  3. right click in a blank area within the folder where the images are saved,
  4. create a new folder,
  5. name the folder CPUZ,
  6. select all the images,
  7. place the pointer over an image,
  8. press and hold down the left mouse button and drag the image (all images should move with it),
  9. drop the images into the CPUZ directory you created,
  10. create a compressed (zipped) folder of CPUZ
  11. upload the .zip file to the forums.
 
#19 ·
I'm not sure if this helps but when i play high intensity games such as far cry 3 and assassins creed 3 I get flashing lights, graphical flickering and then the game crashes to desktop after 20 minutes of playing. Maybe this could also be causes by the same thing as the BSOD.
 
#20 ·
You could try bumping the VCore by 0.1-0.3 V, starting with 0.1 V increments. See if things improve. If so, it may mean either the processor or motherboard is faulty.

It is not likely your display card would cause problems in Prime95, but a processor or motherboard fault could cause problems with the display card. The display card issue could be separate entirely, as well. We need to narrow down the Prime95 problem first.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top