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: Windows 7 crash

05 Dec 2009   #1
green angel

Windows 7
 
 
Windows 7 crash

Hello
Some weeks time ago I have installed Windows 7 but it have Bluescreen when I'm away from the computer. About one day ago the computer has Bluescreen with more often but isn't a Bluescreen, screen goes black and audio output produces noise, and when windows start it says:

Quote:
Problem signature:
Event Name Problem: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Region ID: 2070

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA810429A900
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800237C081
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C: \ Windows \ Minidump \ 120509-24671-01.dmp
C: \ Users \ Paul \ AppData \ Local \ Temp \ WER-65078-0.sysdata.xml
For additional information stay here two files of minidump that occurred today:
Attachment 40571
Attachment 40572

I'm sorry for my bad english but I'm from a distant country where we speak another language... I hope you can understand my very bad english and help me.
Thanky you,


My System SpecsSystem Spec
.
05 Dec 2009   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by green angel View Post
Hello
Some weeks time ago I have installed Windows 7 but it have Bluescreen when I'm away from the computer. About one day ago the computer has Bluescreen with more often but isn't a Bluescreen, screen goes black and audio output produces noise, and when windows start it says:

Quote:
Problem signature:
Event Name Problem: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Region ID: 2070

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA810429A900
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800237C081
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C: \ Windows \ Minidump \ 120509-24671-01.dmp
C: \ Users \ Paul \ AppData \ Local \ Temp \ WER-65078-0.sysdata.xml
For additional information stay here two files of minidump that occurred today:
Attachment 40571
Attachment 40572

I'm sorry for my bad english but I'm from a distant country where we speak another language... I hope you can understand my very bad english and help me.
Thanky you,
Hi and welcome

Well I took a quick look at one of your dmp files. It was probably caused by the 2 and hlf year old usb driver listed below (underlined).

I would update the drivers listed at least
Run system file check to verity and fis you r system files. to do that you type cmd in search>right click run as admin> SFC /SCANOW

If you are over clocking stop.
Let us know if you need any help with this

Ken J+








secdrv.SYS fffff880`04711000 fffff880`0471c000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
gtptser.sys fffff880`06e24000 fffff880`06e26980 0x00002980 0x460cf6a6 3/30/2007 6:38:14 AM
viahduaa.sys fffff880`0488d000 fffff880`048d1000 0x00044000 0x466620dd 6/5/2007 9:50:05 PM
gt72ubus.sys gt72ubus.sys+c081 fffff880`06fdc000 fffff880`06ff4000 0x00018000 0x470b6bb9 10/9/2007 6:53:29 AM
Gt51Ip.sys fffff880`06e00000 fffff880`06e24000 0x00024000 0x4739b9df 11/13/2007 9:51:11 AM
gtscser.sys fffff880`06e27000 fffff880`06e2d780 0x00006780 0x4753e3ed 12/3/2007 6:09:33 AM
RTL8187.sys fffff880`04936000 fffff880`049a2000 0x0006c000 0x48644512 6/26/2008 8:40:34 PM
fet6x64v.sys fffff880`0424f000 fffff880`0425a900 0x0000b900 0x48d76568 9/22/2008 4:29:12 AM


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\120509-41046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16399.amd64fre.win7_gdr.090722-1835
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e3fe50
Debug session time: Sat Dec  5 08:27:22.370 2009 (GMT-5)
System Uptime: 0 days 1:46:54.698
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8103f81870, 2, 0, fffff88006fe8081}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\gt72ubus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gt72ubus.sys
*** ERROR: Module load completed but symbols could not be loaded for gt72ubus.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : gt72ubus.sys ( gt72ubus+c081 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Dec 2009   #3
green angel

Windows 7
 
 

Hi and thank you for helping me but the problem wasn't resolved.
I did what you said, I run system file and it is returned: "windows did not find any breach of integrity". The USB ports of my computer stopped working and I restarted the computer.
Until a few minutes ago, when I has some programs open and I was copy some files to my external disk the computer stopped working and, after a few seconds, the screen goes green and computer restarted. When computer start it says:

Quote:
Problem signature:
Event Name Problem: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Region ID: 2070

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF6800000C310
BCP3: B6C0000061BA2867
BCP4: 00FCFCFC00FCFCFC
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C: \ Windows \ Minidump \ 120609-28203-01.dmp
C: \ Users \ Paul \ AppData \ Local \ Temp \ WER-72015-0.sysdata.xm
Minidump:
Attachment 40737
My System SpecsSystem Spec
.

06 Dec 2009   #4
torrentg

7600.20510 x86
 
 

These drivers are still in need of updating:

Code:
gtscser  gtscser.sys  Mon Dec 03 06:09:33 2007
gtptser  gtptser.sys  Fri Mar 30 07:38:14 2007
gt72ubus gt72ubus.sys Tue Oct 09 07:53:29 2007
Gt51Ip   Gt51Ip.sys   Tue Nov 13 09:51:11 2007
RTL8187  RTL8187.sys  Thu Jun 26 21:40:34 2008
fet6x64v fet6x64v.sys Mon Sep 22 05:29:12 2008
viahduaa viahduaa.sys Tue Jun 05 22:50:05 2007
I can find you the latest Realtek and maybe other one if you tell me your motherboard model. Use the mainboard tab of CPU-Z to find out.
My System SpecsSystem Spec
07 Dec 2009   #5
green angel

Windows 7
 
 

Quote   Quote: Originally Posted by torrentg View Post
These drivers are still in need of updating:

Code:
gtscser  gtscser.sys  Mon Dec 03 06:09:33 2007
gtptser  gtptser.sys  Fri Mar 30 07:38:14 2007
gt72ubus gt72ubus.sys Tue Oct 09 07:53:29 2007
Gt51Ip   Gt51Ip.sys   Tue Nov 13 09:51:11 2007
RTL8187  RTL8187.sys  Thu Jun 26 21:40:34 2008
fet6x64v fet6x64v.sys Mon Sep 22 05:29:12 2008
viahduaa viahduaa.sys Tue Jun 05 22:50:05 2007
I can find you the latest Realtek and maybe other one if you tell me your motherboard model. Use the mainboard tab of CPU-Z to find out.


How can I find another drivers ?
My System SpecsSystem Spec
07 Dec 2009   #6
torrentg

7600.20510 x86
 
 

This is for the RTL8187 - Realtek

The others you'll have to Google to see what you can find.

Install for Win 7 for the link above now though.
My System SpecsSystem Spec
07 Dec 2009   #7
green angel

Windows 7
 
 

Quote   Quote: Originally Posted by torrentg View Post
This is for the RTL8187 - Realtek

The others you'll have to Google to see what you can find.

Install for Win 7 for the link above now though.
To install the new drives do I need to uninstall something first ?
My System SpecsSystem Spec
07 Dec 2009   #8
torrentg

7600.20510 x86
 
 

No. Just install new ones. No need to worry about removing anything.
My System SpecsSystem Spec
Reply

 Windows 7 crash




Thread Tools




Similar help and support threads
Thread Forum
Black screen crash; DSL modem crash
Hello, This morning (11.26.14, 8:50ish) I had nothing running more than usual (chrome, onenote, word) on my desktop. I was in my other room turning on my laptop but it would not find my wireless network. I went to my desktop and found that the monitor turned itself off (that's normal) but moving...
BSOD Help and Support
Startup very slow,crash at welcome and crash randomlythen OS not found
A few weeks back PC crashed out of no where and BSOD appeared.. didnt take much notice until it says OS not found when restarting.. but after a few tries it went back to normal for a few days then these few days it started to startup very slowly and may sometimes crash after typing in the password...
BSOD Help and Support
Recent PC Build. CRASH...CRASH...CRASH
Okay guys, I'd love some help with some issues I am having. About two months ago I decided to start putting together parts to build my own rig(first time builder here) After scrounging around for a bit and getting the deals I liked I decided to put it all together and make my PC. Since then, Ive...
BSOD Help and Support
Crash on new PC Full Crash log zipped and included. Driver related?
So my new Cyberpower PC is crashing. I think it is a driver issue but this level of detail is beyond by "expertise" basic log below. Full diagnostic attached. Please let me know if additional information is needed. Problem signature: Problem Event Name: BlueScreen OS...
BSOD Help and Support
Windows Audio/Windows End Point Services crash
I have a very strange problem; hope someone has the answer to this one. On my new Windows 7 CPU a little red x appears next the the speaker icon every time I closed down certain programs. The programs I use that cause this to happen are Publisher 2003, FrontPage 2003 (yes, I still use that for...
Sound & Audio
Laptop crash no response memory dump crash
My laptop, Packard Bell Easynote TM81, has been crashing and restarting by itself, and when it does, the ENTIRE system will not respond. So I try to format the entire thing, and after a few days, when I have gotten used to it, it comes up with a screen for 1 second, and all I could read was "system...
BSOD Help and Support


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 21:37.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App