Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD-after upgrade to Windows 7 from vista- help!


26 Oct 2010   #1

Windows 7 Home Premium 32bit
 
 
BSOD-after upgrade to Windows 7 from vista- help!

After I upgrade to Windows 7 from Vista, my computer keep crashing for almost every 1-2 hour. I suspect is the display driver crash with Windows 7.

I tried to download the latest driver but the problem remain. I am thinking to fall-back to Window Vista cause the problem really driving me crazy. Please help. Thanks.

Display adapters:
V 8.640.4.0
(ATI Mobility Radeo HD 4670
Mobile Intel 4 Series Express Chipset Family)



Windows 7 . . .
- x86 (32-bit) or x64 ? 32bit
- the original installed OS on the system? vista
- an OEM or full retail version? full Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 1 year
- What is the age of OS installation (have you re-installed the OS?) New install <1month

My System SpecsSystem Spec
.

26 Oct 2010   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2[2].zip\Windows_NT6_BSOD_jcgriff2\102610-27144-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
 
 
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8300d000 PsLoadedModuleList = 0x83155810
Debug session time: Tue Oct 26 10:52:40.047 2010 (GMT-4)
System Uptime: 0 days 0:05:31.592
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : atipmdag.sys ( atipmdag+2bc199 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x7f_0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 946f8199 to 830512ab
STACK_TEXT:  
8f2836cc 946f8199 badb0d00 00000000 8f2836f8 nt!KiTrap00+0x8b
WARNING: Stack unwind information not available. Following frames may be wrong.
8f28373c 8f2837c4 8f2837ac 946f7645 8f28375c atipmdag+0x2bc199
8f283744 946f7645 8f28375c 8f283808 88f9c810 0x8f2837c4
8f2837ac 945fc229 8f2837c4 00000027 88f9c810 atipmdag+0x2bb645
8f2837d4 945f86ac 88f9c810 8f283808 88f9459c atipmdag+0x1c0229
8f2837ec 9443f7e6 88f9c810 8f283808 8f283818 atipmdag+0x1bc6ac
8f2837fc 9445d554 8f283808 00000010 0000003f atipmdag+0x37e6
8f283818 946ca56b 85945000 8f28382c 8a137fb8 atipmdag+0x21554
8f28386c 946d5f07 8a136f2c 0000003f 8f283880 atipmdag+0x28e56b
8f28388c 946eaeef 88f9459c 000107ac 00013880 atipmdag+0x299f07
8f2838b4 946d9962 88f9459c 8a137fb8 8f2838e8 atipmdag+0x2aeeef
8f2838c4 946d4c58 88f9459c 8f283924 00000000 atipmdag+0x29d962
8f2838e8 946d4e0d 88f9459c 8f283924 00000000 atipmdag+0x298c58
8f28390c 946ce762 88f9459c 88f94674 8f283924 atipmdag+0x298e0d
8f28392c 946f35bd 88f9459c 88f94548 8a137fb8 atipmdag+0x292762
8f283950 946f38d0 8a1ae44c 8f283990 8f28399b atipmdag+0x2b75bd
8f28399c 946f16fe 8a1ae44c 94796108 8f2839c8 atipmdag+0x2b78d0
8f2839ac 946d21ee 8a12d97c 8f283a18 00000012 atipmdag+0x2b56fe
8f2839c8 946c8eed 8a12d97c 947934fc 8f283a18 atipmdag+0x2961ee
8f2839dc 946c8f29 8a12d97c 00000012 8f283a18 atipmdag+0x28ceed
8f2839f8 946c54a2 8a12d97c 00000012 8f283a18 atipmdag+0x28cf29
8f283a78 946c64f1 8f283a90 8f283af8 00000000 atipmdag+0x2894a2
8f283aa8 9446c5ef 8a136f28 8f283ae8 8f283af8 atipmdag+0x28a4f1
8f283acc 9446d040 8f283ae8 0000001c 00000000 atipmdag+0x305ef
8f283b08 9446d138 00000009 00000001 00000000 atipmdag+0x31040
8f283b28 9444a2cb 00000005 876548c0 8763ca00 atipmdag+0x31138
8f283b48 9444e4c9 00000000 8763ca00 8f283b70 atipmdag+0xe2cb
8f283b58 9444b371 8763ca00 8763ca00 c0000001 atipmdag+0x124c9
8f283b70 90390232 00000000 8a165000 8a165000 atipmdag+0xf371
8f283b84 990c12ae 8763ca00 85a61008 8a165000 atikmpag+0x4232
8f283ba8 990c2682 8a215008 85a61008 00000000 dxgkrnl+0x852ae
8f283bd0 990c9991 85a61008 85a61008 9018b07e dxgkrnl+0x86682
8f283bec 990f992c 00000000 00000000 8f283cb0 dxgkrnl+0x8d991
8f283c64 99120cd9 fffffcfb 00004fe4 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8f283c90 99100993 8a215008 8f283cb0 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
8f283d28 991254b7 00000000 830493f1 8a215008 dxgmms1!VidSchiScheduleCommandToRun+0x14d
8f283d3c 99125573 8a215008 00000000 895d8710 dxgmms1!VidSchiRun_PriorityTable+0xf
8f283d50 8321b6d3 8a215008 abdd1925 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8f283d90 830cd0f9 991254f4 8a215008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
atipmdag+2bc199
946f8199 ??              ???
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  atipmdag+2bc199
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME:  atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5f8c9b
FAILURE_BUCKET_ID:  0x7f_0_atipmdag+2bc199
BUCKET_ID:  0x7f_0_atipmdag+2bc199
Followup: MachineOwner
---------
This dirver is causing a conflict. Update or replace
Atipmdag.sys file description
Productname: ATI Radeon Family
Description: ATI Radeon Kernel Mode Driver
Company: ATI Technologies Inc.


A scond pontial cause
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads



How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
My System SpecsSystem Spec
26 Oct 2010   #3

Windows 8.1 Pro x64
 
 

All BSODs were caused by your display driver

Possible causes:bad RAM/PSU, incorrect RAM timings/voltages, bad Graphics card, overheating, outdated driver

Uninstall the ATI driver then use driver sweeper to remove leftover ATI files
Guru3D - Driver Sweeper

Then reinstall your driver: ATI Radeon

This was likely caused by the following module: atipmdag.sys
Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
My System SpecsSystem Spec
.


Reply

 BSOD-after upgrade to Windows 7 from vista- help!




Thread Tools



Similar help and support threads for2: BSOD-after upgrade to Windows 7 from vista- help!
Thread Forum
Help with windows 7 upgrade from Vista. General Discussion
Vista OEM upgrade to Windows 7 General Discussion
Windows Vista upgrade to Windows 7 Pro - BSOD (Sort of) BSOD Help and Support
BSOD System_Service_Exception After Upgrade from Vista Installation & Setup
Vista Ult 32 to Win 7 Ult 32 bit Upgrade - BSOD Installation & Setup
Could I upgrade from Vista 32-bit to Windows 7 64-bit? Installation & Setup
is it better to just upgrade from Vista to Windows 7? Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:20 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33