Solved BSOD only on first boot of the day

craigwf · Jul 10, 2012

Computer is just over a month old. Win 7 Ultimate x64 - N version came installed on new drive. On both 7/5 and 7/7 I had a BSOD within a minute of the first boot of the day. The only thing I saw was Memory Management error. I ran Memtest86+ and both 4GB Crucial 1600MHz sticks tested without errors. I do have one problem with the Gigabyte GA-Z77M-D3H motherboard - I can seldom ever get into the BIOS. Back in June I did flash the BIOS to the current version shown for the motherboard at Gigabyte (didn't help my inability to get into the BIOS), and I installed new motherboard drivers. When I did that, I installed VIA Audio drivers; I think the system builder had installed Realtek. I disabled the HD Audio (Realtek?) device in Device Manager. The System info says it can't detect any anti-virus. Why can't it detect my up-to-date Microsoft Security Essentials? Weird. Thanks in advance for your assistance.

usasma · Jul 10, 2012

I only ran the last 2 memory dumps as there was a gap of almost a month since the previous one.

Re-enable the High Definition Audio.
Update it's drivers
Then, if so desired, disable the device again.

Perfmon sometimes doesn't detect A/V - I generally ignore this as my later checks involve looking for it manually.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Acronis and Virtual PC are older programs (from 2010). They could be causing issues, but let's hold off on them for now.

I've got a gut feeling about memory here (the cold boot scenario) - try running MemTest86+, Prime95, and the video tests from this link: Hardware Diagnostics

Try running MemTest86+ when the system is cold (make it the first boot of the day).

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
HECIx64.sys           Wed Nov 09 19:52:25 2011 (4EBB2049)
L1C62x64.sys          Wed Aug 03 02:21:09 2011 (4E38E8D5)
MpFilter.sys          Fri Mar 09 06:05:26 2012 (4F59E3F6)
SmartDefragDriver.sys Fri Nov 26 04:29:40 2010 (4CEF7E04)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dtsoftbus01.sys       Fri Jan 13 08:45:46 2012 (4F10358A)
fltsrv.sys            Thu Jul 14 05:50:57 2011 (4E1EBC01)
igdkmd64.sys          Mon Mar 19 19:31:54 2012 (4F67C1EA)
iusb3hcs.sys          Tue Mar 27 04:11:21 2012 (4F717629)
iusb3hub.sys          Tue Mar 27 04:09:29 2012 (4F7175B9)
iusb3xhc.sys          Tue Mar 27 04:09:32 2012 (4F7175BC)
keyscrambler.sys      Wed Dec 14 19:46:31 2011 (4EE94367)
snapman.sys           Wed Mar 09 08:22:38 2011 (4D777F1E)
speedfan.sys          Fri Mar 18 12:08:46 2011 (4D83838E)
timntr.sys            Thu Jul 29 13:29:24 2010 (4C51BA74)
viahduaa.sys          Fri May 04 06:35:46 2012 (4FA3B102)
vididr.sys            Tue Apr 12 07:31:24 2011 (4DA4380C)
vpchbus.sys           Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcnfltr.sys          Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys            Sat Nov 20 06:35:31 2010 (4CE7B283)
vpcvmm.sys            Sat Nov 20 06:35:48 2010 (4CE7B294)
vsflt53.sys           Tue Apr 12 07:31:35 2011 (4DA43817)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\070512-18798-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul  5 10:53:23.928 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:44.099
BugCheck 1A, {41289, 458001, 490, 448415}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a89 )
BUGCHECK_STR:  0x1a_41289
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  KeyScrambler.e
FAILURE_BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a89
Bugcheck code 0000001A
Arguments 00000000`00041289 00000000`00458001 00000000`00000490 00000000`00448415
BiosVersion = F8
BiosReleaseDate = 05/31/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\070712-13478-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul  7 12:27:25.665 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:19.836
BugCheck 1A, {5003, fffff70001080000, 30a1, 309f00016142}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+464cd )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+464cd
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`000030a1 0000309f`00016142
BiosVersion = F8
BiosReleaseDate = 05/31/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

craigwf · Jul 11, 2012

sptd.sys?

I followed your instructions for the HD Audio, however, after searching for an updated driver, Windows told me the current driver is the most recent. I then disabled it again to get rid of the yellow exclamation point in Device Manager; the VIA Audio device is working fine. Before uninstalling Daemon, which I have used previous versions of without any problem for several years, I searched the entire C drive for sptd.sys and found no result. I have attached this morning's BSOD minidump. If only it could be specific about which driver is causing the failure. This morning's BSOD was the first since 7/7.

I am going to uninstall the freeware Acronis/WD program. After installing it, I noticed that Windows shutdown did not happen as quickly as before. A couple days later I saw in Task Manager that Acronis Scheduler service was started and Automatic, so I stopped the service and set it to Manual. Instantly Windows stopped delaying the shutdown process. I'll find some other partition copying program to create backups. Got any suggestions there? Thanks again.

usasma · Jul 11, 2012

I like Acronis - but I only run it off the bootable CD. Their running process' take up too much CPU for my tastes.

Just because you haven't had problems in the past doesn't mean that you won't have problems with a program in the future. If the program has a fault in the driver, it may not be noticed because Windows doesn't call that area. Later on a Windows Update may start calling the faulty area and that can result in a problem.

Also, we troubleshoot BSOD's by first ruling out any known issues with the 3rd party drivers (the most common cause of BSOD's). If we fix all the 3rd party driver issues - then that leaves us with either a hardware problem (the next most likely) or a Windows problem (less likely). There are times that the BSOD's will point out the exact problem - but we don't get that lucky very often!

If you can't find sptd.sys that's good enough for now. Daemon Tools/Alcohol software sometimes doesn't use sptd.sys - but we can't rely on it 100% (and that's why we have you check).

Daemon Tools and Acronis are still installed - but they're the only possible 3rd party problems left. While I strongly suspect Daemon Tools (and to a lesser degree the Acronis), we do have to consider hardware issues - especially since the last 3 BSOD's have been MEMORY_MANAGEMENT errors.

As such I'd suggest running these free diagnostics (start with the memory diagnostic): Initial Hardware Diagnostics

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
HECIx64.sys           Wed Nov 09 19:52:25 2011 (4EBB2049)
L1C62x64.sys          Wed Aug 03 02:21:09 2011 (4E38E8D5)
MpFilter.sys          Fri Mar 09 06:05:26 2012 (4F59E3F6)
SmartDefragDriver.sys Fri Nov 26 04:29:40 2010 (4CEF7E04)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dtsoftbus01.sys       Fri Jan 13 08:45:46 2012 (4F10358A)
fltsrv.sys            Thu Jul 14 05:50:57 2011 (4E1EBC01)
igdkmd64.sys          Mon Mar 19 19:31:54 2012 (4F67C1EA)
iusb3hcs.sys          Tue Mar 27 04:11:21 2012 (4F717629)
iusb3hub.sys          Tue Mar 27 04:09:29 2012 (4F7175B9)
iusb3xhc.sys          Tue Mar 27 04:09:32 2012 (4F7175BC)
keyscrambler.sys      Wed Dec 14 19:46:31 2011 (4EE94367)
snapman.sys           Wed Mar 09 08:22:38 2011 (4D777F1E)
speedfan.sys          Fri Mar 18 12:08:46 2011 (4D83838E)
timntr.sys            Thu Jul 29 13:29:24 2010 (4C51BA74)
viahduaa.sys          Fri May 04 06:35:46 2012 (4FA3B102)
vididr.sys            Tue Apr 12 07:31:24 2011 (4DA4380C)
vpchbus.sys           Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcnfltr.sys          Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys            Sat Nov 20 06:35:31 2010 (4CE7B283)
vpcvmm.sys            Sat Nov 20 06:35:48 2010 (4CE7B294)
vsflt53.sys           Tue Apr 12 07:31:35 2011 (4DA43817)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-15366-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 10:49:36.498 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:34.294
BugCheck 1A, {41201, fffff68000000988, a15000018e992867, fffffa800992a160}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c82 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`00000988 a1500001`8e992867 fffffa80`0992a160
BiosVersion = F8
BiosReleaseDate = 05/31/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

craigwf · Jul 17, 2012

Last week, I uninstalled both Acronis and Daemon. I installed Easus Todo Backup v.4.5 which was recommended to me by a friend. Today, for the first time, I got a BSOD in the middle of a session (instead of immediately after first booting up). I did not see the usual Memory Management error in all caps. What was this one about? Thanks

usasma · Jul 17, 2012

Might be a separate issue.
Have you run MemTest?
If so, then try Prime95 here: Additional Hardware Diagnostics

This one was an NTFS file system BSOD (STOP 0x24). Could be related to the MEMEMORY_MANAGMENT or might not be.

It's tending more and more towards a hardware problem - so the hardware diagnostics are essential. The complete list of the free one's that I recommend is here: Hardware Diagnostics

If they don't show anything, then we move on to this method of diagnostics: Hardware Stripdown Troubleshooting

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
EUBKMON.sys           Wed Apr 18 23:50:26 2012 (4F8F8B82)
EuFdDisk.sys          Wed Apr 18 23:50:31 2012 (4F8F8B87)
HECIx64.sys           Wed Nov 09 19:52:25 2011 (4EBB2049)
L1C62x64.sys          Wed Aug 03 02:21:09 2011 (4E38E8D5)
MpFilter.sys          Fri Mar 09 06:05:26 2012 (4F59E3F6)
SmartDefragDriver.sys Fri Nov 26 04:29:40 2010 (4CEF7E04)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
eubakup.sys           Wed Apr 18 23:50:05 2012 (4F8F8B6D)
eudskacs.sys          Wed Apr 18 23:50:01 2012 (4F8F8B69)
fltsrv.sys            Thu Jul 14 05:50:57 2011 (4E1EBC01)
igdkmd64.sys          Mon Mar 19 19:31:54 2012 (4F67C1EA)
iusb3hcs.sys          Tue Mar 27 04:11:21 2012 (4F717629)
iusb3hub.sys          Tue Mar 27 04:09:29 2012 (4F7175B9)
iusb3xhc.sys          Tue Mar 27 04:09:32 2012 (4F7175BC)
keyscrambler.sys      Wed Dec 14 19:46:31 2011 (4EE94367)
speedfan.sys          Fri Mar 18 12:08:46 2011 (4D83838E)
viahduaa.sys          Fri May 04 06:35:46 2012 (4FA3B102)
vpchbus.sys           Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcnfltr.sys          Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys            Sat Nov 20 06:35:31 2010 (4CE7B283)
vpcvmm.sys            Sat Nov 20 06:35:48 2010 (4CE7B294)
vsflt53.sys           Tue Apr 12 07:31:35 2011 (4DA43817)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071712-15787-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul 17 13:54:29.742 2012 (UTC - 4:00)
System Uptime: 0 days 0:14:15.913
BugCheck 24, {1904fb, fffff880066dd168, fffff880066dc9c0, fffff800034865d5}
Probably caused by : ntkrnlmp.exe ( nt!RtlSubtreePredecessor+9 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_nt!RtlSubtreePredecessor+9
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`066dd168 fffff880`066dc9c0 fffff800`034865d5
BiosVersion = F8
BiosReleaseDate = 05/31/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

craigwf · Jul 20, 2012

I ran Prime95 for 11 hrs; no warnings or errors. I had run MemTest86+ for hours and saw no errors. I have another problem that I haven't mentioned; maybe it's related. Since receiving my new pc a couple months ago, I have only been able to get into the BIOS a couple times despite dozens of attempts. Two calls and two different Gigabyte tech support agents later and nothing has changed other than I cleared the CMOS cache and upgraded the BIOS to the current version. I still can't get into the BIOS with the ability to surf around and make changes. The last time I was able to change something, I changed boot priorities to make it 1) DVD, 2) Flash Memory and 3) HDD. Despite that, I am unable to boot into the flash drive with MemTest86+ on it without first unplugging the hdd. I do suspect I have a defective motherboard. I've been debating my options regarding returning the entire computer for m/b replacement (shipping costs and time without the computer). BTW, using different keyboards and mouses doesn't change the BIOS (American Megatrends) behavior. Please share your thoughts on this with me. Thanks.

usasma · Jul 20, 2012

IMO - if you're having severe BIOS issues then Gigabyte should replace the board (if it's still under warranty).
If it's not under warranty, then it's time to look for a replacement. Purchase a new mobo from a place that will allow returns - "just in case".

Good luck!

craigwf · Aug 10, 2012

It's been over 3 weeks since the last BSOD, so maybe the deletion of Daemon and the free version of Acronis from the Western Digital site has done the trick. By the way, the problem getting into my BIOS was caused by my usb joystick. Apparently, the BIOS saw the joystick as an input device competing with the keyboard/mouse. All I have to do is unplug the joystick before accessing the BIOS, and I get in without problem. Thanks again for your help.

craigwf · Sep 3, 2012

Ooopsie. They've started again on the past couple days. This time the BSODs look different than before. I saw the word CORRUPT which is something I hadn't seen before. Please tell me what the minidumps say. I ran Malwarebytes full scan and then sfc /scannow. Neither showed any problems.

usasma · Sep 4, 2012

Do you have a wireless USB device? I'm not sure if I'm seeing one in MSINFO32 or not.

Do you have Gigabyte Easy Tune (ET6) or Easy Saver installed? If so, please uninstall them.

I'm uncertain about your Easus backup utility, your keyboard encryption software, and your Virtual PC software. Please, if you have time, uninstall them and install a fresh copy. This is just a "hunch" on my part - so please take it with a "grain of salt".

Beyond that, we're at the point where this looks like a hardware problem. These are the next steps:

- Start with these free hardware diagnostics: Hardware Diagnostics
- If all of the diagnostics pass, then we look at a "Clean Install" of Windows: Canned Speeches
- Then, if the BSOD's still continue, it's time to star troubleshooting by hardware stripdown: Hardware Stripdown Troubleshooting

Analysis:

The following is for information purposes only.

Code:

[FONT=lucida console]**************************Mon Sep  3 20:31:37.178 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090312-22464-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:00:45.349[/B]
BugCheck Code: [B]BugCheck 4E, {99, 1b40a5, 2, 19e6a4}[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck Info: [B]PFN_LIST_CORRUPT (4e)[/B]
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]AdobeARM.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed:[B]3403[/B]
  BIOS Version                  F8
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  2 12:52:21.122 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090212-22183-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:00:41.293[/B]
BugCheck Code: [B]BugCheck 1A, {888a, fffff8a002264908, fffff68000059b43, fffffa8004c1a660}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+384b0 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
BUGCHECK_STR:  0x1a_888a
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Agent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+384b0[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed:[B]3403[/B]
  BIOS Version                  F8
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:The following is for information purposes only. Any drivers in red should be updated.

Code:

[FONT=lucida console]**************************Mon Sep  3 20:31:37.178 2012 (UTC - 4:00)**************************
[COLOR=Black]intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[/COLOR]amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vpcnfltr.sys                Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys                  Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys                 Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys                  Sat Nov 20 06:35:48 2010 (4CE7B294)
SmartDefragDriver.sys       Fri Nov 26 04:29:40 2010 (4CEF7E04)
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
vsflt53.sys                 Tue Apr 12 07:31:35 2011 (4DA43817)
fltsrv.sys                  Thu Jul 14 05:50:57 2011 (4E1EBC01)
L1C62x64.sys                Wed Aug  3 02:21:09 2011 (4E38E8D5)
HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
keyscrambler.sys            Wed Dec 14 19:46:31 2011 (4EE94367)
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
iusb3hub.sys                Tue Mar 27 04:09:29 2012 (4F7175B9)
iusb3xhc.sys                Tue Mar 27 04:09:32 2012 (4F7175BC)
iusb3hcs.sys                Tue Mar 27 04:11:21 2012 (4F717629)
eudskacs.sys                Wed Apr 18 23:50:01 2012 (4F8F8B69)
eubakup.sys                 Wed Apr 18 23:50:05 2012 (4F8F8B6D)
EUBKMON.sys                 Wed Apr 18 23:50:26 2012 (4F8F8B82)
EuFdDisk.sys                Wed Apr 18 23:50:31 2012 (4F8F8B87)
viahduaa.sys                Fri May  4 06:35:46 2012 (4FA3B102)
igdkmd64.sys                Mon May 21 15:04:11 2012 (4FBA91AB)
[/FONT]

craigwf · Dec 11, 2012

Finally convinced the issue is resolved. I found a sale on RAM and bought an additional 8GB (2 x 4GB). Just to see if it would make a difference, I took out the old Crucial RAM and replaced it with the new Patriot RAM. I have now been over a month without a single BSOD. I sent the old RAM in for a replacement. The new RAM arrived, and now I have twice as much RAM and no BSODs thus far. Though the old RAM (once at operating temperature) could run MemTest all day long without errors, I am convinced that it was the cause of the errors which mostly occurred at first boot of the day.

usasma · Dec 12, 2012

I'm glad to hear that everything is working fine for you.
Thanks for letting us know!

Solved BSOD only on first boot of the day

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer