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 10 minutes in playing Empire: TW


31 Mar 2012   #1
Twistedben

Windows 7 Home Premium 64-bit
 
 
BSOD 10 minutes in playing Empire: TW

Hello everyone. Thanks for reading in advance.

I've been having a BSOD when playing Empire: Total War on my new desktop. It has happened 2 out of 2 times now when 3 weeks ago it was fine, and had no BSODs. My BSODs only happen when playing this game--I haven't attempted to play Skyrim yet--though Skyrim played fine 3 weeks ago. I haven't yet updated to the latest Nvidia driver, and I recently installed an SSD (the games worked with the SSD until the last few days, so I don't think it's related to the SSD installation). Other than that, nothing has changed.

Through "Reliability History" in windows; my first BSOD:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032912-12994-01.
I couldn't get the dmp file in time.

Through "Windows Has Recovered From An Unexpected Shutdown"; second BSOD:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Through "Windows Debugging"; Second BSOD:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
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

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3739316361303932
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff8000481f9c8 -- (.exr 0xfffff8000481f9c8)
ExceptionAddress: fffff80003283092 (nt!SwapContext_PatchXRstor)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff8000481fa70 -- (.trap 0xfffff8000481fa70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffff8000481fcc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003283092 rsp=fffff8000481fc00 rbp=fffff8000481fc70
r8=fffffa80068eb850 r9=0000000000000000 r10=0000000000000000
r11=fffff800033f4e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!SwapContext_PatchXRstor:
fffff800`03283092 0fae09 fxrstor [rcx] ds:9f60:fffff800`0481fcc0=7f
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032776fe to fffff8000327fd10

STACK_TEXT:
fffff800`0481eaa8 fffff800`032776fe : 00000000`00000020 fffffa80`069fe000 fffff800`0481f220 fffff800`032aada0 : nt!KeBugCheck
fffff800`0481eab0 fffff800`032aaa6d : fffff800`0348814c fffff800`033c8ee0 fffff800`03203000 fffff800`0481f9c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0481eae0 fffff800`032a9845 : fffff800`033c8fac fffff800`0481eb58 fffff800`0481f9c8 fffff800`03203000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0481eb10 fffff800`032ba7c1 : fffff800`0481f9c8 fffff800`0481f220 fffff800`00000000 fffffa80`0acf1b60 : nt!RtlDispatchException+0x415
fffff800`0481f1f0 fffff800`0327f3c2 : fffff800`0481f9c8 fffff800`033f4e80 fffff800`0481fa70 fffff800`03402cc0 : nt!KiDispatchException+0x135
fffff800`0481f890 fffff800`0327dcca : fffff800`033f4e80 fffff880`06cce28f fffff800`0381b460 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`0481fa70 fffff800`03283092 : fffff800`04819080 fffff800`032cac2c 00000000`00000002 fffff800`03277a42 : nt!KiGeneralProtectionFault+0x10a
fffff800`0481fc00 fffff800`03277b1d : fffff800`033f4e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!SwapContext_PatchXRstor
fffff800`0481fc40 00000000`00000000 : fffff800`04820000 fffff800`0481a000 fffff800`0481fc00 00000000`00000000 : nt!KiIdleLoop+0x10d


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`032776fe 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
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

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3739316361303932
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff8000481f9c8 -- (.exr 0xfffff8000481f9c8)
ExceptionAddress: fffff80003283092 (nt!SwapContext_PatchXRstor)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff8000481fa70 -- (.trap 0xfffff8000481fa70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffff8000481fcc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003283092 rsp=fffff8000481fc00 rbp=fffff8000481fc70
r8=fffffa80068eb850 r9=0000000000000000 r10=0000000000000000
r11=fffff800033f4e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!SwapContext_PatchXRstor:
fffff800`03283092 0fae09 fxrstor [rcx] ds:9f60:fffff800`0481fcc0=7f
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032776fe to fffff8000327fd10

STACK_TEXT:
fffff800`0481eaa8 fffff800`032776fe : 00000000`00000020 fffffa80`069fe000 fffff800`0481f220 fffff800`032aada0 : nt!KeBugCheck
fffff800`0481eab0 fffff800`032aaa6d : fffff800`0348814c fffff800`033c8ee0 fffff800`03203000 fffff800`0481f9c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0481eae0 fffff800`032a9845 : fffff800`033c8fac fffff800`0481eb58 fffff800`0481f9c8 fffff800`03203000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0481eb10 fffff800`032ba7c1 : fffff800`0481f9c8 fffff800`0481f220 fffff800`00000000 fffffa80`0acf1b60 : nt!RtlDispatchException+0x415
fffff800`0481f1f0 fffff800`0327f3c2 : fffff800`0481f9c8 fffff800`033f4e80 fffff800`0481fa70 fffff800`03402cc0 : nt!KiDispatchException+0x135
fffff800`0481f890 fffff800`0327dcca : fffff800`033f4e80 fffff880`06cce28f fffff800`0381b460 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`0481fa70 fffff800`03283092 : fffff800`04819080 fffff800`032cac2c 00000000`00000002 fffff800`03277a42 : nt!KiGeneralProtectionFault+0x10a
fffff800`0481fc00 fffff800`03277b1d : fffff800`033f4e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!SwapContext_PatchXRstor
fffff800`0481fc40 00000000`00000000 : fffff800`04820000 fffff800`0481a000 fffff800`0481fc00 00000000`00000000 : nt!KiIdleLoop+0x10d


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`032776fe 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner


If you can help, I really appreciate it. I'm going to update my GPU drivers right now. My system information is on my account profile, but here's a quick run down.

Win 7 HP 64bit
Asus ENGTX DCII 580
Corsair 850w Professional
OCZ Agility 3 120GB (C
2x 1 TB Caviar Blacks for storage
i7-2600k (OC'd to 4.2ghz)
2x G.Skill Sniper 4gb RAM (OC'd to 1833)
Asrock Fat1lity P67

Thanks for your time,
Twistedben


My System SpecsSystem Spec
31 Mar 2012   #2
zigzag3143

Win 8 Release candidate 8400
 
 



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:
Quote:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
23 Apr 2012   #3
Twistedben

Windows 7 Home Premium 64-bit
 
 

Sorry for the delayed reply.
I updated my Graphics Drivers and thought the BSODs went away with it, but I had one last night. For a while there, I could play Empire with no BSODs and run the computer fine. It had been about 3 weeks since I had one. I attached the MiniDump file in my attachments, using WinRar.

Says: Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e
But I have the detailed report in the attachment.

Thank you for looking in advance,
Twistedben
My System SpecsSystem Spec
24 Apr 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Possible out of date drivers:
Code:
FNETURPX	fffff880`014d4000	fffff880`014dd000	Fri Oct 03 20:27:02 2008 (48e6d476)	00010f39		FNETURPX.SYS
Sahdad64	fffff880`01966000	fffff880`01971000	Mon Oct 27 21:56:11 2008 (49068d5b)	00012d78		Sahdad64.sys
Saibad64	fffff880`0195d000	fffff880`01966000	Mon Oct 27 21:56:15 2008 (49068d5f)	000068be		Saibad64.sys
SaibVdAd64	fffff880`06be7000	fffff880`06bf1000	Mon Oct 27 21:56:20 2008 (49068d64)	0000aed1		SaibVdAd64.sys
FNETURPX.SYS
Sahdad64.sys
Saibad64.sys
SaibVdAd64.sys


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


Loading Dump File [D:\Kingston\BSODDmpFiles\Twistedben\042312-10966-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`03454650
Debug session time: Sun Apr 22 16:37:40.030 2012 (UTC - 6:00)
System Uptime: 0 days 0:48:35.810
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
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

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3739316361303932
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff800048289c8 -- (.exr 0xfffff800048289c8)
ExceptionAddress: fffff8000328ff84 (nt!SwapContext_PatchXRstor)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80004828a70 -- (.trap 0xfffff80004828a70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffff80004828cc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ff84 rsp=fffff80004828c00 rbp=fffff80004828c70
 r8=fffffa80068eb850  r9=0000000000000000 r10=0000000000000000
r11=fffff80003401e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!SwapContext_PatchXRstor:
fffff800`0328ff84 0fae09          fxrstor [rcx]         ds:fffff800`04828cc0=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000328467e to fffff8000328cc50

STACK_TEXT:  
fffff800`04827aa8 fffff800`0328467e : 00000000`00400120 fffff880`0f22a57a fffff800`04828220 fffff800`032b7c80 : nt!KeBugCheck
fffff800`04827ab0 fffff800`032b794d : fffff800`0349514c fffff800`033d5ee0 fffff800`03210000 fffff800`048289c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04827ae0 fffff800`032b6725 : fffff800`033d5fac fffff800`04827b58 fffff800`048289c8 fffff800`03210000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`04827b10 fffff800`032c76a1 : fffff800`048289c8 fffff800`04828220 fffff800`00000000 fffffa80`06a97060 : nt!RtlDispatchException+0x415
fffff800`048281f0 fffff800`0328c302 : fffff800`048289c8 fffff800`03401e80 fffff800`04828a70 fffff800`0340fcc0 : nt!KiDispatchException+0x135
fffff800`04828890 fffff800`0328ac0a : fffffa80`0818ca88 fffff880`015053b5 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`04828a70 fffff800`0328ff84 : fffffa80`069f1740 00000000`00000000 00000000`00000000 fffffa80`06a97060 : nt!KiGeneralProtectionFault+0x10a
fffff800`04828c00 fffff800`03284a3d : fffff800`03401e80 fffff800`0340fcc0 00000000`00000000 fffff880`014e2a00 : nt!SwapContext_PatchXRstor
fffff800`04828c40 00000000`00000000 : fffff800`04829000 fffff800`04823000 fffff800`04828c00 00000000`00000000 : nt!KiIdleLoop+0x10d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`0328467e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------
The above crash report was rather inconclusive. Possible causes include Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...

We should probably wait for a few more crashes to occur to determine any patterns. If you would like, you could help them along by checking for any driver conflicts.
  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 208657
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

    When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset
    -> Restart your computer.
My System SpecsSystem Spec
24 Apr 2012   #5
Twistedben

Windows 7 Home Premium 64-bit
 
 

writhziden,
Thank you for the prompt reply, I'll be trying the driver verifer and I'll look into the drivers you listed. I already updated the FNETURPX. I haven't yet had another BSOD, but when I do I'll post ASAP. Let's see what the Driver Verifier turns up. Also, I do not have any viruses, and I always do the latest Windows updates. It seems these BSODs started when I upgraded to an OCZ SSD 120gb, but that's inconclusive. And thank you so much for your help!

Twistedben
My System SpecsSystem Spec
24 Apr 2012   #6
Twistedben

Windows 7 Home Premium 64-bit
 
 

Dear Writhziden,

I ran the verifier per the instructions. When I rebooted, after windows loaded, I received a BSOD saying "The IO Manager has detected a violation by a driver being verified." I rebooted into safemode without a hiccup; however, I couldn't retrieve the mini dump file, since safemode was slightly unresponsive. I System Restored back to before Verifier was ran, and tried the verifier again. I received the same BSOD and booted into safemode. This time I ran a CMD Prompt and unloaded Verifier. I rebooted into Windows finely. I retrieved the MiniDump file and attached it here, zipped in RAR form.

Thank you for taking time out of your day to help me.

Twistedben
My System SpecsSystem Spec
24 Apr 2012   #7
writhziden

Windows 7 Home Premium 64 Bit
 
 

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs (at least when Verifier is enabled; it can be re-installed once we determine the true causes if you prefer it over other software).

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


Once you have removed Daemon Tools, enable Verifier again with my previous instructions.
My System SpecsSystem Spec
25 Apr 2012   #8
Twistedben

Windows 7 Home Premium 64-bit
 
 

writhziden,

Thanks again.

I removed Daemon Tools and enabled Verifier. I rebooted and the windows logon screen appeared for 1 second before going to BSOD. This time the quote was: "A device attempting to corrupt the system has been caught. The faulty driver currently on the kernal stack must be replaced with a working version." It also mentioned the driver "vsdatant.sys" in the BSOD. I then booted into safemode fine and turned off verifier. When I restarted I got a Disk Reader Error (Ctrl+Alt+Del to restart). I don't know why I got that but I was able to restart and get into windows without a problem. I attached the minidump file.

Twistedben
My System SpecsSystem Spec
25 Apr 2012   #9
writhziden

Windows 7 Home Premium 64 Bit
 
 

Appears to be part of TrueVector. Do you have Zone Alarm installed (I do not see its other drivers, so I assume not). If not, it is probably part of software made by the same company. Are you familiar with what software it is? If not, please post screenshots of your installed programs. Start Menu -> Control Panel -> Uninstall a program -> Take a screenshot -> Scroll down -> Take a screenshot -> Scroll down -> etc. until you have included all programs in the list.
My System SpecsSystem Spec
25 Apr 2012   #10
Twistedben

Windows 7 Home Premium 64-bit
 
 

Just had my first BSOD not caused on purpose. I booted up Empire: TW and bang!
Here's the Minidump for that, too.
My System SpecsSystem Spec
Reply

 BSOD 10 minutes in playing Empire: TW




Thread Tools




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 01:46 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App