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 and computer also hangs requiring hard reset,

19 Jul 2017   #11
axe0

Windows 10 Pro
 
 

The USB list is of all USB devices connected, I believe both direct and indirect.


My System SpecsSystem Spec
.
06 Aug 2017   #12
madboy23

windows 7 x64
 
 

Hi there again, I replaced my power supply with a corsair rm750i, i reinstalled windows and i am still getting BSOD. But the last 2 are exactly the same, seems like it might be the cpu. What do you think?


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-38610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea0750
Debug session time: Sun Aug 6 17:01:59.288 2017 (UTC + 1:00)
System Uptime: 0 days 2:20:38.850
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800dec7028, be000000, 800400}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800dec7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`009f7b58 fffff800`02c27a3b : 00000000`00000124 00000000`00000000 fffffa80`0dec7028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f7b60 fffff800`02de7fef : 00000000`00000001 fffffa80`0dd8a870 00000000`00000000 fffffa80`0dd8a8c0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7ba0 fffff800`02c27700 : 00000000`00000728 fffffa80`0dd8a870 fffff880`009f7f30 fffff880`009f7f00 : nt!WheaReportHwError+0x26f
fffff880`009f7c00 fffff800`02c27052 : fffffa80`0dd8a870 fffff880`009f7f30 fffffa80`0dd8a870 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7d50 fffff800`02c26f0d : 00000000`00000008 00000000`00000001 fffff880`009f7fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7d90 fffff800`02c1ae88 : 00000000`00000002 fffffa80`0e4971a0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7dc0 fffff800`02ccd72c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7df0 fffff800`02ccd593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7f30 fffff800`02cd8bc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1ba40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseSpinLock+0x6


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

SECOND MINI DMP


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-37221-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4c750
Debug session time: Sun Aug 6 18:22:54.927 2017 (UTC + 1:00)
System Uptime: 0 days 0:23:42.756
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800de3f028, be000000, 800400}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de3f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff800`040e7a98 fffff800`03202a3b : 00000000`00000124 00000000`00000000 fffffa80`0de3f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`040e7aa0 fffff800`02d93fef : 00000000`00000001 fffffa80`0de362a0 00000000`00000000 fffffa80`0de362f0 : hal!HalBugCheckSystem+0x1e3
fffff800`040e7ae0 fffff800`03202700 : 00000000`00000728 fffffa80`0de362a0 fffff800`040e7e70 fffff800`040e7e00 : nt!WheaReportHwError+0x26f
fffff800`040e7b40 fffff800`03202052 : fffffa80`0de362a0 fffff800`040e7e70 fffffa80`0de362a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`040e7c90 fffff800`03201f0d : 00000000`00000008 00000000`00000001 fffff800`040e7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`040e7cd0 fffff800`031f5e88 : 00000000`00000002 fffffa80`0e57b100 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`040e7d00 fffff800`02c7972c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`040e7d30 fffff800`02c79593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`040e7e70 fffff800`02c84cef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`040dba20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x4f


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de3f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff800`040e7a98 fffff800`03202a3b : 00000000`00000124 00000000`00000000 fffffa80`0de3f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`040e7aa0 fffff800`02d93fef : 00000000`00000001 fffffa80`0de362a0 00000000`00000000 fffffa80`0de362f0 : hal!HalBugCheckSystem+0x1e3
fffff800`040e7ae0 fffff800`03202700 : 00000000`00000728 fffffa80`0de362a0 fffff800`040e7e70 fffff800`040e7e00 : nt!WheaReportHwError+0x26f
fffff800`040e7b40 fffff800`03202052 : fffffa80`0de362a0 fffff800`040e7e70 fffffa80`0de362a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`040e7c90 fffff800`03201f0d : 00000000`00000008 00000000`00000001 fffff800`040e7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`040e7cd0 fffff800`031f5e88 : 00000000`00000002 fffffa80`0e57b100 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`040e7d00 fffff800`02c7972c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`040e7d30 fffff800`02c79593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`040e7e70 fffff800`02c84cef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`040dba20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x4f


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Aug 2017   #13
axe0

Windows 10 Pro
 
 

The dumps only show that a processor aborts any processing and reports an error after which the system crashes, this is a standard thing with 0x124 crashes.
Run !errrec command on argument 2, e.g. of last dump !errrec fffffa800de3f028, it dumps the error records that contains the reason why a crash was called. Please post the output of the error record, note the triple 'r' in !errrec.

EDIT: run the !errrec command on all recent 0x124 dumps. The more error records there are, the easier it is to find the reason for the crashes.
My System SpecsSystem Spec
.

06 Aug 2017   #14
madboy23

windows 7 x64
 
 

Here is the dm diagnosis, do you still see usb as a problem,

Cheers,
Mike


Attached Files
File Type: zip MIKE2-PC-06_08_2017_193238_45.zip (790.5 KB, 1 views)
My System SpecsSystem Spec
06 Aug 2017   #15
axe0

Windows 10 Pro
 
 

Included hard drive tests, file system issues explained in post #6 is still happening




BSOD and computer also hangs requiring hard reset, STOP 0x124 Troubleshooting BSOD and computer also hangs requiring hard reset,
Read carefully before proceeding.


warning   Warning
If you're overclocking your system, revert back to stock clocks now.

Note   Note
Test the system once the overclock is removed before continuing with the steps outlined below.


Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test




BSOD and computer also hangs requiring hard reset, ONE BSOD and computer also hangs requiring hard reset,
 CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

warning   Warning
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.




BSOD and computer also hangs requiring hard reset, TWO BSOD and computer also hangs requiring hard reset,
 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

Note   Note


MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it please.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.




BSOD and computer also hangs requiring hard reset, Diagnostics Test BSOD and computer also hangs requiring hard reset,
 HDD TEST

Note   Note
Please run HDTune first, in the order posted!

Run HDTune to
  • check the health,
  • scan for errors, no quick scan but full scan
  • run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
  • the health,
  • the error scan,
  • the benchmark incl. following
    • transfer rate,
    • access time,
    • burst rate,
    • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
Note   Note
Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :arrow: Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums





BSOD and computer also hangs requiring hard reset, FOUR BSOD and computer also hangs requiring hard reset,
 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

Note   Note
Run Furmark for around 30 minutes.

warning   Warning
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.
My System SpecsSystem Spec
07 Aug 2017   #16
madboy23

windows 7 x64
 
 

I am currently scanning drives using hd tune, no problems yet but only done 4 drives and i have 11, on most of the drives I can't get any info under the health tab, is that because they are usb?

I also used the drive verifier programme, windows would not even load just got to starting windows and BSOD repeatedly every time I tried to boot into windows, had to go into safe mode and turn drive verifier off. Got this dmp file.


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-9375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e54750
Debug session time: Sun Aug 6 20:01:14.846 2017 (UTC + 1:00)
System Uptime: 0 days 0:00:09.658
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {215, fffff8800f041eab, fffff980082b0e10, 0}

*** WARNING: Unable to verify timestamp for NIWinCDEmu.sys
*** ERROR: Module load completed but symbols could not be loaded for NIWinCDEmu.sys
Probably caused by : NIWinCDEmu.sys ( NIWinCDEmu+9eab )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000215, A non-successful non-STATUS_NOT_SUPPORTED IRP status for IRP_MJ_PNP is being
passed down stack. Failed PNP IRPs must be completed.
Arg2: fffff8800f041eab, The address in the driver's code where the error was detected.
Arg3: fffff980082b0e10, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc9_215

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 215

FAULTING_IP:
NIWinCDEmu+9eab
fffff880`0f041eab 4883c438 add rsp,38h

FOLLOWUP_IP:
NIWinCDEmu+9eab
fffff880`0f041eab 4883c438 add rsp,38h

IRP_ADDRESS: fffff980082b0e10

DEVICE_OBJECT: fffffa800f499e00

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800031154ec to fffff80002c82e40

STACK_TEXT:
fffff880`033af0d8 fffff800`031154ec : 00000000`000000c9 00000000`00000215 fffff880`0f041eab fffff980`082b0e10 : nt!KeBugCheckEx
fffff880`033af0e0 fffff800`0311f5aa : fffff800`03113b00 fffff880`0f041eab fffff980`082b0e10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033af120 fffff800`031205b3 : 00000000`00000215 fffff880`0f041eab fffff980`082b0e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033af170 fffff800`0312c1e2 : fffff980`082b0f70 00000000`00000002 00000000`00000000 fffff800`02d7227b : nt!VfErrorReport1+0x63
fffff880`033af210 fffff800`03115230 : fffff980`082b0f70 fffffa80`0f498760 fffff980`082b0f70 fffff980`082b0f70 : nt!VfPnpVerifyIrpStackDownward+0xe2
fffff880`033af280 fffff800`0312dc80 : fffffa80`0f498760 fffffa80`0f7e0050 fffff980`082b0e10 fffffa80`0e0c01c8 : nt!VfMajorVerifyIrpStackDownward+0x80
fffff880`033af2e0 fffff800`0312deb6 : fffff980`00000000 fffffa80`00000000 fffffa80`00000000 fffff880`0f041eab : nt!IovpCallDriver1+0x4a0
fffff880`033af390 fffff800`03131ce2 : fffff980`082b0e10 00000000`00000002 fffff980`082b0e48 00000000`00000000 : nt!VfBeforeCallDriver+0x186
fffff880`033af3f0 fffff880`0f041eab : fffff980`082b0e10 00000000`00000002 fffffa80`0f499060 fffffa80`0f7f4430 : nt!IovCallDriver+0x502
fffff880`033af450 fffff980`082b0e10 : 00000000`00000002 fffffa80`0f499060 fffffa80`0f7f4430 fffffa80`00000000 : NIWinCDEmu+0x9eab
fffff880`033af458 00000000`00000002 : fffffa80`0f499060 fffffa80`0f7f4430 fffffa80`00000000 fffff980`082b0e10 : 0xfffff980`082b0e10
fffff880`033af460 fffffa80`0f499060 : fffffa80`0f7f4430 fffffa80`00000000 fffff980`082b0e10 fffff980`014c8e00 : 0x2
fffff880`033af468 fffffa80`0f7f4430 : fffffa80`00000000 fffff980`082b0e10 fffff980`014c8e00 fffff880`0f0420c4 : 0xfffffa80`0f499060
fffff880`033af470 fffffa80`00000000 : fffff980`082b0e10 fffff980`014c8e00 fffff880`0f0420c4 fffff980`014c8e00 : 0xfffffa80`0f7f4430
fffff880`033af478 fffff980`082b0e10 : fffff980`014c8e00 fffff880`0f0420c4 fffff980`014c8e00 fffff880`033af510 : 0xfffffa80`00000000
fffff880`033af480 fffff980`014c8e00 : fffff880`0f0420c4 fffff980`014c8e00 fffff880`033af510 fffffa80`0e0c01c8 : 0xfffff980`082b0e10
fffff880`033af488 fffff880`0f0420c4 : fffff980`014c8e00 fffff880`033af510 fffffa80`0e0c01c8 00000000`00000002 : 0xfffff980`014c8e00
fffff880`033af490 fffff980`014c8e00 : fffff880`033af510 fffffa80`0e0c01c8 00000000`00000002 00000000`00000000 : NIWinCDEmu+0xa0c4
fffff880`033af498 fffff880`033af510 : fffffa80`0e0c01c8 00000000`00000002 00000000`00000000 fffff880`0f041f28 : 0xfffff980`014c8e00
fffff880`033af4a0 fffffa80`0e0c01c8 : 00000000`00000002 00000000`00000000 fffff880`0f041f28 fffff880`033af740 : 0xfffff880`033af510
fffff880`033af4a8 00000000`00000002 : 00000000`00000000 fffff880`0f041f28 fffff880`033af740 00000000`00000000 : 0xfffffa80`0e0c01c8
fffff880`033af4b0 00000000`00000000 : fffff880`0f041f28 fffff880`033af740 00000000`00000000 00000000`00000002 : 0x2


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: NIWinCDEmu+9eab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NIWinCDEmu

IMAGE_NAME: NIWinCDEmu.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5062e9b1

FAILURE_BUCKET_ID: X64_0xc9_215_VRF_NIWinCDEmu+9eab

BUCKET_ID: X64_0xc9_215_VRF_NIWinCDEmu+9eab

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc9_215_vrf_niwincdemu+9eab

FAILURE_ID_HASH: {29fd4de1-7065-5473-6755-81a7450a8ed5}

Followup: MachineOwner
---------
My System SpecsSystem Spec
07 Aug 2017   #17
madboy23

windows 7 x64
 
 

My System SpecsSystem Spec
07 Aug 2017   #18
axe0

Windows 10 Pro
 
 

Please finish the hardware scans, the driver being flagged could be a false positive as a result of bad hardware.
My System SpecsSystem Spec
Reply

 BSOD and computer also hangs requiring hard reset,




Thread Tools




Similar help and support threads
Thread Forum
After 6 hours, the PC just hangs and I have to hard reset
This happened EVERY DAY. I have my PC set to turn off automatically at 1 AM. If I leave it on all day then the next morning I'll come to it and it'll just have the desktop there and none of the icons or ctrl alt del or even pressing the power button will work. I have to hard reset. It's screwing up...
BSOD Help and Support
New Computer Randomly Hard Freezes requiring cold boot to get working.
New custom computer running windows 7 64 pro with SP1. I installed the Os, and drivers from the Asus motherboard disk, on the first day I got it, and from the 2nd day the computer started having random freezes that vary from 1-3 times per day. The first time was while watching a video,...
General Discussion
Random Computer Freeze Requiring Hard Reset
Hello, I recently reinstalled Windows 7 on my custom built PC. Since doing so I have random freezes that allow me to do nothing other than hard reset the computer. There is no particular time that it does it, and it has mostly been noticed while either on the desktop or using Firefox. ...
BSOD Help and Support
Random computer freeze requiring hard reset
Hi all, I've been having this problem for quite some time now (I would say a year or more) where my computer completely freezes up without any prompting. It's quite frustrating to diagnose since it happens on such a random basis -there seems to be no trend as to what kind of programs I have...
General Discussion
Laptop screen goes black, requiring hard reset
Hello, I was hoping maybe somebody could help me with this laptop. The issue I'm having is most of the time when I walk away from it and leave it on, upon returning the screen is just black, the computer is running but there is no response on the keyboard or mouse, which requires a hard shutdown...
General Discussion


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