Blue Screen Of Death!!!

garyleung140 · Feb 8, 2014

I keep getting the BSOD when using my computer for about 30 mins to an hour.

Specs:
OS: windows 8.1
Mother board: Gigabyte ga-78lmt-usb3
Graphics card: HD Radeon 7750 2gb
Processor: AMD FX-6300 six core processor
RAM: 16gb 1333mhz
Power Supply: 650 Watt Quiet Power Supply Featuring Large 120mm Cooling Fan

I installed "whocrashed" and this is what it says:

On Sat 08/02/2014 23:51:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-17437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x389A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803F524C9A2, 0xFFFFD00020BE7748, 0xFFFFD00020BE6F50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 08/02/2014 23:51:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803F524C9A2, 0xFFFFD00020BE7748, 0xFFFFD00020BE6F50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 08/02/2014 23:40:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-24156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8039543E9A2, 0xFFFFD0002BE76270, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 08/02/2014 22:40:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-18187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x389A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803A444B9A2, 0xFFFFD00020BE7748, 0xFFFFD00020BE6F50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

There are a lot more....tell me if you need them.

Please help! Its getting really annoying...

johnbl · Feb 9, 2014

Other than just guessing that you have a bug in your graphics driver and need to update it. You would need to post your actual memory .dmp file on a public cloud server like skydrive with public access. Often it only take a moment to check for the cause of the problem with the windows debugger.

garyleung140 · Feb 9, 2014

johnbl :

Here are the minidump files

http://sdrv.ms/1bgCN5N

Also i have tried reinstalling the graphics driver but it still happens

johnbl · Feb 9, 2014

Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505

I looked at your first crash dump, it was caused by a invalid address being passed in to a windows kernel routine.

start by removing these two drivers:

\??\C:\Windows\GVTDrv64.sys Tue Sep 05 00:10:02 2006 (44FD22CA)
\??\C:\Windows\gdrv.sys Thu Mar 12 20:22:29 2009

then retest for failure.

garyleung140 · Feb 10, 2014

How do i remove them?

and are they important for anything?

garyleung140 · Feb 10, 2014

i looked at event manager and it says this before it bluescreens "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8016c8a89a2, 0xffffd00020be7748, 0xffffd00020be6f50)."

johnbl · Feb 10, 2014

first one is Gigabyte Easy Tune 6 driver
I think the second one is also a old gigabyte driver.
I would look in control panel, and see if they have a uninstall program.

garyleung140 :

garyleung140 · Feb 11, 2014

I uninstalled easytuner and downloaded auto run and disabled both of the drivers but it keeps bluescreening.

johnbl · Feb 11, 2014

i don't see the new debug dump, the crash dump was updated but the crash was on
Sun Feb 9 07:10:54.390 2014 (UTC - 8:00)
and still had the same drivers installed.

delete the old dump files and upload a current one and I will take another look.

garyleung140 · Feb 11, 2014

Sorry i sent that message on my phone.
i will upload the new one now

garyleung140 · Feb 11, 2014

the new files have been added

garyleung140 · Feb 11, 2014

it just bluescreened again.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff801c163f9a2, 0xffffd00020be7748, 0xffffd00020be6f50). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021114-13734-01.

johnbl · Feb 11, 2014

-you have a device driver waiting to access data that is "locked" the lock is not getting released.
I am unable to tell what driver is waiting based on the limited debug information in the mini dump.
I would also remove GEARAspiWDM.sys I think it is a part of itunes (google for it to check)

3: kd> lmvm GEARAspiWDM
start end module name
fffff800`01a00000 fffff800`01a06c00 GEARAspiWDM (deferred)
Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys
Image name: GEARAspiWDM.sys
Timestamp: Thu May 03 12:56:17 2012 (4FA2E2E1)
CheckSum: 00008963
ImageSize: 00006C00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

-what you will want to do is update as many 3rd party drivers for your system, and remove the ones you don't need.
In particular your graphics drivers are out of date and your chipset drivers are out of date. You will want update them directly from
http://support.amd.com/en-us/download

if you continue to get the same crash after these updates, you will want to run verifier.exe and enable deadlock detection on your 3rd party drivers.
This will case the system to bluescreen and name the driver that caused the problem. Here is some info on how to run verifier.exe
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html. You will also want to change your memory dump settings to be a full kernel dump. This will cause the dump to include the various driver shared data structures so the cause can be identified.

when you are done with the verifier.exe you will want to run the verifier.exe /reset command to turn off all the special checking on the drivers or you system will run kind of slow (or very slow, depending on your system)

I would also remove any optional drivers:
\??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

you will want to get updates for your wireless driver
\SystemRoot\system32\DRIVERS\RTL8192su.sys
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=48&Level=5&Conn=4&ProdID=231

and because it is a usb device you will want to make sure you have updated
your usb driver for
ViaHub3.sys Sun Aug 11 20:12:43 2013 (here is a link but the drivers are old) You might move your device to another controller or a usb 2.0 connection.
http://www.via-labs.com/en/support/downloads.jsp#hostdriver

Note: there are often issues related to installation of device drivers for USB devices, And that is the the device driver you just installed may not end up being the selected device driver that is enabled. (you install a new one but the system continues to use the old one until you manually make force a change in device manager)

Again from the memory dump provided you can not tell which driver is holding the lock that is causing the system problem.
so update your drivers, if the problem still occurs. run verifier.exe and set system flags to detect deadlocks on various 3rd party drivers.
and change your crash dump type to full kernel mode dump. This will allow the debugger to be to determine the ownership of the locks that are blocking the system. Note: be sure to do the updates because all the debugger is going to do is indicated the driver that has the problem and then you will just have to look for a updated driver anyway.

problem:
BugCheck 1000007E, {ffffffffc0000005, fffff801c163f9a2, ffffd00020be7748, ffffd00020be6f50}
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12

3: kd> kc
Call Site
nt!KxWaitForLockOwnerShip
nt!MmZeroPageThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread

machine info:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
System Uptime: 0 days 0:07:57.158

Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
BIOS Release Date 04/23/2013
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 90h - 1.6V
External Clock 200MHz
Max Speed 3000MHz
Current Speed 4100MHz
Memory Module Voltage 2.9V
Number of Memory Slots 4

-no memory corruption of major OS files detected by debugger.

garyleung140 · Feb 12, 2014

johnbl :

-you have a device driver waiting to access data that is "locked" the lock is not getting released.
I am unable to tell what driver is waiting based on the limited debug information in the mini dump.
I would also remove GEARAspiWDM.sys I think it is a part of itunes (google for it to check)

3: kd> lmvm GEARAspiWDM
start end module name
fffff800`01a00000 fffff800`01a06c00 GEARAspiWDM (deferred)
Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys
Image name: GEARAspiWDM.sys
Timestamp: Thu May 03 12:56:17 2012 (4FA2E2E1)
CheckSum: 00008963
ImageSize: 00006C00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

-what you will want to do is update as many 3rd party drivers for your system, and remove the ones you don't need.
In particular your graphics drivers are out of date and your chipset drivers are out of date. You will want update them directly from
http://support.amd.com/en-us/download

if you continue to get the same crash after these updates, you will want to run verifier.exe and enable deadlock detection on your 3rd party drivers.
This will case the system to bluescreen and name the driver that caused the problem. Here is some info on how to run verifier.exe
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html. You will also want to change your memory dump settings to be a full kernel dump. This will cause the dump to include the various driver shared data structures so the cause can be identified.

when you are done with the verifier.exe you will want to run the verifier.exe /reset command to turn off all the special checking on the drivers or you system will run kind of slow (or very slow, depending on your system)

I would also remove any optional drivers:
\??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

you will want to get updates for your wireless driver
\SystemRoot\system32\DRIVERS\RTL8192su.sys
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=48&Level=5&Conn=4&ProdID=231

and because it is a usb device you will want to make sure you have updated
your usb driver for
ViaHub3.sys Sun Aug 11 20:12:43 2013 (here is a link but the drivers are old) You might move your device to another controller or a usb 2.0 connection.
http://www.via-labs.com/en/support/downloads.jsp#hostdriver

Note: there are often issues related to installation of device drivers for USB devices, And that is the the device driver you just installed may not end up being the selected device driver that is enabled. (you install a new one but the system continues to use the old one until you manually make force a change in device manager)

Again from the memory dump provided you can not tell which driver is holding the lock that is causing the system problem.
so update your drivers, if the problem still occurs. run verifier.exe and set system flags to detect deadlocks on various 3rd party drivers.
and change your crash dump type to full kernel mode dump. This will allow the debugger to be to determine the ownership of the locks that are blocking the system. Note: be sure to do the updates because all the debugger is going to do is indicated the driver that has the problem and then you will just have to look for a updated driver anyway.

problem:
BugCheck 1000007E, {ffffffffc0000005, fffff801c163f9a2, ffffd00020be7748, ffffd00020be6f50}
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12

3: kd> kc
Call Site
nt!KxWaitForLockOwnerShip
nt!MmZeroPageThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread

machine info:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
System Uptime: 0 days 0:07:57.158

Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
BIOS Release Date 04/23/2013
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 90h - 1.6V
External Clock 200MHz
Max Speed 3000MHz
Current Speed 4100MHz
Memory Module Voltage 2.9V
Number of Memory Slots 4

-no memory corruption of major OS files detected by debugger.

Okay ill set the dump file to full and wait for it to bluescreen again then upload the file to see if it gives more detail.
Do i set the memory dump to "Kernel dump" or "complete dump"?

johnbl · Feb 12, 2014

both will work but the complete dump is pretty big and you will want to zip it up to get a much smaller size.
you will want to run verifier.exe and set some system tracking for deadlock detection.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

to disable verifier you would type the command
verifier.exe /reset

quotemsg=12663873,0,1540515]

johnbl :

-you have a device driver waiting to access data that is "locked" the lock is not getting released.
I am unable to tell what driver is waiting based on the limited debug information in the mini dump.
I would also remove GEARAspiWDM.sys I think it is a part of itunes (google for it to check)

3: kd> lmvm GEARAspiWDM
start end module name
fffff800`01a00000 fffff800`01a06c00 GEARAspiWDM (deferred)
Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys
Image name: GEARAspiWDM.sys
Timestamp: Thu May 03 12:56:17 2012 (4FA2E2E1)
CheckSum: 00008963
ImageSize: 00006C00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

-what you will want to do is update as many 3rd party drivers for your system, and remove the ones you don't need.
In particular your graphics drivers are out of date and your chipset drivers are out of date. You will want update them directly from
http://support.amd.com/en-us/download

if you continue to get the same crash after these updates, you will want to run verifier.exe and enable deadlock detection on your 3rd party drivers.
This will case the system to bluescreen and name the driver that caused the problem. Here is some info on how to run verifier.exe
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html. You will also want to change your memory dump settings to be a full kernel dump. This will cause the dump to include the various driver shared data structures so the cause can be identified.

when you are done with the verifier.exe you will want to run the verifier.exe /reset command to turn off all the special checking on the drivers or you system will run kind of slow (or very slow, depending on your system)

I would also remove any optional drivers:
\??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

you will want to get updates for your wireless driver
\SystemRoot\system32\DRIVERS\RTL8192su.sys
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=48&Level=5&Conn=4&ProdID=231

and because it is a usb device you will want to make sure you have updated
your usb driver for
ViaHub3.sys Sun Aug 11 20:12:43 2013 (here is a link but the drivers are old) You might move your device to another controller or a usb 2.0 connection.
http://www.via-labs.com/en/support/downloads.jsp#hostdriver

Note: there are often issues related to installation of device drivers for USB devices, And that is the the device driver you just installed may not end up being the selected device driver that is enabled. (you install a new one but the system continues to use the old one until you manually make force a change in device manager)

Again from the memory dump provided you can not tell which driver is holding the lock that is causing the system problem.
so update your drivers, if the problem still occurs. run verifier.exe and set system flags to detect deadlocks on various 3rd party drivers.
and change your crash dump type to full kernel mode dump. This will allow the debugger to be to determine the ownership of the locks that are blocking the system. Note: be sure to do the updates because all the debugger is going to do is indicated the driver that has the problem and then you will just have to look for a updated driver anyway.

problem:
BugCheck 1000007E, {ffffffffc0000005, fffff801c163f9a2, ffffd00020be7748, ffffd00020be6f50}
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12

3: kd> kc
Call Site
nt!KxWaitForLockOwnerShip
nt!MmZeroPageThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread

machine info:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
System Uptime: 0 days 0:07:57.158

Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
BIOS Release Date 04/23/2013
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 90h - 1.6V
External Clock 200MHz
Max Speed 3000MHz
Current Speed 4100MHz
Memory Module Voltage 2.9V
Number of Memory Slots 4

-no memory corruption of major OS files detected by debugger.

Okay ill set the dump file to full and wait for it to bluescreen again then upload the file to see if it gives more detail.
Do i set the memory dump to "Kernel dump" or "complete dump"?[/quotemsg]

garyleung140 · Feb 12, 2014

johnbl :

both will work but the complete dump is pretty big and you will want to zip it up to get a much smaller size.
you will want to run verifier.exe and set some system tracking for deadlock detection.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

to disable verifier you would type the command
verifier.exe /reset

quotemsg=12663873,0,1540515]

johnbl :

-you have a device driver waiting to access data that is "locked" the lock is not getting released.
I am unable to tell what driver is waiting based on the limited debug information in the mini dump.
I would also remove GEARAspiWDM.sys I think it is a part of itunes (google for it to check)

3: kd> lmvm GEARAspiWDM
start end module name
fffff800`01a00000 fffff800`01a06c00 GEARAspiWDM (deferred)
Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys
Image name: GEARAspiWDM.sys
Timestamp: Thu May 03 12:56:17 2012 (4FA2E2E1)
CheckSum: 00008963
ImageSize: 00006C00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

-what you will want to do is update as many 3rd party drivers for your system, and remove the ones you don't need.
In particular your graphics drivers are out of date and your chipset drivers are out of date. You will want update them directly from
http://support.amd.com/en-us/download

if you continue to get the same crash after these updates, you will want to run verifier.exe and enable deadlock detection on your 3rd party drivers.
This will case the system to bluescreen and name the driver that caused the problem. Here is some info on how to run verifier.exe
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html. You will also want to change your memory dump settings to be a full kernel dump. This will cause the dump to include the various driver shared data structures so the cause can be identified.

when you are done with the verifier.exe you will want to run the verifier.exe /reset command to turn off all the special checking on the drivers or you system will run kind of slow (or very slow, depending on your system)

I would also remove any optional drivers:
\??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

you will want to get updates for your wireless driver
\SystemRoot\system32\DRIVERS\RTL8192su.sys
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=48&Level=5&Conn=4&ProdID=231

and because it is a usb device you will want to make sure you have updated
your usb driver for
ViaHub3.sys Sun Aug 11 20:12:43 2013 (here is a link but the drivers are old) You might move your device to another controller or a usb 2.0 connection.
http://www.via-labs.com/en/support/downloads.jsp#hostdriver

Note: there are often issues related to installation of device drivers for USB devices, And that is the the device driver you just installed may not end up being the selected device driver that is enabled. (you install a new one but the system continues to use the old one until you manually make force a change in device manager)

Again from the memory dump provided you can not tell which driver is holding the lock that is causing the system problem.
so update your drivers, if the problem still occurs. run verifier.exe and set system flags to detect deadlocks on various 3rd party drivers.
and change your crash dump type to full kernel mode dump. This will allow the debugger to be to determine the ownership of the locks that are blocking the system. Note: be sure to do the updates because all the debugger is going to do is indicated the driver that has the problem and then you will just have to look for a updated driver anyway.

problem:
BugCheck 1000007E, {ffffffffc0000005, fffff801c163f9a2, ffffd00020be7748, ffffd00020be6f50}
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12

3: kd> kc
Call Site
nt!KxWaitForLockOwnerShip
nt!MmZeroPageThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread

machine info:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
System Uptime: 0 days 0:07:57.158

Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-78LMT-USB3
BIOS Release Date 04/23/2013
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 90h - 1.6V
External Clock 200MHz
Max Speed 3000MHz
Current Speed 4100MHz
Memory Module Voltage 2.9V
Number of Memory Slots 4

-no memory corruption of major OS files detected by debugger.

Okay ill set the dump file to full and wait for it to bluescreen again then upload the file to see if it gives more detail.
Do i set the memory dump to "Kernel dump" or "complete dump"?

[/quotemsg]

Okay

Ill do that after when it bluescreens again

garyleung140 · Feb 13, 2014

What do i do after i loaded up verifier.
Which option do i select to enable deadlocks detection?

thanks

garyleung140 · Feb 13, 2014

hmm okay.
so it bluescreened again and i have the complete dump file here and its 15gb.
when ever i try and zip it it says "file not found or no read permission.

what should i do?

garyleung140 · Feb 13, 2014

oh wait nevermind.
i opened winrar as admin and it works now.

garyleung140 · Feb 15, 2014

Okay so i have enabled verifier and it had bluescreened a couple of times now. what do i do next?

I have uploaded the new dump files onto the skydrive

johnbl · Feb 15, 2014

I think what happened was your old overclocking software from 2006 did not know about the new processor and guessed at the voltage but the newer processors use a lower voltage and that caused CPU issues which caused various bugchecks.
You then removed the old software but did not update or reset your BIOS so the incorrect voltages are still causing the problems even though your old overclocking drivers are not installed.
overclocking driver release date Tue Sep 05 00:10:02 2006
your cpu release date 2012-10-23, (default voltages have dropped on CPUs over the years and may be the root cause of your issue)

- I looked at your crash dumps, 3 were access violations caused by bad memory references and one was corrupt.
- you have set verifier to check certain structures but you also need to change the minidump type to be kernel or full
otherwise this data is just not saved to them memory dump file and can not be retrieved from the dump.

- I think in this case you have a hardware issue. your BIOS is reporting 1.6v to the CPU for a CPU that should run 0.8–1.425 V
I would reset the BIOS back to the defaults and see if your system is stable. Or manually set your CPU and turn off any overclocking.

because your system is unstable you will want to boot a memtest86 CD and get it to run with out errors before it is worthwhile to actually look for windows driver bugs.

as you get more and more bugchecks there is a chance that your filesystem will get corrupted then you will start getting bugcheck related to that corruption even though it was not the original cause of your problem.

at this point you need to get your hardware stable, then run a full chkdsk /f /r on your drives
then sfc.exe /scannow to check for file corruption in core OS files.

after you do that you will be back to where you can look for your original problem again.

debug info
System Uptime: 0 days 0:00:43.158
Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8000097ad6c, 2, 8, fffff8000097ad6c}
GetPointerFromAddress: unable to read from fffff803d2f57100

garyleung140 · Feb 16, 2014

I get this message whenever i load up my pc

Message:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Multiple&Prod_Card__Reader&Rev_1.00#058F63666438&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Could it be to do with that and how can i fix it?

garyleung140 · Feb 16, 2014

Now i have this message:

A corruption was discovered in the file system structure on volume ??.

A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$SII:$INDEX_ALLOCATION".

Detail:

+ System

- Provider

[ Name] Ntfs
[ Guid] {DD70BC80-EF44-421B-8AC3-CD31DA613A4E}

EventID 55

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2014-02-16T20:20:02.626600600Z

EventRecordID 2589

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 168

Channel System

Computer GarysPC

- Security

[ UserID] S-1-5-18

- EventData

DriveName ??
DeviceName \Device\HarddiskVolumeShadowCopy4
CorruptionState 0x0
HeaderFlags 0x922
Severity Critical
Origin File System Driver
Verb Index Subtree
Description A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$SII:$INDEX_ALLOCATION".
Signature 0x457b0dd
Outcome Read Only Volume
SampleLength 0
SampleData
SourceFile 0x14
SourceLine 4004
SourceTag 351
CallStack Ntfs+0x1582fa, Ntfs+0xd5122, Ntfs+0xaf3bd, Ntfs+0xaf73b, Ntfs+0xacb0f, Ntfs+0xae5c4, Ntfs+0x24c8c, Ntfs+0x116048, Ntfs+0x109f7d, Ntfs+0x88cf7, Ntfs+0xa618, ntoskrnl+0xa11b9, ntoskrnl+0x8d2e4, ntoskrnl+0x1542c6

It says that the NTFS file is corrupted what should i do?

garyleung140 · Mar 4, 2014

Heyyy its been a couple of weeks now and my pc has not bluescreened since i reset the bios.
i think it worked!

thank you so much for you help

Blue Screen Of Death!!!

Honorable

Polypheme

Honorable

Polypheme

Honorable

Honorable

Polypheme

Honorable

Polypheme

Honorable

Honorable

Honorable

Polypheme

Honorable

Polypheme

Honorable

Honorable

Honorable

Honorable

Honorable

Polypheme

Honorable

Honorable

Honorable

Share this page