Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

Homebuilt PC BSOD's

This is a discussion on Homebuilt PC BSOD's within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Hello all, I recently built a PC with the help of a friend and have been having serious BSOD problems.


Closed Thread
 
Thread Tools Search this Thread
Old 05-04-2012, 10:30 AM   #1
Registered Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 16
OS: Windows 7 Ultimate 64 bit



Hello all,

I recently built a PC with the help of a friend and have been having serious BSOD problems. I have attempted to fix the problems myself but have been having no luck for as soon as i correct one problem another appears.

My BSOD's happen quite quickly when i start windows normally, not even executing any programs or operations. The computer starts and runs pretty well in safe mode and safe mode with networking. The biggest change that I have made so far was based off the advice of another forum where i disabled the gdrv.sys file that I thought was giving me problems. I have attached my minidump files any help would be greatly appreciated because I am looking at a 1200 paperweight right now...

Thanks!
Attached Files
File Type: zip Minidump - Copy.zip (607.0 KB, 39 views)
SWayland is offline  
Sponsored Links
Advertisement
 
Old 05-04-2012, 12:50 PM   #2
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,338
OS: Windows 10, 8.1 + Windbg :)



Hi -

Good call on gdrv.sys - Driver Verifier flagged it.

System uptimes show BSODs occurring ~2 min - 2 days after boot -

Code:
System Uptime: 0 days 0:03:30.802
System Uptime: 0 days 0:04:53.094
System Uptime: 0 days 0:19:07.923
System Uptime: 0 days 0:17:56.525
System Uptime: 0 days 0:03:57.622
System Uptime: 0 days 0:04:04.817
System Uptime: 0 days 0:07:17.097
System Uptime: 0 days 0:02:38.612
System Uptime: 0 days 0:02:48.854
System Uptime: 0 days 0:02:50.297
System Uptime: 0 days 0:02:43.363
System Uptime: 0 days 0:02:25.558
System Uptime: 0 days 0:02:51.289
System Uptime: 0 days 0:03:09.776
System Uptime: 0 days 0:03:13.804
System Uptime: 0 days 0:03:39.191
System Uptime: 0 days 0:02:55.493
System Uptime: 0 days 0:04:38.299
System Uptime: 0 days 0:05:43.754
System Uptime: 0 days 0:18:11.109
System Uptime: 0 days 0:29:03.318
System Uptime: 0 days 0:06:43.986
System Uptime: 0 days 1:35:30.008
System Uptime: 0 days 1:56:53.574
System Uptime: 0 days 0:31:16.327
System Uptime: 0 days 0:08:09.472
System Uptime: 0 days 0:17:56.184
System Uptime: 0 days 1:07:37.499
Remove Norton - it is definitely not helping you here.

Use removal tool - Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Reboot upon completion. Install Microsoft Security Essentials (MSE)


Please provide a link to the thread at other forum.

Try and run jcgriff2 BSOD app - https://www.techsupportforum.com/f217...ns-452654.html

Re-seat RAM. Check all hardware connections.

Lack of Windows 7 SP1 is a problem here too.

The dumps indicate RAM or HDD problems, but mobo/other can be the cause as well. The dumps are incapable of telling us.

Do you have an SSD or HDD?

Regards. . .

jcgriff2


`


BSOD SUMMARY
Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-39671-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 21:58:35.912 2012 (GMT-4)
System Uptime: 0 days 0:03:30.802
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1b71240 fffff900`c1b71290 00000000`25050001
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309

ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-39312-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 20:47:18.204 2012 (GMT-4)
System Uptime: 0 days 0:04:53.094
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1bab240 fffff900`c1bab290 00000000`25050001
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-41262-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 20:41:52.033 2012 (GMT-4)
System Uptime: 0 days 0:19:07.923
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1b5e240 fffff900`c1b5e290 00000000`25050001
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-92539-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 17:50:16.198 2012 (GMT-4)
System Uptime: 0 days 0:17:56.525
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9dbbd50f b3b7465e`f038a775 fffff800`030130a9 00000000`00000001
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-34351-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 17:01:32.106 2012 (GMT-4)
System Uptime: 0 days 0:03:57.622
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1bae240 fffff900`c1bae290 00000000`25050001
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-35303-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 01:12:22.490 2012 (GMT-4)
System Uptime: 0 days 0:04:04.817
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`9916191e b3b7465e`eb92eb84 fffff800`02c10bdf 00000000`00000001
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-111213-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 01:03:59.882 2012 (GMT-4)
System Uptime: 0 days 0:07:17.097
BugCheck D6, {fffff900c8009620, 1, fffff96000092394, 0}
Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD6
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xD6_VRF_win32k!sfac_GetLongGlyphIDs+84
Bugcheck code 000000D6
Arguments fffff900`c8009620 00000000`00000001 fffff960`00092394 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-32198-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 00:40:05.285 2012 (GMT-4)
System Uptime: 0 days 0:02:38.612
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`08852060 fffff880`0a43c809
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-34304-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 00:23:40.918 2012 (GMT-4)
System Uptime: 0 days 0:02:48.854
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`0a9f0b30 fffff880`0a8e2809
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-103335-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 00:19:24.344 2012 (GMT-4)
System Uptime: 0 days 0:02:50.297
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`0a0a53a0 fffff880`08fac809
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-100839-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 00:15:55.426 2012 (GMT-4)
System Uptime: 0 days 0:02:43.363
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`0acee750 fffff880`09001809
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-32261-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed May  2 00:06:06.231 2012 (GMT-4)
System Uptime: 0 days 0:02:25.558
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`0ad7e340 fffff880`094e0809
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042912-100589-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 29 20:38:23.352 2012 (GMT-4)
System Uptime: 0 days 0:02:51.289
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`09eab060 fffff880`09355809
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042912-101197-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 29 20:34:26.855 2012 (GMT-4)
System Uptime: 0 days 0:03:09.776
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  GUI.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000011c fffffa80`0ad7db30 fffff880`092e6809
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042912-99981-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 29 20:30:39.493 2012 (GMT-4)
System Uptime: 0 days 0:03:13.804
Probably caused by : ntkrnlmp.exe ( nt!IoIsOperationSynchronous+b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!IoIsOperationSynchronous+b
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ce76eb 00000000`00000000 ffffffff`ffffffff
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042912-31605-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 29 20:00:37.864 2012 (GMT-4)
System Uptime: 0 days 0:03:39.191
Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  LMS.exe
FAILURE_BUCKET_ID:  X64_0x50_VRF_NETIO!NsiEnumerateObjectsAllParametersEx+24f
Bugcheck code 00000050
Arguments fffff87f`ff606440 00000000`00000008 fffff87f`ff606440 00000000`00000005
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042912-28438-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 29 19:41:36.572 2012 (GMT-4)
System Uptime: 0 days 0:02:55.493
Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LMS.exe
FAILURE_BUCKET_ID:  X64_0x50_NETIO!NsiEnumerateObjectsAllParametersEx+24f
Bugcheck code 00000050
Arguments fffff87f`ff608440 00000000`00000008 fffff87f`ff608440 00000000`00000005
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-44897-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 21:16:41.988 2012 (GMT-4)
System Uptime: 0 days 0:04:38.299
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1a745d0 fffff900`c1a74620 00000000`25050029
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
MaxSpeed:     3300
CurrentSpeed: 3309
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-45661-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 21:09:04.832 2012 (GMT-4)
System Uptime: 0 days 0:05:43.754
Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!sfac_GetLongGlyphIDs+84
Bugcheck code 00000050
Arguments fffff900`c21e7000 00000000`00000001 fffff960`00102394 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-49077-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 21:02:44.798 2012 (GMT-4)
System Uptime: 0 days 0:18:11.109
Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!sfac_GetLongGlyphIDs+84
Bugcheck code 00000050
Arguments fffff900`c2151000 00000000`00000001 fffff960`00052394 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-43368-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 18:25:57.007 2012 (GMT-4)
System Uptime: 0 days 0:29:03.318
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000109
Arguments a3a039d8`9fc1583c b3b7465e`f23f26f6 fffff800`02e05510 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-45146-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 17:55:57.065 2012 (GMT-4)
System Uptime: 0 days 0:06:43.986
Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!sfac_GetLongGlyphIDs+84
Bugcheck code 00000050
Arguments fffff900`c1a06000 00000000`00000001 fffff960`00022394 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-45708-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 17:48:44.086 2012 (GMT-4)
System Uptime: 0 days 1:35:30.008
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c1a249e0 fffff900`c1a24a30 00000000`2505009e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-54413-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 16:12:16.652 2012 (GMT-4)
System Uptime: 0 days 1:56:53.574
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000109
Arguments a3a039d8`9a43352c b3b7465e`ecc103e6 fffff800`02e1f510 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-58921-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 14:14:25.406 2012 (GMT-4)
System Uptime: 0 days 0:31:16.327
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`99b5d90a b3b7465e`ec340140 fffff880`00d35470 00000000`00000001
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042712-43571-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Apr 27 13:13:18.160 2012 (GMT-4)
System Uptime: 0 days 0:08:09.472
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0b640508 fffff880`0b63fd70 fffff880`012653a8
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042612-47814-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr 26 21:31:34.872 2012 (GMT-4)
System Uptime: 0 days 0:17:56.184
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`99ae6632 b3b7465e`ec2b3860 fffff800`030130f0 00000000`00000001
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\042612-22526-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr 26 19:56:11.188 2012 (GMT-4)
System Uptime: 0 days 1:07:37.499
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0317dea8 fffff880`0317d700 fffff880`012553a8
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  

	    
             
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           https://mvp.support.microsoft.com/profile/Griffith   

           www.sysnative.com
             
           www.jcgriff2.com 


ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии


  
jcgriff2 is offline  
Old 05-06-2012, 07:30 PM   #3
Registered Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 16
OS: Windows 7 Ultimate 64 bit



jcgriff,

Thanks I am currently in the process of working through the steps you described. I ended up restoring my system to an earlier time frame through the repair windows option on startup. I will let you know of any progress I make.

I am currently using a 1TB Western Digital HDD.

Thanks
SWayland is offline  
Sponsored Links
Advertisement
 
Old 05-08-2012, 07:40 AM   #4
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,338
OS: Windows 10, 8.1 + Windbg :)



OK... please let us know how it goes.
jcgriff2 is offline  
Old 05-13-2012, 08:43 PM   #5
Registered Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 16
OS: Windows 7 Ultimate 64 bit



Jcgriff,

Sorry I took so long getting back to you. I have been caught up with classes and other various items., I ended up reinstalling Windows 7 out of sheer frustration. I am still getting BSOD's but I believe I have a much more stable environment now.

I uploaded the BSOD report files as you requested, hopefully this will be able to help out. The primary error i am receiving now is the 0x00000109 error. I have tried to update my computer to SP1 per your recommendations, however the installation always fails. This is followed by a bluescreen with the aforementioned error code.

Again thank you so much! Also I noticed your Drexel logo, what is your affiliation with the university? I am currently an undergrad student.


OS: Windows 7
64 Bit
No original installed OS
Full retail version installed by user
All brand new hardware
Age of OS installation (<1 week)

Intel Core i5 2500k CPU @ 3.30 GHz
AMD Radeon HD6800 Series
Gigabyte Z68X-UD3H-B3 Motherboard
ANTEC Earthwatts 500w Power supply
Attached Files
File Type: zip BSOD_Windows7_Vista_v2.64_jcgriff2_.zip (80.2 KB, 45 views)
SWayland is offline  
Old 05-14-2012, 11:19 PM   #6
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,338
OS: Windows 10, 8.1 + Windbg :)



Hi -

Bugcheck 0x109 = kernel corruption

Either a rogue driver attempted to patch the kernel (only Windows Updates can patch) or hardware failure caused the corruption, e.g., RAM failed and couldn't properly hold kernel code.

Given the fresh OS install, I have a feeling the 0x109 dumps will probably look like prior-OS 0x109 dumps -
Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050312-92539-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu May  3 17:50:16.198 2012 (GMT-4)
System Uptime: 0 days 0:17:56.525
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`9dbbd50f b3b7465e`f038a775 fffff800`030130a9 00000000`00000001
We never should see "Unknown Image". Windows 7 x64 systems mandate driver signing, so the chances of this being software related are near zero.

I'll be glad to take a look at the dumps; however, the zip file contained the executable + HTML file. I need the output from the exe -
Quote:
╖ Output = new folder Windows7_Vista_jcgriff2 in Documents
Re-run if you need to - https://www.techsupportforum.com/foru...ta-452654.html

Skip #3.

You should check hardware out, starting w/ RAM. Re-seat, run memtest 86+ one stick at a time; alternate the slots.

https://www.techsupportforum.com/2863029-post5.html

I majored in Accounting & Finance at Drexel; graduated around the time your (very young) parents did! 4 kids here - 22,18,13,11

Regards. . .

John
jcgriff2 is offline  
Old 05-15-2012, 08:28 AM   #7
Registered Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 16
OS: Windows 7 Ultimate 64 bit



John,

I do remember there being an error with the wilan card driver being unsigned. Windows flagged it, but the install manual said that would happen and to continue on. do you think that this is causing the error? I even went to the card's website and downloaded the most up to date driver for the card. I will re run the BSOD app and test the ram as well.

Thanks so much

-Steve
SWayland is offline  
Old 05-15-2012, 08:33 AM   #8
Enthusiast
 
Join Date: Apr 2007
Posts: 16,762
OS: Windows 7

My System


you are also on your limit of power required just for the graphics card. Your card requires 500w whilst the rest of your system also requires power too.

Generally when you see a psu recommendation for a gpu you should add 30% to that figure. I would be running a 650w good make of power supply with your setup.
__________________
Microsoft Certified Professional
compTIA Certified Professional
greenbrucelee is offline  
Old 05-15-2012, 09:26 AM   #9
Registered Member
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 16
OS: Windows 7 Ultimate 64 bit



I have been reading almost the opposite of what you just said. A lot of what ive read has said average power drawn for most systems average 130 - 350 W, where as overclocking systems can draw up to 460 W. Im not sure if the take account the GPU and its power requirements. I havent been over clocking on this PC (dont really plan to either) and I have been barely running any processor/ GPU intensive processes. Do you still think the power supply is a problem?

Quote:
Originally Posted by greenbrucelee View Post
you are also on your limit of power required just for the graphics card. Your card requires 500w whilst the rest of your system also requires power too.

Generally when you see a psu recommendation for a gpu you should add 30% to that figure. I would be running a 650w good make of power supply with your setup.
SWayland is offline  
Old 05-15-2012, 01:47 PM   #10
Enthusiast
 
Join Date: Apr 2007
Posts: 16,762
OS: Windows 7

My System


Quote:
Originally Posted by SWayland View Post
I have been reading almost the opposite of what you just said. A lot of what ive read has said average power drawn for most systems average 130 - 350 W, where as overclocking systems can draw up to 460 W. Im not sure if the take account the GPU and its power requirements. I havent been over clocking on this PC (dont really plan to either) and I have been barely running any processor/ GPU intensive processes. Do you still think the power supply is a problem?
go into your BIOS (if you can) and check the voltages for the 12v the 3.3v and the 5v reading.

Your card needs 500w ATI do not lie about this, alot of what you read from people who dont really know about this is about what happens when the card uses power what they don't know about is how electricity fluctuates and ripples. I used to work in the power supply testing industry and when it says this card needs 500w that is the most the card can pull, this does not take into account that you may have an ipod plugged in and an external hard drive and an internal card such as a network interface card or indeed that you may be burning CDs whilst playing a game.

For all these reasons (and more) it is wise to add 30% to what is stated for the card. It is also wise to invest in a good make of power supply which Antec used to be and there high end range is getting back to good quality but the earthwats are not their high end range.

Antec used to get their power supplies made by seasonic up untill about 7 years ago. They decided in order to save themselves money that they would stop getting seasonic to make their power supplies because of the gold capacitors seasonic use and they started gettinmg low end manufacturers to create their power supplies such as sirtec and other bog standard manufacturers.

The psu is the most important part of your system, I would not be suprised if it is contributing to the problem.

If you are overclocking, scale back your overclock and see if the problem goes away. If it does then you know it is either power or heat.

Also download OCCT and run the psu test for 1 hour. If the psu test stops before 1 hour is up then your psu is the issue and the graphs will show this.
__________________
Microsoft Certified Professional
compTIA Certified Professional
greenbrucelee is offline  
Old 05-15-2012, 09:30 PM   #11
TSF Enthusiast
 
Join Date: May 2012
Location: Australia
Posts: 513
OS: Windows 7 32bit SP1



When the manufacture states that a GPU require a 400 watts PSU, they are referring to the idle mode of that GPU or when using simple programs like spider solitaire...

Some GPU's can require as much as 165 watts (or more) when used for programming and extreme gaming. The CPu may use about 36 watts, the CD/DVD drive uses about 35watts, external devices also require power as does ram (about 40 watts), the motherboard for transferring data bewteen components so add another 75 to 125 watts. Other addons like internal fans, CPU fan etc also require power so I'd say that for your rig, I wouldn't go below 700 watts (36 amps).

My rule of thumb is to add up all the watts and then add 200 watts to that figure.

However, the Question is more about the BSOD which a low PSU doesn't really do, the PC will just shut down or other components will not have power to work like cd/dvd drive.

The main problem with BSOD is that 64 bit opewrating systems do not like 32 bit games or programs, especially those programs or games that require Directx 9C compatible GPU.
Jupiter2 is offline  
Old 05-16-2012, 04:26 AM   #12
Enthusiast
 
Join Date: Apr 2007
Posts: 16,762
OS: Windows 7

My System


A low quality power supply can cause all sorts of issues. I have seen them produce kernel BSODs and other blue screens.

Any modern pcie system should be running atleast a 550w these days anyway then you add 30% and you should be fine.

Anyway as said a 64 bit OS will not like something purely made for 32bit
__________________
Microsoft Certified Professional
compTIA Certified Professional
greenbrucelee is offline  
Old 05-16-2012, 07:41 AM   #13
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,338
OS: Windows 10, 8.1 + Windbg :)



Quote:
Originally Posted by SWayland View Post
John,

I do remember there being an error with the wilan card driver being unsigned. Windows flagged it, but the install manual said that would happen and to continue on. do you think that this is causing the error? I even went to the card's website and downloaded the most up to date driver for the card. I will re run the BSOD app and test the ram as well.

Thanks so much

-Steve
Hi Steve. . .

The wifi driver could be a problem - written by Atheros -
Code:
athrx.sys Wed Jan 27 20:25:39 2010 (4B60E793)
http://www.sysnative.com/drivers/driver.php?id=athrx.sys

You'll have a hard time finding an update. Unplug it & run Ethernet.

Norton or lack of W7 SP1 may have contributed to some BSODs.

Please run the jcgriff2 BSOD app - takes a few minutes.

Are you overclocked? PERFMON reporting -
Code:
 
Intel(R) Core(TM) i5-2500K CPU @ 3.30 GHz
 
CurrentClockSpeed               3601 
Reset to default if o/c.
Quote:
Originally Posted by Jupiter2 View Post
The main problem with BSOD is that 64 bit opewrating systems do not like 32 bit games or programs, especially those programs or games that require Directx 9C compatible GPU.
No gamer here, but my kids are. ALL OS here are x64. Most apps and games are x86 and run fine. There really are few pure x64 apps comared to x86. GPU compatibility can be an issue. PERFMON -
Quote:
The "Gaming graphics" rating for the system is poor and may be the cause of performance problems in multimedia applications or games. Disabling Aero Glass may improve performance in multimedia applications or games. If the problem continues the display adapter may need an updated driver or may need to be upgraded.

The "Graphics" rating for the system is poor and may be the cause of performance problems. Disabling Desktop Composition or reducing screen resolution may improve graphical performance. If the problem continues the display adapter may need an updated driver or may need to be upgraded.
Not sure why those messages appear.
Quote:
Originally Posted by greenbrucelee View Post
A low quality power supply can cause all sorts of issues. I have seen them produce kernel BSODs and other blue screens.
Quote:
Originally Posted by Jupiter2 View Post
However, the Question is more about the BSOD which a low PSU doesn't really do, the PC will just shut down or other components will not have power to work like cd/dvd drive.
greenbrucelee is right here. Inadequate PSU can absolutely cause BSODs.

The definition of 0x109 = kernel corruption, which can be caused by a rogue driver or hardware failure - like RAM or other hardware failure affecting RAMs ability to properly hold kernel code. PSU would be on this list.

Your BSODs are very likely hardware related as many were VERIFIER_ENABLED, yet no 3rd party driver named. Also numerous bugchecks (STOP errors) found.

A low quality PSU can lead to OS instability and BSODs, not necessarily a power failure type shutdown.

Swap out the PSU for one recommended by greenbrucelee and see if BSODs persist.

Regards. . .

jcgriff2

`
jcgriff2 is offline  
Old 05-16-2012, 08:07 AM   #14
Moderator
- Microsoft Support
BSOD Kernel Dump Analyst
 
satrow's Avatar
 
Join Date: Feb 2012
Location: Wales U.K.
Posts: 5,682
OS: W7 SP1 Pro x64

My System


One additional point about poor/failing PSU's: they can, and sometimes do, cause data loss and hard drive failure before becoming a frequent BSOD trigger - on that point alone, if someone suggests the PSU needs updgrading, seriously consider that as being good, solid advice - data loss/recovery is no laughing matter.
__________________
satrow is online now  
Old 05-16-2012, 10:21 AM   #15
TSF Enthusiast
 
Join Date: May 2012
Location: Australia
Posts: 513
OS: Windows 7 32bit SP1


Red Faced

On my Vista 32 bit PC, I tried to load an old 32 bit game that caused the BSOD. I did a repair but to no avail, I tried to do another repair and saw an option for Directx Repair to which I did and the problem was solved. I think the game had overwritten some instruction of Directx or something but either way, it was a Directx problem that caused the BSOD.

Your kids mostly play old 32 bit games (Directx 8.1 or 9) so try the repair option and see if the Directx option is available in the Repair dialog (if the problem occurs again).

Also, you may want to set up Guest accounts for your kids rather than letting them download and install games without your consent or supervision.

Reason for Edit - Typos...
Jupiter2 is offline  
Old 05-16-2012, 10:26 AM   #16
TSF Enthusiast
 
Join Date: May 2012
Location: Australia
Posts: 513
OS: Windows 7 32bit SP1



About the PSU, I was referring to a lower wattage rather than a failing PSU which can cause problems. Using a PSU that does not have sufficient power for all components can cause addon devices not to operate.
Jupiter2 is offline  
Old 05-16-2012, 12:30 PM   #17
Enthusiast
 
Join Date: Apr 2007
Posts: 16,762
OS: Windows 7

My System


Quote:
Originally Posted by Jupiter2 View Post
About the PSU, I was referring to a lower wattage rather than a failing PSU which can cause problems. Using a PSU that does not have sufficient power for all components can cause addon devices not to operate.
yes you are correct but with lower tier power supplies when they do not have enough power to power everything they tend to spike and this causes death to other components usually it's RAM or some other smaller component like a NIC but I have seen them spike hard drives and in the case of Huntkey power supplies they spike themselves which causes them to explode and most of the time it destroys everything.

If I can find it and compress it I actually have a video of huntkey spiking and ripping a motherboard in two as it catches fire and expands.
__________________
Microsoft Certified Professional
compTIA Certified Professional
greenbrucelee is offline  
Old 05-16-2012, 12:49 PM   #18
TSF Enthusiast
 
Join Date: May 2012
Location: Australia
Posts: 513
OS: Windows 7 32bit SP1



Quote:
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
You have a utility to Free Ram memory and, as such, is a 32 bit program trying to access ram modules far greater than it could ever access and could the problem.

If you can get into Control Panel through Safe Mode, I suggest uninstalling all those add on programs like FreeMem (and programs that were created pre 2005 era)
Jupiter2 is offline  
Old 05-16-2012, 12:56 PM   #19
TSF Enthusiast
 
Join Date: May 2012
Location: Australia
Posts: 513
OS: Windows 7 32bit SP1



Quote:
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
It seems that your OS is a beta version of Windows 7 sp1 rather than an offical full version.

"the leaked beta-build with string - "6.1.7601.16537.amd64fre.win7.100327-0053" is not intended for use on production computers and users are advised to download it from the official source only"
Jupiter2 is offline  
Old 05-16-2012, 01:10 PM   #20
Administrator
Team Manager, Gaming
Team Manager, Microsoft Support
Team Manager, Hardware Team
Microsoft MVP
 
Wrench97's Avatar

Microsoft Most Valuable Professional
 
Join Date: May 2008
Location: S.E. Pennsylvania
Posts: 54,007
OS: Win7



Quote:
Originally Posted by Jupiter2 View Post
It seems that your OS is a beta version of Windows 7 sp1 rather than an offical full version.

"the leaked beta-build with string - "6.1.7601.16537.amd64fre.win7.100327-0053" is not intended for use on production computers and users are advised to download it from the official source only"
His code string as you quoted and as listed is

7600.16841.amd64fre.win7_gdr.110622-1503
Not
6.1.7601.16537.amd64fre.win7.100327-0053

He's running Win7 RTM not Win7 SP1
Wrench97 is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
over a year of BSODs later, I'm at my wit's end
╖ Windows 7 professional sp 1 ╖ 64bit ╖ custom built this around Dec/Jan of 2009 ╖ reinstalled the OS about a two months or so ago (didn't fix BSODs obviously) ╖ CPU: AMD Phenom II X4 965 3.4Ghz ╖ Video Card: HIS Radeon HD 5750 ╖ MoBo: GIGABYTE GA-790FXTA-UD5 ╖ PSU: Rosewill Xtreme Series...
Lemcott BSOD, App Crashes And Hangs 43 09-06-2012 02:17 PM
[SOLVED] HP a6200n random BSODs
I'm working on a HP Pavilion a6200n w/Vista 32bit machine that has had random BSODs for a few months now according to the owner. Since all the BSODs I've tested memory with memtest86, memtest86+, and HP hard drive/memory diagnostics with no errors. Made sure all drivers were updated. Updated system...
Rampart BSOD, App Crashes And Hangs 3 09-01-2011 02:57 AM
BSoD's and now computer fails to start
Hello, I was getting random BSoD's after installing a new graphics card (went from a XFX HD 5870 to XFX HD 6870 Black Edition). Ever since, I have had random BSoD's that started off being once every few days, to almost always within a couple hours of booting. I installed the card correctly, and...
EvoSpyder BSOD, App Crashes And Hangs 2 07-23-2011 07:17 AM
Incessant BSOD's
OS: Windows 7 Professional (64-bit) Original OS: Same OS version: Retail (from MSDNAA) Age of hardware: 1.5 years Age of OS: Formatted approximately ten days ago CPU: AMD Phenom II X4 925 (C2 step.) OC'd to 3.5 GHz (24 hours stable) GPU: Galaxy GTS 250 512 MB Motherboard: ASRock M3A770DE...
Dbzruler72 BSOD, App Crashes And Hangs 46 03-28-2011 08:54 AM
BSOD's Win7 ATI 5770
BSOD's have plagued my new computer build for almost a year now and I have not been able to find the culprit. BSOD's happen at any time, more frequent when playing graphically intensive games, however it also has occurred just while browsing at Firefox and the desktop. I am hoping to find some...
derektriley BSOD, App Crashes And Hangs 6 03-14-2011 04:38 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 04:57 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts