Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 7 0x0000000a BSOD


  • Please log in to reply
2 replies to this topic

#1 johndorrian

johndorrian

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:21 PM

Posted 30 July 2018 - 08:06 AM

Hello All,

I have a QEMU-KVM which has windows 7 running on it. 

This system has been getting very random BSOD's over the past 2 months. the last 3 were caused by a bug in the driver verfier program in windows (bug check: 0x000000C4).

But there have been some IRQL and KERNEL_MODE_TRAP errors which I cant figure out what is causing them.

I have uploaded the system info zip file.

 

any ideas?

 

Thank you so much,

John D

 

Attached Files


Edited by johndorrian, 30 July 2018 - 08:08 AM.


BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:21 AM

Posted 30 July 2018 - 03:41 PM

Hi. . .

Are you over-clocked? Several of the dumps showed numbers like:
MaxSpeed:     1800
CurrentSpeed: 2028
1 dump showed -
MaxSpeed:     3000
CurrentSpeed: 2999
.... so I'm not sure what to believe here.

If you are over-clocked, please reset to default until BSOD epidemic is over.

As for the 4 dumps from late July 2018 - 3 were VERIFIER_ENABLED dumps (Driver Verifier was running) and had bugcheck 0xc4 (Driver Verifier); the other had bugcheck 0xa (attempt to access invalid memory) and named the Microsoft TCP/IP Registry Compatibility Driver tcpipreg.sys -
BugCheck C4, {0, 0, 0, 0}
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {0, 0, 0, 0}
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {8304ad78, ff, 0, 8304ad78}
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {0, 0, 0, 0}
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
tcpipreg.sys is not the actual cause. It is a default of sorts. It's safe to say that whenever Driver Verifier flags a Microsoft driver, unknown hardware failure is the usual cause of the BSODs.

Start with diagnostic tests for RAM and HDD -
RAM - memtest86+ - run 1 stick at a time; alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

HDD - SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html

If you have an SSD, go to the SSD manufacturer's support site and check for firmware upgrades.

Regards. . .

jcgriff2

`

FULL DUMP SUMMARY

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072918-60531-01.dmp]
Built by: 7601.24168.x86fre.win7sp1_ldr.180608-0600
Debug session time: Sun Jul 29 11:45:50.765 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:19.531
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc4_0_VRF_tcpipreg!InterfaceAddressRegKeyChangeHandler+b5
Bugcheck code 000000C4
Arguments 00000000 00000000 00000000 00000000
BiosVersion = 1.10.2-1
BiosReleaseDate = 04/01/2014
SystemManufacturer = QEMU
SystemProductName = Standard PC (i440FX + PIIX, 1996)
MaxSpeed:     1800
CurrentSpeed: 1956
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072918-7843-01.dmp]
Built by: 7601.24168.x86fre.win7sp1_ldr.180608-0600
Debug session time: Sun Jul 29 11:52:43.343 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:21.093
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc4_0_VRF_tcpipreg!InterfaceAddressRegKeyChangeHandler+b5
Bugcheck code 000000C4
Arguments 00000000 00000000 00000000 00000000
BiosVersion = 1.10.2-1
BiosReleaseDate = 04/01/2014
SystemManufacturer = QEMU
SystemProductName = Standard PC (i440FX + PIIX, 1996)
MaxSpeed:     1800
CurrentSpeed: 2028
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072918-9625-01.dmp]
Built by: 7601.24168.x86fre.win7sp1_ldr.180608-0600
Debug session time: Sat Jul 28 10:54:31.868 2018 (UTC - 4:00)
System Uptime: 1 days 23:59:05.868
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  ECDIS.exe
FAILURE_BUCKET_ID:  0xA_CODE_AV_PAGED_IP_nt!KiTrap0E+0
Bugcheck code 0000000A
Arguments 8304ad78 000000ff 00000000 8304ad78
BiosVersion = 1.10.2-1
BiosReleaseDate = 04/01/2014
SystemManufacturer = QEMU
SystemProductName = Standard PC (i440FX + PIIX, 1996)
MaxSpeed:     3000
CurrentSpeed: 2999
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072918-10468-01.dmp]
Built by: 7601.24168.x86fre.win7sp1_ldr.180608-0600
Debug session time: Sun Jul 29 11:33:59.921 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:23.671
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+b5 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc4_0_VRF_tcpipreg!InterfaceAddressRegKeyChangeHandler+b5
Bugcheck code 000000C4
Arguments 00000000 00000000 00000000 00000000
BiosVersion = 1.10.2-1
BiosReleaseDate = 04/01/2014
SystemManufacturer = QEMU
SystemProductName = Standard PC (i440FX + PIIX, 1996)
MaxSpeed:     1800
CurrentSpeed: 1992
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#3 johndorrian

johndorrian
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:21 PM

Posted 31 July 2018 - 04:25 AM

Hey @jcgriff2, thank you so much for the reply!

The overclocking was disabled a few weeks ago and there was still BSOD's. So I did a memtest and the HDD test and they both came back clean. 

Im wondering what would cause the 7F and 0xA bugchecks? the C4 stopped showing up once I removed a registry key (IPAddress).

 

Thank you again!

John D






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users